BF contract-to-spec
将合同文件转换为需求规格说明书。使用场景：用户提供合同文件名（如"合同 -XXX 系统.docx"），需要生成完整的需求规格说明书。自动完成：1) 读取合同提取项目信息 2) 生成系统架构图 3) 生成 6 个子功能原型图 4) 生成带格式的 Word 文档到桌面。
As a process F 31/100 · Will not run — References files that are not bundled: references/architecture_template.html, references/prototype_templates/
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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: 4. 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") - warning
missing-refreference to a missing file: references/architecture_template.html - warning
missing-refreference to a missing file: references/prototype_templates/
Process rating: all ten parameters 31/100
Will not run. References files that are not bundled: references/architecture_template.html, references/prototype_templates/
- 0Tools and files. 2 referenced file(s) missing: references/architecture_template.html, references/prototype_templates/
- 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 (contract-to-spec) differs from the folder (shucheng-contract-to-spec)
- 100Steps. 31 steps
- 100Execution cost. Instruction body is 317 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
- +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 133: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 31 items
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.
External checks
ClawHub: suspicious
This skill is a local contract-to-Word generator, but it should be reviewed because it can pick the wrong Desktop file and generate authoritative-looking output with hard-coded or incomplete contract details.
LLM: suspicious (high) · VirusTotal: · 29 May 2026