Guide
How to sync skills to Claude Code, Codex, Cursor and OpenCode
Keep every skill in one folder and link it to where each tool looks: ~/.claude/skills for Claude Code, ~/.agents/skills for Codex (Cursor and OpenCode read both). To share the same skills with a team, serve them from one MCP server instead, since all four tools connect to remote MCP servers.
Short answer
- Claude Code:
~/.claude/skills, or.claude/skillsin a repo. It doesn't read.agents/skills. - Codex:
~/.agents/skills, or.agents/skillsin a repo. - Cursor:
.cursor/skillsand.agents/skills, also.claude/skillsand.codex/skills, each in the repo or under~/. - OpenCode:
.opencode/skills,~/.config/opencode/skills, also.claude/skillsand.agents/skills.
Where each tool looks
| Tool | Personal folder | Repo folder | Also reads |
|---|---|---|---|
| Claude Code | ~/.claude/skills | .claude/skills | Managed, plugin, and claude.ai account skills |
| Codex | ~/.agents/skills | .agents/skills (current folder, parent, repo root) | /etc/codex/skills |
| Cursor | ~/.cursor/skills, ~/.agents/skills | .cursor/skills, .agents/skills | .claude/skills, .codex/skills and their ~/ versions |
| OpenCode | ~/.config/opencode/skills | .opencode/skills | .claude/skills, .agents/skills and their ~/ versions |
From each tool's docs, read on 4 November 2026. Each folder holds one subfolder per skill, with a SKILL.md inside.
Two folders cover all four: ~/.claude/skills (Claude Code, Cursor, OpenCode) and ~/.agents/skills (Codex, Cursor, OpenCode).
One copy on your machine: symlinks
Keep the real files in one folder and point both locations at it. On macOS or Linux:
mkdir -p ~/skills
# move existing skills in first, then:
ln -s ~/skills ~/.claude/skills
ln -s ~/skills ~/.agents/skills
If either folder already exists, move its contents into ~/skills and remove the empty folder before linking. Cursor and OpenCode read both locations, so they reach the same files through two paths. If either shows a skill twice, it is still one file: edit it once in ~/skills.
For a repo, do the same with .claude/skills and .agents/skills, commit the real folder, and everyone who clones gets the skills.
One copy for the team: an MCP server
Symlinks and repos work for developers. They don't reach the teammate who works in Claude or ChatGPT in the browser, and they need a git pull to update. All four coding agents also connect to remote MCP servers:
- Claude Code:
claude mcp add --transport http <name> <url> - Codex: a server entry with
url = "…"in its config (Streamable HTTP). - Cursor: a Streamable HTTP server in its MCP settings.
- OpenCode: a server with
"type": "remote"in its config.
A server that holds the team's skills gives the coding agents, Claude, and ChatGPT the same current copy, with nothing to pull or re-link.
AI Skill Pod · free to start
One pod for your team's skills and one MCP link for Claude Code, Codex, Cursor, OpenCode, Claude, and ChatGPT. The people who never open a terminal add skills by pasting a doc or saying "make this a team skill" in chat.
Check that a tool sees your skill
- Check the shape:
<folder>/<skill-name>/SKILL.md, with the folder named the same as thenamefield. - Check the frontmatter: a
nameof lowercase letters, numbers, and hyphens, up to 64 characters, and a non-emptydescription. The SKILL.md converter writes both. - Start a new session and ask the agent what skills it has, or ask for the task the description names.
Skills for this
- ProductPRD from messy notesTurns notes, Slack threads, and call notes into a PRD: problem with evidence, goals and non-goals, metrics, must/should/could requirements, and flagged gaps.
- ProductRelease notes from merged changesWrites customer-facing release notes from merged PRs or tickets, grouped New, Improved, Fixed, benefit-first, plus an internal changelog.
- ProductUser stories with acceptance criteriaTurns a feature into user stories with Given/When/Then acceptance criteria, edge cases, out-of-scope notes, and an INVEST check per story.
- ProductSpec review before buildReviews a PRD or spec before build for ambiguity, missing empty/loading/error/permission states, metrics, rollout, and a first-time user walk-through.
- Customer successBug report from a support ticketTurns a customer complaint into an engineering-ready bug report: steps to reproduce, expected vs actual, environment, impact, evidence, and questions to ask.
Questions
How do I sync Claude Code skills with Claude Desktop and claude.ai?
Claude Code reads folders on disk; Claude Desktop and claude.ai keep uploaded skills in your account. Upload the same folder as a ZIP under Customize > Skills, or connect both to one MCP server that serves the skills.
Why doesn't Claude Code see my .agents/skills folder?
Claude Code reads ~/.claude/skills and .claude/skills, not .agents/skills. Link the folder into ~/.claude/skills, as in the symlink steps above.
Sources
- Claude Code docs: Skills (read 2026-11-04)
- Claude Code docs: MCP (read 2026-11-04)
- Codex docs: Build skills (read 2026-11-04)
- Codex docs: MCP (read 2026-11-04)
- Cursor docs: Skills (read 2026-11-04)
- Cursor docs: MCP (read 2026-11-04)
- OpenCode docs: Skills (read 2026-11-04)
- OpenCode docs: MCP servers (read 2026-11-04)