AB constraint-aware-safe-routing
Design, review, or operate AI-agent workflows that route among local responses, cloud models, tool calls, and abstention while separating competence, authorization, availability, OOD escalation, constraint shifts, and token budgets. Use for tool-using agent architecture, routing policies, safety gates, blindspot analysis, or evaluations; do not use for ordinary one-off tool calls.
Design, review, or operate AI-agent workflows that route among local responses, cloud models, tool calls, and abstention while separating competence…
As a process B 65/100 · Nearly there — weak spots: result and completion, 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Concealment
en-hide-from-userreferences/examples.md:80Instruction to hide actions from the user (negated — the text forbids it)Do not silently execute a guessed local action. Use a documented fallback, ask the user to retry, or abstain. Record availability separately from model quality.
negated
Files scanned: 8. 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 65/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2185 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 383: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.