CF do
Classify user requests and route to the correct agent + skill. Primary entry point for all delegated work.
Classify user requests and route to the correct agent + skill.
As a process F 41/100 · Will not run — References files that are not bundled: scripts/routing-ab-results/self-route-v1/VERDICT.md, scripts/routing-manifest.py
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Bash Grep Glob Skill Task
Files scanned: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6985 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/routing-ab-results/self-route-v1/VERDICT.md - warning
missing-refreference to a missing file: scripts/routing-manifest.py - note
frontmatter-keyunknown frontmatter key "routing" - note
edit-residuethe text marks something as outdated (lines 266): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 41/100
- 0Tools and files. 2 referenced file(s) missing: scripts/routing-ab-results/self-route-v1/VERDICT.md, scripts/routing-manifest.py
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 16 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 6985 tokens
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 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
- +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 106: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 10 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (7 of 17)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 53.