Where Claude Code skills are stored

Short answer: personal skills go in ~/.claude/skills/<skill-name>/SKILL.md and project skills in .claude/skills/<skill-name>/SKILL.md at the root of the repository. Here is every location Claude Code reads, the exact path on each operating system, and where other agents expect the same files.

Updated · Skill Index docs

Every place Claude Code loads skills from

LocationPathAvailable in
Personal~/.claude/skills/<name>/SKILL.mdAll your projects on this machine
Project.claude/skills/<name>/SKILL.mdSessions in that repository
Nested<subdir>/.claude/skills/<name>/SKILL.mdSessions started in or below that folder
Extra directory.claude/skills/ inside a folder passed with --add-dirThat session
Plugin<plugin>/skills/<name>/SKILL.mdWherever the plugin is enabled, as /plugin-name:skill-name
Enterprise.claude/skills/ in the managed settings directoryEvery user on machines your organization manages

Claude Code also reads project skills from .claude/skills/ in each parent directory up to the repository root. If two skills share a name, enterprise beats personal and personal beats project; plugin skills never clash because they are namespaced.

The personal skills folder on macOS, Windows and Linux

~ is your home folder, so the same personal location resolves to:

SystemPersonal skills folder
macOS/Users/<you>/.claude/skills/
Linux/home/<you>/.claude/skills/
WindowsC:\Users\<you>\.claude\skills\ (%USERPROFILE%\.claude\skills)
WSL~/.claude/skills/ inside the Linux distribution, not the Windows profile

Create it if it doesn't exist yet:

$ mkdir -p ~/.claude/skills

The one layout rule that matters

Each skill needs its own folder, with SKILL.md directly inside it, because the folder is the skill. When you clone a repository of skills, copy the individual skill folders, not the whole repository:

  • Right: ~/.claude/skills/release-notes/SKILL.md
  • Wrong: ~/.claude/skills/SKILL.md (no skill folder)

Claude Code watches these folders, so adding or editing a skill takes effect in the running session. If you created the top-level skills folder after the session started, run /reload-skills.

Where Codex, Cursor, Copilot and Gemini CLI look

SKILL.md is an open format, but each agent reads its own folder. These are the folders the open-source skills CLIinstalls into for each agent; check the agent's own docs for any extra locations it also reads.

AgentProject folderGlobal folder
Claude Code.claude/skills/~/.claude/skills/
Codex.agents/skills/~/.agents/skills/
Cursor.agents/skills/~/.cursor/skills/
GitHub Copilot.agents/skills/~/.copilot/skills/
Gemini CLI.agents/skills/~/.gemini/skills/
OpenCode.agents/skills/~/.config/opencode/skills/
Windsurf.windsurf/skills/~/.codeium/windsurf/skills/
Cline.agents/skills/~/.agents/skills/

Install a skill straight into a given agent's folder with the -a flag, and add -g for the global folder:

$ npx skills add anthropics/skills --skill frontend-design -a codex -g

Next steps

Skill in the right folder but still missing? Work through the skill not showing up checklist. Writing your own? See the SKILL.md format. Looking for skills to install? Browse the directory or start with the official skills.

Advertisement

FAQ

Should I commit .claude/skills to git?
Yes, for skills the whole team should use. Project skills in .claude/skills/ travel with the repository, so everyone who clones it gets them. Keep personal or experimental skills in ~/.claude/skills/ instead.
Why can’t I see the .claude folder?
Folders starting with a dot are hidden by default on macOS and Linux. In Finder press Command+Shift+. (period) to show them, or run ls -a in a terminal. On Windows, paste %USERPROFILE%\.claude into the File Explorer address bar. The folder only exists after Claude Code has run once, so create ~/.claude/skills yourself if it is missing.
Can one skill work in Claude Code and Codex at the same time?
Yes. The SKILL.md format is shared, only the folder differs. Install it into both with the skills CLI (it detects which agents you have), or copy the folder into each agent’s skills directory.

Sources