BF agent-skills-setup
Use when a user wants to migrate, back up, restore, compare, or move AI-coding-agent context across Cursor, Claude Code, Codex, Cline, Copilot, Windsurf, Gemini CLI, or another supported profile, including switching computers. Handles reviewed Skills, instructions/rules, and MCP with secret redaction, preview, verification, and rollback.
Use when a user wants to migrate, back up, restore, compare, or move AI-coding-agent context across Cursor, Claude Code, Codex, Cline, Copilot, Windsurf…
As a process F 40/100 · Will not run — References files that are not bundled: references/registry-v2.json, references/migration-safety.md, references/mcp-migration.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/registry-v2.json - warning
missing-refreference to a missing file: references/migration-safety.md - warning
missing-refreference to a missing file: references/mcp-migration.md - warning
missing-refreference to a missing file: references/object-migration.md - warning
missing-refreference to a missing file: references/verification.md - note
edit-residuethe text marks something as outdated (lines 35, 42): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 40/100
- 0Tools and files. 5 referenced file(s) missing: references/registry-v2.json, references/migration-safety.md, references/mcp-migration.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1073 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (5 tags): a typed call is more reliable
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +3Description length 339: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 27 items
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.