BC bizauto-flow-pro
业务自动化师专业版是面向团队与企业的全功能业务自动化架构系统。采用"审计-设计-实现-监控-优化"五阶段方法论，从识别瓶颈到高级容错，覆盖自动化全生命周期。专业版解锁事件驱动架构、人机协同审批门、五级容错降级、多系统同步策略与ROI仪表盘五大高级能力。Use when 需要设计创作、UI设计、海报制作、品牌视觉时使用。不适用于3D建模和动画制作。
业务自动化师专业版是面向团队与企业的全功能业务自动化架构系统。采用"审计-设计-实现-监控-优化"五阶段方法论，从识别瓶颈到高级容错，覆盖自动化全生命周期。专业版解锁事件驱动架构、人机协同审批门、五级容错降级、多系统同步策略与ROI仪表盘五大高级能力。Use when…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 2. 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: Unexpected scalar at node end at line 5, column 89: …、人机协同、多系统同步、ROI仪表盘与五级容错降级.。业务自动化师专业版是面向团队与企业的全功能业务自动化架构系统。采用"审计-设计-实现-监控-优化"五阶" ^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 174 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 90 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3429 tokens
- 100Running it twice. No mutating operations
- low 22 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
- +2Single-language instructions
- +3Description length 174: enough signal without eating the budget
- +4Structure: 59 headings
- +3Step-by-step instructions: 90 items
- +4Has examples (15 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.