Walkthrough
Create a Codex Skill with /skill creator
A Codex skill is a saved set of instructions that Codex follows whenever you give it a familiar task. You write the instructions once, and Codex reuses them in every future conversation where that workflow applies.
Use /skill creator from the Codex text input
- 1
Open Codex to a conversation with a workflow worth reusing
- 2
Pick project-level or user-level before you create
- 3
Name the skill and describe when Codex should use it
- 4
Test the skill by running it in a new conversation
A working Codex skill created from inside the app, saved to the right project or user location, and tested in a new conversation.
Follow the setup path in Codex
- 1
Open Codex to a conversation with a workflow worth reusing
Open the Codex app. You can start from a fresh conversation, or open an existing one that already contains a workflow you want to turn into a reusable skill. Starting from an existing conversation lets the Skill Creator study what you already built and shape the skill's instructions around it. Starting fresh works too; you will describe the workflow from scratch in the next steps.
- 2
Pick project-level or user-level before you create
Skills can live in two places. A project-level skill only appears when you are working inside that specific project. It can read the project's files and understands the project's folder structure. A user-level skill is available across every project you open in Codex. Think of the difference like a recipe taped to one specific oven versus a recipe card you carry in your wallet. If the workflow only makes sense for one codebase or folder, open that project first from the Codex sidebar. If you want the skill everywhere, tell the Skill Creator you want a user-level skill when you describe it in the next step.
Tip: After creating the skill, try calling it from the project where you expect to use it. A project-level skill will not appear if you open a different project.
- 3
Name the skill and describe when Codex should use it
Type `/skill creator` in the text input at the bottom of Codex. Describe the workflow you want to save, give it a short lowercase name like `ui-builder`, `meeting-recap`, or `source-auditor`, and add a sentence explaining when the skill should activate. For example: "use when I ask Codex to redesign a UI component from a screenshot." Codex creates a SKILL.md file (a plain-text instruction file that defines the skill) and shows you where it saved it. The name you choose becomes the slash command you type to run the skill later, so pick something short enough to remember and type quickly.
Tip: The skill's description directly controls when Codex auto-selects the skill for a conversation. A vague description like "helps with code" will match too many conversations and fire when you do not want it. A specific description like "redesigns a React component from a screenshot mockup" matches the right ones.
- 4
Test the skill by running it in a new conversation
Open a new conversation in the same project and type the slash command for your skill (for example, `/ui-builder`). You can also type `$ui-builder` inline in your message, or simply write "use the ui-builder skill" in plain English. If you only remember the first few letters, type them after `/` and Codex shows matching skills in a dropdown menu. When you select the skill, Codex loads the saved instructions into the conversation and follows the workflow you defined.
Tip: If the skill was created at the project level, make sure you are inside the correct project before trying to run it. Opening a different project hides project-level skills and removes the local file context they depend on.
Official guidance checked
All official docs referenced on this page were checked to confirm accuracy and current instructions.