AC kai-business-blueprint
Use when generating business capability blueprints, domain-knowledge maps, or architecture diagrams from presales materials, meeting notes, or solution docs. Triggers: 商业蓝图, 商业模式画布, 领域知识大图, 架构图, capability map, strategy canvas. Not for generic documents, PPTs, or simple flowcharts.
As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, consistency, progress reporting
How to improve
- 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: 59. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Use when generating business capability blueprints, domain-knowled… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (kai-business-blueprint) differs from the folder (business-blueprint-skill)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 10 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1309 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 282: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 10 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (6 of 19)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.