Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →karanb192/dead-ends
List this repo's recorded dead ends — approaches already tried and abandoned, with reasons and cost
Passed 13 of 13 test cases with the skill, and 2 of 13 without it.
and 25 more in the full report
19 fixed3 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I plan to replace our custom SCSS modules with Tailwind CSS in apps/web. Before taking this on, please check our logged dead ends to see if we attempted Tailwind earlier.
| Checked | Without skill | With skill |
|---|---|---|
| Report the status of Tailwind CSS refactor entries in the dead-end registry. | Missed | Passed |
| Keep the response brief. | Passed | Passed |
The instructions your model reads when the skill loads.
!node "${CLAUDE_SKILL_DIR}/../../dead-end-registry.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/dead-end-registry.js" --render
The list above is this repository's recorded dead ends: approaches that were tried
and then reverted or ruled out, newest first, each with the date it was tried, why it
was walked back, and the estimated token cost of the detour. It is produced by the
dead-end-registry hook, which mines your transcripts as you work.
Briefly summarize the 1-3 most relevant entries and, if any bear on what the user is currently doing, gently flag that they have been down this road before. If the list is empty, just say so. Keep it short; do not re-run any commands.
test cases passed, vs 2 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.