AC prompt-to-skill-router
Route each request to the best execution path: direct answer, installed skill, new skill, or a multi-skill workflow, with explicit reasoning about friction, value, and fit.
As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
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
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Route each request to the best execution path: direct answer, inst… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 70Failures and branches. 11 branches
- 100Tools and files. No external tools needed
- 100Steps. 96 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1919 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 172: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 96 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.
External checks
ClawHub: clean
This instruction-only skill helps route requests to direct help or suitable skills and does not request code execution, credentials, data access, or persistence.
LLM: benign (high) · VirusTotal: · 29 May 2026