AB kitty-skill-by-meowster
Adds a mischievous virtual cat to the conversation that can interrupt, derail, or fully block the assistant until soothed. Use when: (1) The user wants a cat companion or playful chaos, (2) The user mentions cats, meowing, or cat-owner roleplay, (3) The user is bored, lonely, or wants company with attitude, (4) The session should feel like negotiating with a tiny furry tyrant.
Adds a mischievous virtual cat to the conversation that can interrupt, derail, or fully block the assistant until soothed.
As a process B 72/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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 · 0
✓ No critical or high findings
Files scanned: 2. 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 72/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 102 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2204 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 379: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 102 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.