Install agent skills in OpenAI Codex
Add a skill to Codex in the CLI, the IDE extension or the ChatGPT desktop app, find it with /skills and call it with $skill-name. Repo and personal folders.

Codex reads skills from .agents/skills in your repo and from ~/.agents/skills in your home folder. Skills work in the Codex CLI, the IDE extension and the ChatGPT desktop app.
Short answer: run the skill's npx line with -a codex in your repo, type /skills to find it, then mention it with $skill-name or just ask for the job.
What you need
Step 1: Choose a repo or personal skill
1 minCodex looks in several places, from the folder you work in up to your home folder.
- Repo:
.agents/skills/in the folder you work in, or any folder above it up to the repo root. Commit it to share it with your team. - Personal:
~/.agents/skills/. It applies to any repo you work in. - Admins can also put skills in
/etc/codex/skills, and Codex comes with built-in skills of its own.
If two skills share a name, Codex doesn't merge them. Both can appear when you pick a skill, so give each a different name.
- Repo:
Step 2: Install a free skill with one line
1 minThe skills CLI copies the skill from its maker's GitHub repo into
.agents/skills/.- Open a terminal in your project folder.
- Paste the line from the skill's Recaply page. It ends in
-a codex. - To install it for all your projects instead, add
-g. It then goes to~/.agents/skills/.
The install linenpx skills add <owner>/<repo> --skill <skill-name> -a codex
You should see a new
.agents/skills/<skill-name>/folder withSKILL.mdinside.The CLI asks which agents to install to?
The line is missing its
-avalue. Pick your agent in the list, or run the line again with it. Add-yto skip the questions.Codex can also fetch skills itself:
$skill-installeradds OpenAI's curated skills, such as$skill-installer linear, and can download skills from other repos.Step 3: Or install a premium skill from its ZIP
2 minA premium skill comes as one ZIP that holds a single folder named after the skill.
- On the skill's Recaply page, sign in, buy it (or use the plan), then click Download ZIP.
- Move the ZIP into your project folder and open a terminal there.
- Run the line below. It unzips the folder, then installs it for your agent.
- When it's done, you can delete the ZIP and the unzipped folder: the CLI made its own copy.
Your lineunzip <slug>.zip && npx skills add ./<slug> -a codex
You should see
.agents/skills/<slug>/SKILL.md, with the skill's other files beside it.On Windows, there's no
unzip?Right-click the ZIP, choose Extract All, and move the extracted folder into
.agents/skills/in your project.Unzipping straight into the folder works too:
unzip <slug>.zip -d .agents/skills/.Step 4: Check that Codex sees it
1 minCodex notices new and changed skills on its own.
- In the Codex CLI or the IDE extension, run
/skillsand look for the name. - In the ChatGPT desktop app, open the Skills sidebar to see the skills across your projects.
You should see the skill's name with its description.
A new or changed skill doesn't show?
Restart Codex. It usually picks up changes by itself, and a restart makes it look again.
- In the Codex CLI or the IDE extension, run
Step 5: Run the skill
1 minCodex uses a skill when your task matches its description, or when you mention it.
- In the CLI or IDE extension, type
$and choose the skill, or write$skill-namein your prompt. - In the ChatGPT desktop app, type
@and pick the skill. - Or describe the job in words from the skill's description.
Your prompt$<skill-name> <what you want it to do>You should see Codex follow the skill's steps for your task.
Codex ignores the skill?
Mention it with
$skill-name. If it still doesn't load, check thatSKILL.mdstarts with anameand adescriptionbetween two---lines.- In the CLI or IDE extension, type
Step 6: Not working? Check these
2 minMost problems come from the folder's place or a setting that turned the skill off.
- The skill sits in
.agents/skills/<skill-name>/SKILL.md, the folder Codex's docs name for repos. - Started Codex outside the repo? Repo skills load from your current folder up to the repo root, so start it inside the repo.
- Turned off? Look in
~/.codex/config.tomlfor a[[skills.config]]entry for that skill withenabled = false, remove it, and restart Codex. - A symlinked folder is fine: Codex follows the link when it looks for skills.
- The skill sits in
You get
A skill in Codex that you can call with $skill-name
Try next
Did this guide work for you?
Thanks. It helps us fix the steps.


