Switch Claude Code skills on per project so they stop getting dropped
makosamunyaa found skill descriptions are capped at about 1% of context and the least-used get silently dropped, so he built Skillshed to enable vetted skills per project.
Source
@makosamunyaa on X · 2026-10-22
Written in our own words. Credit to the original author. Link checked 2026-10-24.
What they did
makosamunyaa found skill descriptions are capped at about 1% of context and the least-used get silently dropped, so he built Skillshed to enable vetted skills per project.
Result (as claimed)
The skills a project needs actually fire.
Tools they used
Cost: Pricing depends on the tools you pick; check each official pricing page.
Set it up
Pick a contained repo or task
Start on a branch or side project where mistakes are cheap.
Install and configure
Set up Claude Code, Codex. Read what it can run on your machine and limit permissions where possible.
Run it on a real task
Give it a well-scoped issue and let it work. Review the diff like any pull request.
Add guardrails
Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Switch Claude Code skills on per project so they stop getting dropped What the original author did: makosamunyaa found skill descriptions are capped at about 1% of context and the least-used get silently dropped, so he built Skillshed to enable vetted skills per project. Reported result (as claimed by the author): The skills a project needs actually fire. Source: https://x.com/makosamunyaa/status/2113243148876951978 Tools they used: Claude Code, Codex Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Switch Claude Code skills on per project so they stop getting dropped What the original author did: makosamunyaa found skill descriptions are capped at about 1% of context and the least-used get silently dropped, so he built Skillshed to enable vetted skills per project. Reported result (as claimed by the author): The skills a project needs actually fire. Source: https://x.com/makosamunyaa/status/2113243148876951978 Tools they used: Claude Code, Codex Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Switch Claude Code skills on per project so they stop getting dropped What the original author did: makosamunyaa found skill descriptions are capped at about 1% of context and the least-used get silently dropped, so he built Skillshed to enable vetted skills per project. Reported result (as claimed by the author): The skills a project needs actually fire. Source: https://x.com/makosamunyaa/status/2113243148876951978 Tools they used: Claude Code, Codex Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Guides for this use case
How to write a CLAUDE.md or AGENTS.md rules file · How to use Claude Code and Codex together · How to use Claude Code skills and plugins · How to run multiple coding agents together
Related use cases
Have Claude Code review your Codex build from your phone
From his phone, ZazenCodes gets Codex on his computer to spin up Claude Code and pull its review of what Codex built.
Have CLAUDE.md import AGENTS.md so Claude and Codex share rules
Dainer_Jun's CLAUDE.md just imports AGENTS.md and routes the work, Codex reads AGENTS.md on its own, and work state lives in files too.
Run Claude Code and Codex agents together from one local dashboard
ahmedaghadi built acom, a local dashboard to launch Claude Code and Codex agents across projects, follow their activity, pass messages and handle interruptions.
Keep Claude Code and Codex on one rules file with a symlink
rthiago found CLAUDE.md said pnpm while AGENTS.md said npm, so the two agents kept rewriting the lockfile. He keeps one file and symlinks the other: ln -s AGENTS.md CLAUDE.md.