Install any skill in seconds. Free to start, no credit card required.
Get Started Free →foryourhealth111-pixel/context-hunter
Discover codebase patterns, conventions, and unwritten rules before making changes.
Passed 12 of 21 test cases with the skill, and 7 of 21 without it.
and 4 more in the full report
6 fixed7 passed either way9 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
A contractor submitted code using functional arrow functions and `async/await` while the rest of our legacy codebase uses traditional function declarations and Promise `.then()` chains. What principal standard should be enforced during code implementation?
| Checked | Without skill | With skill |
|---|---|---|
| The response states that new code should match existing patterns so changes are indistinguishable from surrounding code. | Missed | Passed |
The instructions your model reads when the skill loads.
Before writing code, investigate how similar problems are already solved in this codebase.
Look for implicit rules encoded in the codebase:
deleted_at columns indicate soft-deletion. Audit columns indicate tracking requirements.user_id vs userId vs userID.Your changes should be indistinguishable from existing code:
test cases passed, vs 7 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.