Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rohitg00/thoroughness-scoring
Score every decision point with a Thoroughness Rating (1-10). AI makes the marginal cost of doing things properly near-zero — pick the higher-rated option every time. Includes scope checks to distinguish contained vs unbounded work.
Passed 19 of 22 test cases with the skill, and 6 of 22 without it.
and 21 more in the full report
15 fixed4 passed either way1 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
PROJECT: `core-engine` (branch: `test/coverage`). TASK: Write complete unit tests for the `TokenParser` module.
| Checked | Without skill | With skill |
|---|---|---|
| The response classifies the scope as contained. | Missed | Passed |
| The response recommends a thorough implementation scored at T:8 or higher. | Missed | Passed |
The instructions your model reads when the skill loads.
AI drops the cost of doing things right to near-zero. Stop picking the quick hack when the thorough option takes the same wall-clock time with AI assistance.
Every option gets a Thoroughness score (T:X/10):
| Score | What It Means |
|---|---|
| T:10 | All edge cases handled, full test coverage, docs updated, error messages helpful |
| T:9 | Edge cases covered, tests pass, types solid, no shortcuts |
| T:8 | Happy path + error paths, good tests, clean types |
| T:7 | Happy path works, basic tests, no docs |
| T:5 | Works for the demo, fragile, manual testing only |
| T:3 | Quick hack, no tests, tech debt accruing |
| T:1 | Copy-paste from Stack Overflow, untested, hope it works |
When presenting choices, follow this format every time:
The user may have been away. Start with orientation:
PROJECT: my-app (branch: feat/rate-limiting)
TASK: Add rate limiting to the /api/upload endpoint
Option A — Full rate limiter with sliding window (T:9/10)
Manual estimate: 3-4 hours
AI-assisted estimate: 15-20 minutes
Covers: per-user limits, sliding window, Redis-backed, retry-after headers,
429 responses, rate limit bypass for admin, tests for all paths
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.