How to install a skill in Claude Code and Codex
Short answer: A skill is a folder with a SKILL.md file. To install one, copy the folder into .claude/skills/ for Claude Code or .agents/skills/ for Codex, then start a session and check it loads. Use your home folder (~/.claude/skills/, ~/.agents/skills/) to make it available in every project.
Written by the Buy Agent Skills team. Updated 17 November 2026. Folders and commands checked against the Claude Code and Codex documentation on 17 November 2026.
New to the idea? Read what are agent skills first.
Before you start
- Unzip the skill or pack. You should see a folder per skill, each with a
SKILL.md. - Open one
SKILL.mdand read it. It is plain text and it tells your agent what to do. See how to check a skill before installing if it is from someone you do not know.
Claude Code
For one project (from the project root):
mkdir -p .claude/skills
cp -r path/to/my-skill .claude/skills/my-skill
For all projects:
mkdir -p ~/.claude/skills
cp -r path/to/my-skill ~/.claude/skills/my-skill
Check it loaded:
- Start Claude Code (or keep your session; edits to existing skills are picked up live).
- Type
/and look for the skill name, or run/skillsfor a list. - If you created the
.claude/skills/folder while a session was already open, run/reload-skills. - Call it with
/my-skill, or ask for a task that matches its description and it should load by itself.
Codex
For one project (from the repo root):
mkdir -p .agents/skills
cp -r path/to/my-skill .agents/skills/my-skill
For all projects:
mkdir -p "$HOME/.agents/skills"
cp -r path/to/my-skill "$HOME/.agents/skills/my-skill"
Check it loaded: Codex detects new skills automatically. In the CLI, run /skills or type $ and look for the skill in the list, or run a task that matches its description. If it does not appear, restart Codex.
Installing a whole pack
A pack is several skill folders in one zip. Copy each skill folder (not the zip's outer folder) into the skills directory, so each has its own SKILL.md directly inside. Our packs include a README with the exact steps for that pack.
If it does not trigger
- Folder path.
SKILL.mdmust sit directly inside<skills-folder>/<skill-name>/. One extra folder level is the most common mistake. - Description. The agent uses the
descriptionline to decide when to load a skill. If it is vague, call the skill by name or make the description more specific. - Frontmatter. The
---blocks at the top must be valid YAML. A stray tab or quote breaks it. - Settings. In Claude Code, a skill with
disable-model-invocation: trueonly runs when you call it by name. - Restart. If Codex does not show a new skill, restart Codex.
Which of our packs work where
Each pack page states what it has been tested in. Check works with Claude Code and works with Codex before you buy. Today, Marketing Foundations Pack and Marketing Copy Pack are text skills; Cartoon Films is a larger pipeline that needs macOS on Apple Silicon and Blender and has been tested with Claude Code only. We do not say "works with" until someone has run it. See how we test.
FAQ
Do I need to restart the agent? Claude Code picks up edits to existing skills during a session; use /reload-skills after creating a new skills folder. Codex detects skill changes automatically; restart it if a change does not appear.
Can the same folder serve both tools? Yes, if the skill uses only name and description. Copy it to both locations. See Codex vs Claude Code skills.
Project or personal install? Project install keeps a skill with one repo and lets teammates share it. Personal install makes it available everywhere on your machine.
Is it safe to install any skill? A skill can tell the agent to run commands. Read it first.