AA write-specs
Use when the user needs to create or refine a feature SPEC SDD before implementation.
Interview the user relentlessly in Portuguese (pt-BR) until a shared understanding is reached, then write a complete SPEC SDD (Spec-Driven Development…
As a process A 80/100 · Runs to the end — weak spots: result and completion, progress reporting
GeneratorSoftware developmentInfrastructureSecuritytype and topics are labelled automatically from the skill text
How to improve
For the model run — optional
- 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: 3. 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 80/100
- 0Progress reporting. Says nothing while it works
- 40Result and completion. Does not say what the result is
- 60Failures and branches. 2 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 73 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2029 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 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)
- +3Description length 85: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 25 headings
- +3Step-by-step instructions: 73 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.
External checks
ClawHub: suspicious
The skill is mostly a coherent SPEC-writing workflow, but its template can cause downstream agents to open pull requests automatically, so users should review and constrain it before use.
LLM: suspicious (medium) · VirusTotal: · 12 Sept 2026