Share one agent skill between Claude Code, Codex and Cursor

A skill you wrote for Claude Code loads in Cursor, and Codex misses it. You want Claude Code, Codex and Cursor to share that one skill, so the next edit lands in all three.

A skill is a folder with a SKILL.md file. It teaches an agent one task. The free AI Agent Skills course is where that file gets written: the name, the description, the steps, and what the skill should refuse to do. Skills, prompts and rules is the lesson that separates a skill from a rules file. This tutorial starts after the folder exists.

Project rules are the other shared file. AGENTS.md lives in the repo, and the agents that read it already share those rules. A skill is a procedure for one kind of task, and each agent looks for it in its own folders. Copying the folder into each one gives you three files that drift apart.

What you need

Skill Cabinet runs on macOS 15 or later, on Apple silicon and on Intel. After purchasing it, connect GitHub in Polar, accept the private repository invitation, and download the app from Releases. Unzip it and drag Skill Cabinet to your Applications folder. It’s signed with an Apple Developer ID and notarized.

You also need Claude Code, Codex and Cursor on the Mac, and one skill you already use. I’ll call that skill release-notes. Yours will have its own name.

Skill Cabinet reads skills on your Mac. There’s no account. Listing skills and linking a folder stays on the machine. Your chats leave the Mac only if you use the AI features, through your own Claude Code or Codex login. This walkthrough doesn’t use those.

The skillscout command ships inside the app. We’ll use it at the end, to list what is still missing.

See which agents already load the skill

Open Skill Cabinet. It knows eight agents: Cursor, Claude Code, Codex, Gemini CLI, OpenCode, Droid, Pi and Amp. Copies of one skill are grouped under one name, and each row shows the agents that load it.

The toolbar filter can show your own skills, the ones that came with plugins, the ones built into Cursor and Codex, or all of them. Choose your own skills. Built-in skills already belong to the agent that shipped them.

Find release-notes. In the example, you wrote it for Claude Code, so the row shows Claude Code and Cursor, with Codex still missing from the icons.

That split is how the folders work. Six of the eight agents share ~/.agents/skills. Cursor and OpenCode also load ~/.claude/skills. Claude Code and Amp only read their own folder. Codex is one of the six that share ~/.agents/skills, so it does not read Claude Code’s folder. A skill you wrote for Claude Code loads in Cursor, and Codex misses it.

Missing somewhere lists every skill that at least one agent can’t see. release-notes belongs on that list until Codex has it.

Link the folder into the agent that’s missing

Select release-notes. Click Add to and choose Codex.

Skill Cabinet links the skill folder into Codex’s skills folder. You should then see Codex on that row, next to Claude Code and Cursor. There is still one SKILL.md. Edit that file and all three load the change.

The other direction uses the same button. Say the skill already lives in ~/.agents/skills. Codex and Cursor can read that folder. Claude Code can’t, because Claude Code only reads its own folder. Click Add to and choose Claude Code. The row should gain Claude Code, and the file stays the one you already had.

You can stop once Claude Code, Codex and Cursor are on the row. Amp, Pi, Droid, Gemini CLI and OpenCode can wait until you use them. Missing somewhere keeps listing those gaps.

Edit it once and check all three

Open the skill’s SKILL.md in Skill Cabinet. Change one line you can recognize, like a sentence at the top of the steps, and save.

Then ask Claude Code, Codex and Cursor to use release-notes on a tiny task. You should see that same sentence from each one. If you edit the file in your own editor, edit the original folder, the one Add to linked. A second copy you made by hand is a different file.

A rename stays in one place too. Rename the skill in the app and it moves the folders and the links, so the three agents keep loading it under the new name.

Check the gap from the terminal

When you want the list without opening the window:

skillscout list --missing

After Codex can see release-notes, that skill should drop off the list for the agents you care about. Another agent you never installed can still appear. Add it only if you use that agent.

For a script, ask for JSON:

skillscout list --missing --json

If something looks wrong

If Cursor has the skill and Codex doesn’t, you’re in the Claude Code case. Click Add to and choose Codex. Dropping a second copy into ~/.agents/skills by hand leaves two SKILL.md files, and an edit in one doesn’t change the other.

If Claude Code still can’t see a skill that sits in ~/.agents/skills, that folder isn’t on Claude Code’s list. Click Add to and choose Claude Code.

If you linked the wrong agent, click Remove. That takes the skill out of one folder and undoes an Add to. Uninstall this skill is the wider command. It moves every copy to the Trash, links included, and it tells you first which agents will stop loading the skill. Use Remove when you only meant to undo a share. You can put a trashed skill back from the Trash.

If the shell says skillscout: command not found, do the same steps in the window. Missing somewhere and Add to are there.

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 → · $20 including tax, with full source code.

More tutorials for my apps →

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