AD attacker
Attack any target (skill, design, argument, code, KB) with a FRESH independent attacker rotating five lenses; coverage-first strike, then PROVE-OR-FLAG adjudication (findings vs flags); never fixes. A different-vendor attacker buys stronger independence. Use-when: "red-team/break this", "$attacker". Do-NOT: fix or edit the target.
Attack any target (skill, design, argument, code, KB) with a FRESH independent attacker rotating five lenses; coverage-first strike, then PROVE-OR-FLAG…
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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: 15. 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 49/100
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (web, git) that frontmatter does not declare
- 100Steps. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2857 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 332: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 24 items
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.