Claude Code has a specific skill precedence order

There’s a specific priority order that determines which skill gets activated in Claude Code. This matters a lot if you have personal skills that might clash with project-level ones in a repo you’ve just cloned.

From highest to lowest:

Enterprise — managed settings deployed org-wide. They always win. Makes sense for enforcing standards across a company.

Personal — lives in ~/.claude/skills. Follows you across every project and overrides any project skill with the same name.

Project — the .claude/skills directory inside a repo. Shared with anyone who clones it, but gets ignored if you have a conflicting personal skill.

Plugins — lowest priority of the bunch.

So if a skill isn’t behaving the way you expect, check whether something higher up the chain is shadowing it.