How to Use OpenAI Codex Skills with Claude Code

To use OpenAI Codex from inside Claude Code, install a bridge skill: `codex` (3,824 installs, skills.sh registry) lets Claude Code call the Codex CLI directly for code analysis and refactoring. Interest in running the two agents together is rising, and the catalog now carries skills that connect them.

Key takeaways

• codex (3,824 installs, 2,175 GitHub stars, softaworks, skills.sh registry) lets Claude Code delegate analysis, refactoring, and automated edits to the OpenAI Codex CLI.
• chatgpt-codex-onboarding (2,260 installs, 18 GitHub stars) connects a ChatGPT or Codex subscription over OAuth device-code login, with no API key exposed.
• codex-history-ingest (2,136 installs, 2,823 GitHub stars) parses local Codex session history for pattern analysis and agent improvement.
• Skills are portable SKILL.md instruction files; browse the full ranked set on the leaderboard.

Can Claude Code use OpenAI Codex?

Yes, through a bridge skill. The `codex` skill (3,824 installs, skills.sh registry) teaches Claude Code to call the OpenAI Codex CLI for code analysis, refactoring, and automated editing inside an agent workflow. Instead of choosing one agent, you let Claude Code orchestrate and hand specific tasks to Codex.

What is the best Codex skill for Claude Code?

The best pick is `codex` (3,824 installs, 2,175 GitHub stars, softaworks, skills.sh registry). It is the most-installed Codex bridge in the catalog and covers the core delegate-to-Codex loop. To wire up authentication, add `chatgpt-codex-onboarding` (2,260 installs), which handles login. See the install a skill guide for setup.

How do you connect a Codex subscription without an API key?

Use `chatgpt-codex-onboarding` (2,260 installs, 18 GitHub stars, skills.sh registry). It connects an existing ChatGPT or Codex subscription to an agent through secure OAuth device-code login, so you reuse a paid plan instead of managing a separate API key. This lowers the barrier to running Codex from inside Claude Code.

What can you do with Codex session history?

`codex-history-ingest` (2,136 installs, 2,823 GitHub stars, skills.sh registry) reliably ingests, parses, and queries local Codex session history. That turns past runs into a dataset for spotting patterns and improving how your agents work, a useful complement once Codex is part of your workflow.

How does this compare to other cross-agent skills?

Bridging agents is a broader pattern. The Gemini CLI skills guide covers the same idea for Google's agent, and the catalog of 60,632 skills (skills.sh registry) includes many such connectors. Understanding what Claude Code skills are helps you judge which bridges are worth installing.

A complete starter stack

• codex (3,824 installs) - call the Codex CLI from Claude Code.
• chatgpt-codex-onboarding (2,260 installs) - OAuth login for a Codex subscription.
• codex-history-ingest (2,136 installs) - parse and query past Codex sessions.

Common pitfalls

• Expecting a SKILL.md file to install Codex itself; these skills bridge to an existing Codex CLI, they do not replace it.
• Managing a separate API key when chatgpt-codex-onboarding can reuse your subscription over OAuth.
• Running two agents with no coordination instead of letting Claude Code orchestrate and delegate.

Install codex first, connect your subscription with chatgpt-codex-onboarding, and let Claude Code delegate the right tasks.

The OpenAI Codex documentation is the authoritative reference for the underlying CLI these skills call.

Common questions