Use when deciding WHAT kind of test a piece of code needs — before writing tests for a new module, when unsure whether something deserves a property test, an example test, a contract test, or an integration test, or when scoping where cargo-mutants should run. Maps test types onto hexagonal zones. The verification-ratchet skill defines HOW to write each kind; this skill defines WHERE each kind belongs.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Scanned
igouss/gitweb-rs
9ef2429
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.