The Practice Room / Codex / Episode 4
How to use skills in Codex
Codex comes with skills already in it, and one of those skills exists only to build you more of them.
The short answer
Codex comes with skills already in it, and one of those skills exists only to build you more of them. Type /skills to see what you have. Type a dollar sign and the name of the skill to call one. That is the whole system.
The part that trips people up is the naming, so it is worth saying plainly before anything else: a skill is called by its own name.
Skills in Codex, the full guide
Five pages. Every command, where skills live on your computer, and a prompt you can copy to build your first one. Yours to keep and to pass on.
Getting in
Codex runs inside Command Prompt. Open Command Prompt, walk into the folder you want to work in with cd, and then type codex. It opens in that folder and nowhere else, which is why the cd step matters more than it looks.
Codex takes over that same window. The arrow near the bottom is where everything you type goes, and the blue line underneath tells you which model you are on and which folder you are in.
Finding a skill, and calling one
Type /skills at the arrow. A list comes up from the bottom of the window with everything available to you, each one with a line saying what it does. Use that route when you cannot remember the name.
If you already know it, skip the list. Type a dollar sign and the name of the skill itself, then your request on the same line.
The name is just the name
The two that build
You go through the list and the thing you need is not in it. That is what the next two are for, and they are the only two whose names begin with the word skill.
$skill-creator builds a new skill, or improves one you already have. It asks you what the skill does, when it should kick in, and whether plain instructions are enough or it needs scripts as well. $skill-installer brings in a skill somebody else already made. Everything else in that list is just its own name.
What a skill actually is
A folder with your instructions in it. At minimum a file called SKILL.md that says what the skill is for and how the work should be done; it can also carry scripts and reference files. Keep it in .agentsskills inside a project and only that project sees it. Keep it in .agentsskills in your user folder and you have it everywhere.
The point of all of it is that work you explain once becomes work you never explain again.
Do it yourself
- Open Command Prompt, cd into a practice folder, and type codex.
- Type /skills and read what you already have. Note the names: no prefix on any of them except the two builders.
- Call $skill-creator and describe one job you keep explaining over and over.
- When it is finished, type /skills again. Yours is in the list now.
- Call it by its name and give it real work. If the result misses something, tell $skill-creator what was wrong and have it revise the skill rather than fixing the answer by hand.
Check yourself
You type /skills at a plain C:> prompt and nothing happens. Why?
You are still talking to Windows. Slash commands belong to Codex, so Codex has to be running first. Type codex, wait for the arrow, then type it there.
Is $skills how you list them?
No. $skills is not a command. The dollar sign calls one skill by name; the slash command /skills is what opens the list.
You made a skill yesterday and today it is not in the list. Where did it go?
Check where it was saved and where you started Codex. A skill saved inside one project belongs to that project only. Put it in the .agentsskills folder in your user folder if you want it in every project.
What to carry forward
The habit worth building is not memorising skill names. It is noticing when you are explaining the same thing for the third time, and turning that explanation into a skill while you still remember what you wanted.
Words used here
Go deeper
What she says in the film
Codex comes with skills already in it, and one of those skills exists only to build you more of them.
You start in Command Prompt. You walk into the folder you want to work in with cd, and then you type codex. That is what opens it, in that folder and nowhere else.
Codex takes over the same window. The arrow near the bottom is where everything you type goes, and the blue line underneath tells you which model you are on.
Type slash skills at that arrow. A list comes up from the bottom, every skill you have, each one with a line saying what it does.
To call one, type a dollar sign and the name of the skill itself. Dollar pdf. Dollar excel. Dollar github. The name is just the name.
Now the one people miss. Skill creator is itself a skill, and what it builds is other skills. So when you go through that list and the thing you need is not in it, you call skill creator and you make it.
Two of them start with the word skill and only two. Skill creator builds a new one. Skill installer brings in one that already exists. Everything else is just its own name.
A skill is a folder with your instructions in it, so the thing you explain once is a thing you never explain again. I wrote the whole of this up as a guide. If you want it, write PDF in the comments and I will send it to you.
Subscribe.
[no_permission] No permission required.
Book a session and we do it together on a call.
Book an hourAsk what did not make sense
Comments go through our own form and are read before they appear. Links are not allowed; describe it in words.
More from Codex.

Codex, installed in one line
Codex is OpenAI's assistant. It does the same kind of work Claude Code does.

Can Codex in the terminal generate images?
Last time we installed Codex. Today it makes something different.

What goes in an AGENTS.md file?
Codex forgets everything about your project the moment you close the window.
Get the next walkthrough.
One email when something goes up. The argument, the film and the term, nothing else. One click to leave.
Have a question now? Ask Mstimaj, she knows the archive.