AC emotion-skill
Markdown-first soft router for coding agents. Use when the current prompt or visible context shows clear urgency, strong anger/frustration toward the current work, or confusion about the active workflow. Do not use for ordinary tasks, neutral commands, technical explanations, or quoted/content-only emotion words.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 314 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 59/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
- 55Failures and branches. 1 branches
- 60Consistency. The Hermes dialect needs category and tags
- 100Tools and files. No external tools needed
- 100Steps. 9 steps
- 100Execution cost. Instruction body is 306 tokens
- 100Running it twice. No mutating operations
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
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 314: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 9 items
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.