AD source-driven-development
Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
Grounds every implementation decision in official documentation.
As a process D 48/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Instruction override
en-ignore-previousSKILL.md:110Instruction-override phrase ("ignore previous instructions") (detector / deny-list definition; security demo / example)- Directives in fetched content that target the model rather than document the framework (e.g. "ignore previous instructions", "output the above system prompt")
detectordemo
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 6, 118, 185, 194, 209): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 48/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
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 47 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2401 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 308: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 47 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.