BD quality-document-control
质量体系文件管控助手。聚焦文件管控生命周期——编号体系设计、审批与变更流程、文件矩阵/受控清单生成、记录留存期限判定、外来文件受控、版本与作废判断。生成为主+轻交互，纯文字MD输出，企业专属信息标"待企业补充"。不替代iso9001-qms-generator等文档内容生成类技能。
质量体系文件管控助手。聚焦文件管控生命周期——编号体系设计、审批与变更流程、文件矩阵/受控清单生成、记录留存期限判定、外来文件受控、版本与作废判断。生成为主+轻交互，纯文字MD输出，企业专属信息标"待企业补充"。不替代iso9001-qms-generator等文档内容生成类技能。
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: 0. 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 "slug" - note
frontmatter-keyunknown frontmatter key "displayName"
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 (quality-document-control) differs from the folder (skill-quality-document-control)
- 100Tools and files. No external tools needed
- 100Steps. 37 steps
- 100Execution cost. Instruction body is 861 tokens
- 100Running it twice. No mutating operations
- low 10 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
- +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 141: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 37 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.