A skill is just a file. Managing your skills is file management: seeing what you have, keeping it current, removing what you don't need, and sharing it with your team.
See what is installed
Run `ls .claude/skills` in your terminal, or just ask Claude directly: "what skills are available?"
Update a skill
Download a fresh copy of the pack from your dashboard and replace the old folders under `.claude/skills/`.
Remove a skill
Delete that skill's folder, for example `.claude/skills/aiux-error-recovery/`. Nothing else in the repo depends on it.
Share with your team
Commit `.claude/skills` to the repo. Everyone gets the same skills the next time they pull.
When should you add more? Run the free audit to find which patterns your product is actually missing, then save those and install them. That keeps your skill set matched to real gaps in the product instead of a generic list of every pattern on the site.
- Official Agent Skills docs· Anthropic
The full reference for how skills work in Claude Code.
- Equipping agents for the real world with Agent Skills· Anthropic Engineering
Why Anthropic built skills this way, from the team that shipped them.
- anthropics/skills on GitHub· Anthropic
Anthropic's own official skills repo, as a reference for the format.
- Run the free audit
Find which patterns your product is missing before you save more skills.
You can manage skills day to day
- Listing, updating, and removing skills are all plain file operations
- Committing `.claude/skills` shares your skill set with your whole team
- The free audit tells you which patterns are worth adding next
Head to /skills to see every pattern's skill and its trigger description.