What happens when you install too many Claude skills
Every installed skill's name and description is visible to Claude up front. With dozens installed, overlaps multiply. How to keep your set of skills lean.
Skills are cheap to install and easy to forget. After a few months it is common to have dozens, several of which describe similar jobs. That has two costs.
Cost one: every description is always in view
Claude sees each installed skill's name and description so it can decide when to use one. The bodies stay out of context until needed, which is the point of the design, but the descriptions add up, and a long, vague description costs more than a short, precise one.
Cost two: more candidates, more mistakes
Every extra skill is another option for each request. Overlapping descriptions make the choice less predictable, as in two skills wanting the same prompt.
Keep the set lean
- Delete personal skills you have not used recently.
- Merge skills that describe the same job.
- Move project-specific skills into that project's
.claude/skills/, so they load only there. - Tighten every description you keep; short and specific beats long and general.
Where each kind of context belongs, skills or CLAUDE.md or MCP, is covered in skills vs CLAUDE.md vs MCP.
Questions
Do installed skills use context even when not active?
Their names and descriptions do, because that is how Claude knows they exist and decides when to use them. The full body is loaded only when a skill is used.
How many skills is too many?
There is no fixed number. The practical limit is where descriptions start overlapping and the wrong skill gets picked. Watch for that rather than counting.
How do I trim my installed skills?
Remove skills you have not used in weeks, merge ones that do the same job, and move project-specific skills into the projects that need them.