Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/cavekit-writing
How to write Cavekit-quality kits that AI agents can consume effectively. Covers implementation-agnostic cavekit design, testable acceptance criteria, hierarchical structure, cross-referencing, cavekit templates, greenfield and rewrite patterns, cavekit compaction, and gap analysis. Trigger phrases: "write kits", "create kits", "cavekit this out", "define requirements for agents", "how to write kits for AI"
Passed 16 of 21 test cases with the skill, and 10 of 21 without it.
and 6 more in the full report
8 fixed9 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
Create a Mermaid entity-relationship diagram (ERD) definition for a relational database with `Customer`, `Order`, and `OrderItem` tables.
| Checked | Without skill | With skill |
|---|---|---|
| Declares the diagram header starting with erDiagram on the first line | Missed | Passed |
The instructions your model reads when the skill loads.
Kits are implementation-agnostic. They define what the system must do and how to verify it, but never prescribe a specific framework, language, or architecture.
This is the fundamental distinction in Cavekit:
When kits avoid prescribing HOW, they become:
Bad cavekit requirement: "Use React useState hook to manage form state" Good cavekit requirement: "Form state persists across user interactions within a session. Acceptance: entering values, navigating away, and returning preserves all entered values."
This is the single most important rule in Cavekit writing. If an agent cannot automatically validate a requirement, that requirement will not be met.
Every requirement must answer: "How would an automated test verify this?"
| Weak Criterion | Strong Criterion |
|---|---|
| "UI should look good" | "All interactive elements have minimum 44x44px touch targets" |
| "System should be fast" | "API responses return within 200ms at p95 under 100 concurrent users" |
| "Handle errors gracefully" | "Network failures display a retry prompt with exponential backoff (1s, 2s, 4s)" |
| "Support authentication" | "Valid credentials return a session token; invalid credentials return 401 with error message" |
test cases passed, vs 10 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.