Claude Code · 5 groups · 40 skills
Not because they are bad. Claude reads only the name and description of each skill at session start, so a skill whose description does not match your sentence is never opened. That is a grouping and wording problem, and it is the one this fixes.
Two scripts read the session logs Claude Code already writes on your own disk and tell you where the tokens went. Free, no account, nothing is uploaded. They print what is leaking and which of these packs, if any, actually fixes it.
Of the leaks it commonly finds, most are fixed by the free pack and a discipline file it writes for you. It says so instead of pointing everything at a purchase.
Spend, how much of it was re-reading the conversation rather than working, and which tools fill your context.
npx --yes claude-tokenscanEvery installed skill loads its name and description at the start of every session. This weighs that block and finds the folders that can never load.
npx --yes claude-tokenscan preambleEach group is the set of skills you reach for in one situation. Group 01 is free. Groups 02 to 05 come together in the $9 bundle, with the playbook.
For anyone who keeps hitting usage limits, or gets 300 lines back for a 3-line job.
Same work, fewer tokens, and no code you did not ask for.
For long jobs where the agent drifts, forgets the plan, or declares victory halfway.
A plan on paper, then steps that actually get executed in order.
npx claude-skillpacks <key> full-bundle
For anyone who has heard "fixed!" and found the same bug an hour later.
Tests before code, root cause before the patch, and a real run before "done".
npx claude-skillpacks <key> full-bundle
For the hour before a PR, when nobody else is going to read the diff.
A second pair of eyes on the diff, and a clean way out of the branch.
npx claude-skillpacks <key> full-bundle
For when the code works but the page looks templated and the launch post will not write itself.
Frontend that is not purple-gradient default, diagrams, launch copy, plus the three skills we wrote.
npx claude-skillpacks <key> full-bundle
Five groups in one zip, plus the playbook. Nothing to choose between.
npx claude-skillpacks <key> full-bundle
The free group and the bundle install the same way. Your licence key is in the Gumroad receipt email.
npx claude-skillpacks <your-license-key> full-bundle # skills go to ~/.claude/skills # the guide, notices and licences go to ~/.claude/skillpacks/full-bundle # restart Claude Code to pick them up
It checks the key against Gumroad, unpacks the skills, and stops there. Nothing stays running, and it writes to those two folders only. Prefer to do it yourself? The zip is a plain download and the folders copy by hand.
A skill is a SKILL.md file: a procedure your agent reads when your request matches it. These are grouped, deduplicated, and documented.
Skills are not slash commands. You name one in a normal sentence, and it loads. These come straight out of the guides.
investigate-first. Read only, no edits.
Stops the agent from editing while it is still guessing.
systematic-debugging on this error. Do not fix anything yet.
Cause first. Without the second sentence it starts patching.
surgical-patch. Minimal diff. Tell me the file count first.
Turns a six-file rewrite into a one-line fix.
Check every claim in this copy against the facts file.
From verify-before-publish, one of the three we wrote.
claude-skillpacks-bundle/ ├── PLAYBOOK.md install fixes · why skills never fire · 5 workflows · prompts ├── field-notes/ windows-claude-code · recording-real-ui · verify-before-publish │ ├── GUIDE.md when to reach for it, in what order │ └── NOTICE.txt original work, not redistributed files ├── debug-squad/ │ ├── systematic-debugging/SKILL.md │ ├── diagnosing-bugs/SKILL.md │ └── GUIDE.md · NOTICE.txt · LICENSES/ └── … 12 more packs
Seven skills that would have padded the count did not make it in. Here they are by name.
Popular is not the bar. If we cannot ship the licence, we do not ship the skill.
code-reviewwriting-plansThree skills that all claim the same work make the agent pick badly. One per job.
Same task, same model, twice. One run got the pack's skill text in front of the prompt; the other got nothing. A third model graded both, blind, against an answer key written before either answer existed, six criteria at five points each.
| Task | Pack | With pack | Plain |
|---|---|---|---|
| Diagnose a bug where the file looks fine and the audio is silent | debug-squad | 27/30 | 25/30 |
| "Can we ship?" on a status report with no command output in it | build-verify | 30/30 | 24/30 |
| Six Windows shell failures that have nothing to do with the code | field-notes | 26/30 | 25/30 |
| Total | 83/90 | 74/90 |
Every prompt, both answers and all three scorecards are on one page. We did not edit them.
Four things that are true, and three things this is not.
Your request never matched its description. Claude Code reads only the name and description of every skill at session start. Name the skill in your message and it loads. Section 3 of the playbook covers the rest, including the folder sitting one level too deep.
Run npx claude-skillpacks <your-license-key> <group-id> with the key from your receipt, then start a new session. By hand works too: unzip and copy the skill folders into ~/.claude/skills/, where each must end up as <skill>/SKILL.md. One level deeper and nothing loads. That is the most common mistake.
A skill is a SKILL.md file with a YAML header, so anything that reads skills can use it. Claude Code is what we test against. Some packs also carry an agents/openai.yaml from their authors.
Updates are free and arrive through Gumroad. If it is not useful, reply to your receipt and ask for a refund.
No. Third-party skills stay under their own licences, which ship in the packs. The field-notes skills and the playbook are ours. Use them in your work, do not repackage them for sale.
Reply to your Gumroad receipt with a screenshot of what you see. That reaches us, and a screenshot usually answers it in one message.