The short answer
- 1Folders:
~/.claude/skills·~/.agents/skills(legacy~/.codex/skillstoo) ·~/.cursor/skills - 2Start one:
/namein Claude Code or Cursor ·$namein Codex ·@nameadds it to a Cursor chat - 3List installed Skills:
/skills· Customize → Skills in Cursor - 4Install:
npx --yes fable5-cli@latest install <slug>, plus--agent claude-codefor Claude Code
Where each agent keeps Skills
A personal Skill works in any project you open. A project Skill is stored in the repo and travels with every clone.
| Agent | Your own | In the repo |
|---|---|---|
| Claude Code | ~/.claude/skills/ | .claude/skills/ |
| Codex | ~/.agents/skills/ (legacy: ~/.codex/skills/) | .agents/skills/ in the working directory and each parent, up to the repository root |
| Cursor | ~/.cursor/skills/, ~/.agents/skills/ | .cursor/skills/, .agents/skills/ |
Which copy wins on a name clash, and every folder per agent: Skill locations.
Skill commands for Claude Code, Codex and Cursor
The fastest install check is to start the Skill by its name. When it runs, the agent has found it.
| Task | Claude Code | Codex | Cursor |
|---|---|---|---|
| Show Skills | /skills | /skills | Customize → Skills |
| Start one | /name | $name | /name, @name |
| Skill from a plugin | /plugin:name | Through a plugin | Through a plugin |
| Keep it active | — | — | Option/Alt+Enter (Custom Mode) |
| After an edit | Seen right away; /reload-skills for a brand-new folder | Seen right away; restart if not | Reload the window or open a new chat |
Frontmatter fields in SKILL.md
Every Skill has a SKILL.md file whose settings sit at the top, between a pair of --- lines. The fields below change how an agent handles the Skill.
| Field | Limit or effect | Claude Code | Codex | Cursor |
|---|---|---|---|---|
name | Up to 64 characters: lowercase letters, digits, hyphens; matches its folder | Optional | Required | Required |
description | Up to 1,024 characters; what it does and when it applies | Recommended | Required | Required |
allowed-tools | Lets it use tools without asking; the spec marks it experimental | Yes | — | — |
paths | Starts by itself only when files match these patterns | Yes | — | Yes |
The Frontier Brief CLI commands
The Frontier Brief CLI fetches a Skill from The Frontier Brief and drops it into the folder your agent reads.
| Command | What happens |
|---|---|
fable5-cli login | Opens the browser so you can approve a sign-in code |
fable5-cli status | Prints the account and plan you are signed in with |
fable5-cli install <slug> | Puts the Skill in ~/.agents/skills/<slug>/ |
--agent claude-code | …uses ~/.claude/skills/<slug>/ in its place |
--target <dir> | …uses whatever Skills folder you name, such as .claude/skills |
--force | Swaps out a copy already there, keeping the old one as a backup |
fable5-cli logout | Ends the sign-in and cancels it on the server |
Put npx --yes fable5-cli@latest in front of each command. It needs macOS or Windows and Node.js 22 or newer. --agent and --target can't be combined.
Common questions
Which Claude Code commands work with Skills?
/skills shows what you have, /skill-name starts one, /plugin-name:skill-name starts a Skill bundled with a plugin, and /reload-skills loads a Skills folder you only just made.
Where can I read how the agents differ?
Compare agents goes through the same facts with examples.
Sources
Did this guide help?
