Why Too Many Agent Skills Can Make Your AI Worse
More agent skills can make selection harder even when SKILL.md files use progressive disclosure. Learn where context bloat starts, what research found, and how to evaluate skills.
On this page
TL;DR
- Progressive disclosure delays loading a skill's full instructions, but an installed catalog can still expose every skill's name and description to the agent.
- Overlapping skills create a selection problem. A wrong match can add irrelevant instructions or miss a useful workflow; a 2026 benchmark found selection was the clearer source of performance loss.
- Inspect the source, scripts, permissions and real user feedback before relying on a skill; upvotes are leads, not safety certificates.
- Search for a skill at the moment of work, try it on a small task, and share honest feedback after using it.
More skills should make an AI agent more capable. But when you ask Claude to improve a product screen, a crowded skill library creates another job before it changes a pixel: choose among frontend design skills with similar names and confident descriptions. Installing them all hands that decision to the agent every time you work.
That trade is easy to miss. The wrong skill may trigger, a useful one may go unnoticed, and every unreviewed file adds another trust decision. Progressive disclosure limits how much of each skill is loaded, but it does not guarantee the agent will pick well. The question is whether a skill improves the task in front of you.
1. What does a SKILL.md file actually give an agent?
An agent skill is a folder with a SKILL.md file containing a name, description and instructions. It can also include references, assets and executable scripts. The Agent Skills specification describes a three-stage loading pattern: the agent first sees metadata, loads the full instructions when it chooses the skill, and reads supporting files as needed.