BD migration-pack-deploy
帮用户把 AI 助手（谢尔比）从一台电脑"搬"到另一台。用户说想迁移/换电脑/换平台/打包带走时，帮他打包成一个 zip；到了新电脑说部署/还原时，帮他自动放回原位，完成迁移闭环。对用户零技术要求，全程代劳。关键词：迁移、换电脑、换平台、打包、部署、新机器、还原、migrate、pack、deploy。
帮用户把 AI 助手（谢尔比）从一台电脑"搬"到另一台。用户说想迁移/换电脑/换平台/打包带走时，帮他打包成一个 zip；到了新电脑说部署/还原时，帮他自动放回原位，完成迁移闭环。对用户零技术要求，全程代劳。关键词：迁移、换电脑、换平台、打包、部署、新机器、还原、migrate、pack、deploy。
As a process D 48/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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 48/100
- 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
- 30Running it twice. 12 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 715 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 152: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 33 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.