BC dev-guide-generator
Generates complete technical tutorials from prerequisites and environment setup to core steps, troubleshooting, and a final cheatsheet. Trigger on requests to write a tutorial, create a setup guide, organize steps for beginners, or keywords like step-by-step, quickstart, or how-to guide.
Generates complete technical tutorials from prerequisites and environment setup to core steps, troubleshooting, and a final cheatsheet.
As a process C 64/100 · Has gaps — weak spots: result and completion, running it twice, 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Dangerous commands
cmd-privilegeSKILL.md:193Privilege escalation / world-writable permissions (quoted — discussed, not commanded)- For permission-related issues, explain why the permission is needed rather than jumping to `sudo` or `chmod 777`
quoted -
low Dangerous commands
cmd-privilegeSKILL.md:196Privilege escalation / world-writable permissions (detector / deny-list definition; security demo / example)- Solutions must not include operations that could create security risks (e.g., `chmod 777`, disabling firewalls)
detectordemo -
low Dangerous commands
cmd-privilegeSKILL.md:359Privilege escalation / world-writable permissions (security demo / example; quoted — discussed, not commanded)- [ ] No suggestions that could create security vulnerabilities (e.g., `chmod 777`)
demoquoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 60Steps. 102 steps, 6 vague phrases
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3311 tokens
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 288: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 102 items
- +4Has examples (10 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.