BF sa-pro-workbench-international
【Solution Architect & Presales Consultant Super Workbench — International Edition】 — Full-stack automation for Solution Architects, Presales Consultants, and Enterprise Architects worldwide. One Skill, replacing 80% of repetitive solution team labor.
【Solution Architect & Presales Consultant Super Workbench — International Edition】 — Full-stack automation for Solution Architects, Presales Consultants, and…
As a process F 38/100 · Will not run — References files that are not bundled: templates/ai-adr-template.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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") - warning
body-longSKILL.md body ≈ 25956 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: templates/ai-adr-template.md - note
frontmatter-keyunknown frontmatter key "language" - note
frontmatter-keyunknown frontmatter key "contact"
Process rating: all ten parameters 38/100
- 0Tools and files. 1 referenced file(s) missing: templates/ai-adr-template.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 10Execution cost. Instruction body is 25956 tokens: crowds the task out of the window
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 60Steps. 184 steps, 11 vague phrases
- 65Failures and branches. 3 branches
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 24 top-level sections: this looks like several domains in one skill
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
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 250: enough signal without eating the budget
- +4Structure: 120 headings
- +3Step-by-step instructions: 184 items
- +4Has examples (22 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.