Chapter 5. Moving Skills — A Weekly Review in One Line with $weekly-review
Required Read this to follow this stage.One-line summary: Codex skills use the same format (
SKILL.md) as Claude Code, and only differ in where you put them and the symbol you use to call them. The folder is.agents/skills, and you call them with$name. You will move three skills from your note-organizing tool, create a weekly review with a single line ($weekly-review), and check it against the original notes.
This chapter is based on the Codex official docs checked on November 1, 2026, and the hands-on test for this guide (run in the Codex terminal). What skills are and why you use them are explained in Claude Code Chapter 7.
Same Format, Different Location
A Codex skill is also a folder containing a SKILL.md file, and SKILL.md must include a name and a description.[1] Skills follow an open standard shared across multiple tools.[2] That is why we moved the SKILL.md files made in Claude Code without changing them.
What differs is where you put them and how you call them.
| Claude Code | Codex | |
|---|---|---|
| This folder only | .claude/skills/ | .agents/skills/ |
| All my folders | ~/.claude/skills/ | ~/.agents/skills/ |
| How to call | /name | $name |
Source: Codex official docs[3][4]
We tested this before moving them. When we called $weekly-review while the files were still in .claude/skills, Codex could not find it right away in the skill list and instead found SKILL.md by searching files. It found the skill this time, but putting it in the expected place is much more reliable.
Quick check
In Codex, what is the right place to put a skill for your organizer folder only, and how do you call it?
Moving the Skills
We asked Codex:
Copy the 3 skills in the .claude/skills folder to .agents/skills, where Codex reads them. Leave the original folder as it is.It was blocked. This happened because of the protected folders we saw in Chapter 4. Inside a workspace folder, .agents is read-only by default.[5] Codex reported that the copy was blocked and showed the commands to run instead.
mkdir -p .agents/skills
cp -R .claude/skills/meeting-notes .claude/skills/study-notes .claude/skills/weekly-review .agents/skills/Here is what the two lines mean.
mkdir -p .agents/skills: Creates the.agents/skillsfolder.mkdirmeans "make a folder," and-pmeans "create any in-between folders at once, and just move on if it already exists."cp -R source1 source2 source3 .agents/skills/: Copies the three skill folders into.agents/skills/.cpmeans "copy," and-Rmeans "including all the files inside the folder." The original folders stay as they are.
This guide ran the exercise not in the app but in the terminal. It used a mode where the approval method is set in advance so Codex does not ask, so Codex could not ask for permission and simply stopped (we cover this mode in Chapter 7). This guide could not directly verify how this moment looks in the app. If an approval screen pops up, read what is being written and where before you decide.
For this guide, we ran the commands Codex gave us ourselves to copy the files. Open the macOS Terminal, go into the folder with cd ~/hello-ai-practice/organizer, and type the two lines above. If you are new to the terminal, see Claude Code Chapter 10 first.
After moving them, you should see three folders under .agents/skills: meeting-notes, study-notes, and weekly-review.
Quick check
When you asked Codex to copy a skill into .agents/skills, it replied that it was 'blocked because it is read-only.' What is the right way to handle this?
Calling with $
You can type $ in the message box to pick and call a skill.[6] This time, we sent only the skill name.
$weekly-reviewAfter the copy was done, Codex opened .agents/skills/weekly-review/SKILL.md right away without searching files. Then it gathered the three reflection notes and created a weekly review.
Result: Weekly review made with a skill
We checked the numbers and facts against the original notes.
| Original note | Weekly review | Match? |
|---|---|---|
| 12 likes | 12 | Match |
| Wrote the price wrong as 6,000 won | 6,000 won error | Match |
| 4 sets today | 4 | Match |
| 11 sets total this week | 11 | Match |
| Posted all 3 times on Instagram | 3 times | Match |
| Mulled wine cost: 1,800 won | None | Missing |
| Bought and replaced a light bulb | None | Missing |
| 2 hours spent writing copy | None | Missing |
Source: Hands-on results from this guide (2026-11-01)
Nothing was wrong, but three items were missing. They seem to have been left out because they did not fit neatly into the three sections of the review format (What went well, What could be better, To do next week). Always check not only what is wrong, but also what is missing. If there is something that must not be left out, you can add a single line to the skill, such as: "Put numbers for the next meeting agenda, like the mulled wine cost, under To do next week."
Even if you do not call a skill by name, Codex can pick it on its own when your request matches the skill description.[7] That is why it helps to clearly write when to use it near the beginning of the description.[8]
Quick check
In the weekly review made with $weekly-review, all the numbers were right, but the mulled wine cost of 1,800 won was left out. What next step does this guide recommend?
Making New Skills and Plugins
When you make a new skill from scratch, call the built-in $skill-creator skill and explain your goal, steps, and format.[9] The official docs recommend starting with tasks where the steps and format always stay the same, like a weekly report or a meeting follow-up.[10] The three skills in our note-organizing tool are exact examples of this.
You do not need a plugin for this exercise. Just learn the name and what to watch out for. A plugin is an installable bundle that packages skills together with external tool connections.[11][12] The docs say to review plugin hooks (scripts that run automatically) and decide whether you trust them before they run.[13] For any plugin you are seeing for the first time, check who made it and what permissions it needs first, just as you learned in Claude Code Chapter 7.
Quick check
You are about to install a plugin you have never seen before. What do the official docs emphasize?
Try It Yourself
- Ask Codex to copy the three skills from
.claude/skillsto.agents/skills. If it asks for permission, read the details and decide; if it gets blocked, type the two-line command from this chapter directly in the terminal (you can also use the app menu "View → Open Terminal"). - Open a new chat and type
$in the message box to check that all three skills appear. - Send
$weekly-reviewand check the result against the original notes. Count wrong items and missing items separately. - If anything is missing, add one line to the skill and run it again.
Up next: In Chapter 6, we will look at scheduling the weekly review to run automatically every Friday, along with the cloud and mobile features.
Summary
- The skill format (
SKILL.md) is the same as in Claude Code. The location is.agents/skills, and you call skills with$name. - Because
.agentsis a protected folder, moving files there may be blocked or require permission (this guide only verified being blocked in the terminal). - A single line,
$weekly-review, produced the weekly review. Five items matched and three were missing. - Check not only what is wrong, but also what is missing. If it keeps happening, update the skill.
Glossary
| Term | One-line meaning |
|---|---|
$ mention | How you call a skill by name in Codex |
.agents/skills | Where Codex looks for skills in this folder |
| skill-creator | A built-in skill that helps you make new skills |
Finished this chapter?
Progress is saved only in this browser. See your progress on the full table of contents.
Next chapter: Chapter 6. Schedule, Cloud, and Mobile
References (13)
Codex official docs, "Build skills". "A skill is a directory with a
SKILL.mdfile plus optional scripts and references. TheSKILL.mdfile must includenameanddescription." learn.chatgpt.com (checked on 2026-11-01) ↩︎Codex official docs, "Build skills". "Skills build on the open agent skills standard." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Build skills". "For repositories, Codex scans
.agents/skillsin every directory from your current working directory up to the repository root." / "$HOME/.agents/skills
Any skills checked into the user's personal folder." learn.chatgpt.com (checked on 2026-11-01) ↩︎Codex official docs, "Skills & Plugins". "ChatGPT supports
@mentions, while Codex supports$mentions for skills." learn.chatgpt.com (checked on 2026-11-01) ↩︎Codex official docs, "Agent approvals & security". "
<writable_root>/.agentsis protected as read-only when it exists as a directory." learn.chatgpt.com (checked on 2026-11-01) ↩︎Codex official docs, "Slash commands". "You can also explicitly invoke skills by typing
$in the chat composer." learn.chatgpt.com (checked on 2026-11-01) ↩︎Codex official docs, "Build skills". "Implicit invocation: ChatGPT or Codex can choose a skill when your task matches the skill
description." learn.chatgpt.com (checked on 2026-11-01) ↩︎Codex official docs, "Build skills". "Front-load the key use case and trigger words so a host can still match the skill if descriptions are shortened." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Skills & Plugins". "In ChatGPT, start with
@skill-creator; in Codex, use$skill-creator." learn.chatgpt.com (checked on 2026-11-01) ↩︎Codex official docs, "Skills & Plugins". "Good first skills include a weekly update, a campaign brief, a meeting follow-up, or any task where the steps and format should stay consistent." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Skills & Plugins". "A plugin is an installable bundle that can include skills and Model Context Protocol (MCP) servers." learn.chatgpt.com (checked on 2026-11-01) ↩︎
ChatGPT and Codex share a single plugin list. Codex official docs, "Skills & Plugins". "ChatGPT and Codex share one universal plugin directory." learn.chatgpt.com (checked on 2026-11-01) ↩︎
Codex official docs, "Plugins". "Review and trust plugin hooks before they run." learn.chatgpt.com (checked on 2026-11-01) ↩︎