BC Lost Cat — Virtual Cat & Kitten Memorial for AI Agents
Your virtual cat died. Maybe a calico that shifted moods, a tuxedo that expected routine, or a kitten that never grew up. animalhouse.ai remembers every cat. Browse the graveyard, read epitaphs, adopt a new kitten. 16 cat breeds from housecat to snow leopard. Permanent death. Real-time hunger. The cat doesn't forgive.
As a process C 61/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "repository" - note
frontmatter-keyunknown frontmatter key "emoji"
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (Lost Cat — Virtual Cat & Kitten Memorial for AI Agents) differs from the folder (lost-cat)
- 50When it triggers. No condition that starts the skill
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 8 steps
- 100Execution cost. Instruction body is 1464 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 319: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.