AIPM
Theme

Plain-English guide

Can Codex use Claude skills? Paths that work

Codex does not read .claude/skills. The same SKILL.md works in .agents/skills. See the paths and the AIPM install for each tool.

Published September 1, 2026. Last reviewed October 7, 2026.

Short answer

Codex can use a Claude skill, but not from Claude's folder. Codex does not read .claude/skills. Put the same SKILL.md in .agents/skills/<name>/SKILL.md, or run aipm add @scope/name@version --target codex. Claude Code uses --target claude, which writes .claude/skills/<name>/SKILL.md.

Paths that work in Claude Code and Codex.
Claude CodeCodex
Project skill path.claude/skills/<name>/SKILL.md.agents/skills/<name>/SKILL.md
Reads the other tool's folder?NoNo
AIPM installaipm add @scope/name@version --target claudeaipm add @scope/name@version --target codex
Same SKILL.md?Yes, after you install it into this pathYes, after you install it into this path

Words used in this guide

  • AIPM: a tool that installs and updates reusable AI instructions.
  • Package: a named group of files that people can install and update together.
  • Workflow: a set of steps used to finish a task.
  • Git: a tool that records file changes so people can review or undo them.

What this means

The shared idea

A skill gives an AI tool a reusable job description, steps, examples, and optional resources. Keeping one job per skill makes it easier for both people and agents to choose the right workflow.

The important differences

Claude Code and Codex read skills from their own supported locations and apply their own discovery rules. A skill should avoid product-specific assumptions unless it is intentionally made for one tool. Check each product's current documentation before choosing folders or optional fields.

Sharing across a team

Keep shared skill source in Git, review changes, and state which tools were tested. A package can hold common instructions plus target-specific files when the tools need different layouts.

Simple steps

  1. Write one clear task in SKILL.md.
  2. Keep common instructions free of tool-specific wording.
  3. Add separate target files only when behavior differs.
  4. Test the skill in Claude Code and Codex.
  5. Record the tested tools and publish a new version when behavior changes.

Where to go next

If you want to try this in a real project, start with how to use AIPM and the command reference. If you want to share your own workflow, read the publishing guide.

FAQ

Can one SKILL.md work in both Claude Code and Codex?

Often yes, when it contains plain task instructions and uses files both tools can read. Product-specific tools, paths, or commands may need separate guidance.

Does AIPM install directly into Codex?

Yes. aipm add @scope/name@version --target codex writes the skill to .agents/skills/<skill>/SKILL.md with its supporting files, the folder Codex loads project skills from. --target claude writes .claude/skills/<skill>/ for Claude Code.

Sources

Related guides