BD 技能升级巧匠L2
面向已有基础结构但不够稳定、放进技能群后容易调错或打架的AI技能，进行系统化升级改造。执行五机制会诊（注册格式合规、入口匹配、去打架、衔接契约、命名记忆），按六条标准修法逐项改造。当用户说"这个技能调不对""多个技能互相抢""帮我做L2升级""这个技能在技能群里不行"时调用。
面向已有基础结构但不够稳定、放进技能群后容易调错或打架的AI技能，进行系统化升级改造。执行五机制会诊（注册格式合规、入口匹配、去打架、衔接契约、命名记忆），按六条标准修法逐项改造。当用户说"这个技能调不对""多个技能互相抢""帮我做L2升级""这个技能在技能群里不行"时调用。
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "knowledge_deps" - note
frontmatter-keyunknown frontmatter key "trigger" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (技能升级巧匠L2) differs from the folder (skill-upgrade-craftsman-l2)
- 100Tools and files. No external tools needed
- 100Steps. 56 steps
- 100Execution cost. Instruction body is 759 tokens
- 100Running it twice. No mutating operations
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
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 138: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.