Share one agent skill between Claude Code, Codex and Cursor

By

Updated

See which skill folders Claude Code, Codex and Cursor read, find the skills one of them is missing, and link the same folder into it with Skill Cabinet.

You wrote a skill for Claude Code. Cursor loads it, Codex doesn’t, and you’d like all three to read the same SKILL.md, so one edit reaches every agent.

A skill is a folder with a SKILL.md file that teaches an agent one task. Writing that file is covered in agent skills. Project rules are a different thing: AGENTS.md lives in the repo, and the agents that read it already share it. Skills live in your home folder, and each agent looks in its own folders.

Which agent reads which folder

This is the map Skill Cabinet uses to decide where a skill is available:

FolderAgents that load skills from it
~/.agents/skillsCursor, Codex, Gemini CLI, OpenCode, Droid, Pi
~/.claude/skillsClaude Code, Cursor, OpenCode
~/.codex/skillsCodex, Cursor
~/.cursor/skillsCursor
~/.config/agents/skillsAmp

Gemini CLI, OpenCode, Droid and Pi also have a folder of their own.

So a skill in ~/.claude/skills loads in Claude Code and Cursor, and Codex never sees it. A skill in ~/.agents/skills loads in Codex and Cursor, and Claude Code never sees it. Copying the folder into the other place fixes it today, and next month you have two SKILL.md files that say different things.

The fix is a symbolic link: the folder stays where it is, and the other agent’s folder gets a link to it.

One skill folder linked into CodexThe release-notes folder lives in the Claude Code skills folder, which Claude Code and Cursor read. Add to Codex creates a link in the Codex skills folder that points back to it, so Codex reads the same SKILL.md.points to~/.claude/skills/release-notesClaude CodeCursor~/.codex/skills/release-noteslinkCodex

Find the skills an agent can’t see

Skill Cabinet runs on macOS 14 Sonoma or later. Download it from your Polar receipt, unzip it and drag it to Applications. Everything here happens on your Mac, with no account.

Open it and choose Your skills in the toolbar menu, so plugin and built-in skills stay out of the way. The sidebar shows Missing somewhere, the skills at least one of your agents can’t load. Each row has an icon per agent, grayed out where the skill is missing.

Select a skill and Available in lists every agent. The ones that load it say where from, and the others have an Add to button with the folder it will link into. Here’s a sample release-notes skill that lives in ~/.agents/skills, so it needs a link for Claude Code and one for Amp:

Skill Cabinet with Missing somewhere selected and the release-notes skill open. Available in shows Cursor, Codex, Gemini, OpenCode, Droid and Pi loaded from ~/.agents/skills, and Add to Claude Code and Add to Amp buttons with the folders they link into

The same check works in the terminal. Choose Skill Cabinet → Install Command Line Tool… to link the skillscout command into /usr/local/bin. macOS may ask for your password for that folder.

Here’s the Claude Code case, in a test home folder that has one skill in ~/.claude/skills:

skillscout list --missing
SKILL          CHATS  Cu Cl Co DESCRIPTION
release-notes      –  ●  ●  ·  Write the release notes for a new version from the commits since the…

Cu, Cl and Co are Cursor, Claude Code and Codex. The dot under Co is the gap. show tells you the command that fixes it. This is a real skill on my Mac, a reminders skill I keep in ~/.claude/skills:

skillscout show remindme
Available in
  ● Cursor  ~/.claude/skills
  · Codex   missing  skillscout add remindme --to codex

list and show only check the agents turned on in Skill Cabinet’s settings. On my Mac that’s Cursor and Codex, so Claude Code has no column there.

In the app, click Add to Codex. From the terminal, run the command show printed:

skillscout add release-notes --to codex
Linked release-notes into ~/.codex/skills for Codex

Now skillscout list --missing prints No skills match., and the Codex icon on that row lights up in the app. Running the same add again does nothing and says so:

release-notes already works in Codex. It loads it from ~/.codex/skills.

skillscout add release-notes --all adds it to every agent you use that’s missing it.

The other direction works the same way. For the skill in the screenshot, which lives in ~/.agents/skills, click Add to Claude Code and Skill Cabinet links it into ~/.claude/skills.

Check that it’s one file

Where it lives, in the app or in skillscout show, lists every copy and where each link points. My flavioify writing skill lives in ~/.agents/skills and is linked into three other agents:

Where it lives
  Created 16 September 2026
  Shared       ~/.agents/skills/flavioify
  Cursor       ~/.cursor/skills/flavioify → ~/.agents/skills/flavioify
  Claude Code  ~/.claude/skills/flavioify → ~/.agents/skills/flavioify
  Codex        ~/.codex/skills/flavioify → ~/.agents/skills/flavioify

ls -ld shows the same thing. The real folder starts with d, a link with l and an arrow:

ls -ld ~/.agents/skills/flavioify ~/.codex/skills/flavioify
drwxr-xr-x@ 7 flaviocopes  staff  224 Nov  4 15:54 /Users/flaviocopes/.agents/skills/flavioify
lrwxr-xr-x@ 1 flaviocopes  staff   43 Oct  7 19:35 /Users/flaviocopes/.codex/skills/flavioify -> /Users/flaviocopes/.agents/skills/flavioify

If two entries are both d, you have two copies. Skill Cabinet compares their content, and when they differ it warns that editing one won’t update the others. Read both before you delete one, because the older copy may have an instruction the newer one lost.

Edit it once

Under SKILL.md, Edit opens the file in Skill Cabinet and Open in editor opens it in your default editor. Both edit the one real file, so the next new chat in Claude Code, Codex or Cursor reads the change.

Rename… renames the skill’s folders in your skills folders, re-creates the links under the new name, and updates name in SKILL.md, so all the agents keep finding it.

Plugin skills get copied

A skill that came with a plugin shows Copy to Codex instead of Add to Codex. Plugin updates replace their folders, so a link could break, and Skill Cabinet copies the folder into the agent’s skills folder instead. That copy doesn’t get the plugin’s later changes.

In Where it lives, Remove next to a link takes it out of that one folder and leaves the original in place. Uninstall this skill moves every copy and link to the Trash. Both move what they remove to the Trash, and the confirmation says which agents will stop loading the skill. Remove on the original folder takes its links with it, since they’d point to nothing.

Get Skill Cabinet

Find agent skills on your Mac, see which agents load each one, share them across folders, and track how often you use them.

See Skill Cabinet → · Read the docs · $20. See the app page for tax details, with full source code.

More tutorials for my apps →

Want me to talk about your product? You can sponsor this site.