CA rt-ica
Works backward from the stated goal through its prerequisite chain — what must exist to reach the goal, then what each of those requires, back to the current state — classifying each prerequisite as AVAILABLE, DERIVABLE, or MISSING, and blocking planning until nothing is MISSING. Use before creating plans, delegating to agents, or defining acceptance criteria. Activates on specs, PRDs, tickets, RFCs, architecture designs, and multi-step engineering tasks. Always pass `#N` or an inline goal — invoking with no argument and no inline context returns BLOCKED. Integrates with CoVe-style planning pipelines.
Works backward from the stated goal through its prerequisite chain — what must exist to reach the goal, then what each of those requires, back to the current…
As a process A 81/100 · Runs to the end — weak spots: when it triggers, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 Risky intent
intent-offensive-securitySKILL.md:158Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)1. **Security boundary or credential ambiguity** - any action involving secrets, credentials, tokens, auth rules, permissions, encryption keys, signing keys, customer data, or privilege escalation whe
detector
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 9367 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 81/100
- 20When it triggers. No condition that starts the skill
- 40Execution cost. Instruction body is 9367 tokens: crowds the task out of the window
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 136 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Result and completion. Output format and completion criterion are stated
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 19 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (21 tags): a typed call is more reliable
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)
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 608: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 136 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.