AF lang-migration
AI-driven full-project language migration skill. Use this skill whenever the user wants to port, translate, or rewrite a codebase from one programming language to another — including Python→Rust, Python→Go, Python→C, Python→C++, Python→Zig, Python→Bun/TS, or any other pair. Also trigger when user mentions "精确复刻", "语言迁移", "port project", "translate codebase", "1:1 rewrite", or "language conversion". This skill enforces structural equivalence first, full asset coverage (no file skipped), persistent YAML state across sessions, and a strict no-mock verification policy with human-gated blocking.
As a process F 52/100 · Will not run — References files that are not bundled: references/lang-pairs/<source>-<target>.md, references/lang-pairs/<pair>.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: 36. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/lang-pairs/<source>-<target>.md - warning
missing-refreference to a missing file: references/lang-pairs/<pair>.md
Process rating: all ten parameters 52/100
- 0Tools and files. 2 referenced file(s) missing: references/lang-pairs/<source>-<target>.md, references/lang-pairs/<pair>.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Result and completion. Does not say what the result is
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 5 branches
- 70Execution cost. Instruction body is 4736 tokens
- 85Steps. 63 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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)
- +3Output format is not stated: the model decides each time
- -31 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 597: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 63 items
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (10 of 10)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.