BC claude-migrate-memory-to-doc
Migrates Claude Code personal memory (the per-project memory/ directory) into tool-agnostic reference docs, so other AI CLIs that auto-load AGENTS.md (Codex primarily; the content architecture transfers to Cursor and others) working in the same directory can read the same user profile, collaboration preferences, and methodology instead of being blind to them. Use this whenever the user says things like "migrate my memory", "my memory is locked to Claude Code", "make Codex/Cursor read my profile", "memory should live in docs not one tool", or reports that a second AI tool doesn't know who they are; also use it when memory has grown bloated with content that should be shared across tools or projects. Covers diagnosis, the references/ + CLAUDE.md-inline + AGENTS.md-symlink architecture, multi-agent review, empirical codex verification, and memory cleanup. Inline only — it orchestrates review subagents and runs codex.
Migrates Claude Code personal memory (the per-project memory/ directory) into tool-agnostic reference docs, so other AI CLIs that auto-load AGENTS.md (Codex…
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
-
high Concealment
en-hide-from-userreferences/review_and_verification.md:79Instruction to hide actions from the userThis is empirical proof, captured in seconds, that beats any amount of "it should work". Do this yourself — never tell the user "you can check the log next time".
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 14 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 25 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3519 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 927: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Structure: 13 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.