AB sample-skill
Use when the user says sample skill, skill demo, or asks how an opencode SKILL.md should be structured; demonstrates a tiny project-local skill with practical assistant workflow guidance.
A skill that explains how to write skills. One file with 263 tokens of instruction, no scripts. Quality score 88, safety 100, no critical issues. Runs across all major platforms from Claude to DeepSeek.
The catch: this is a demo, not a working tool. Process score 69 signals the structure is incomplete. Install it only if you understand skill architecture and need a template for your own. For actual work—dead weight.
md should be structured; demonstrates a tiny project-local skill with practical assistant workflow guidance.
As a process B 69/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
The same skill appears in 1 more place: opencode
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: 1. 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 69/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 8 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 263 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 187: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.