migrate-to-codex

Convert Claude Code assets into Codex formats with migration plans.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jbarlek3-web/claudecommandcenter --skill migrate-to-codex-jbarlek3-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-codex
Source: https://github.com/jbarlek3-web/claudecommandcenter/tree/main/skills/.curated/migrate-to-codex
Command: npx skills add https://github.com/jbarlek3-web/claudecommandcenter --skill migrate-to-codex-jbarlek3-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Migrate Claude Code assets (instructions, skills, agents, and MCP config) into Codex project and global files.

Core Features & Use Cases

  • Convert Claude instruction sources (CLAUDE.md, AGENTS.md) and all skills/commands into Codex-friendly formats.
  • Transform Claude Code MCP/config into .codex/config.toml and enable Codex hooks when appropriate.
  • Produce migration plans with dry-run support, validation, and manual-review guidance for non-migrated content.

Quick Start

Run the migrate-to-codex tool with your Claude sources and a Codex target to generate Codex artifacts.

Frequently Asked Questions about migrate-to-codex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Claude Code instructions and agents to Codex?

Migrating Claude Code instructions and agents to Codex involves converting CLAUDE.md and AGENTS.md sources into Codex artifacts. It transforms skills, commands, and MCP config into Codex project and global files automatically.

Can I convert Claude Code MCP config into .codex/config.toml?

Yes, you can convert Claude Code MCP config into .codex/config.toml. The migration transforms your Claude Code configuration and enables Codex hooks when appropriate, preserving your existing setup in the new format.

Does the Claude Code to Codex migration support a dry-run?

Yes, the Claude Code to Codex migration supports a dry-run. It produces a detailed migration plan with validation and manual-review guidance, allowing you to verify targets and review non-migrated content before finalizing.

What is the best way to handle non-migrated content when moving to Codex?

The best way to handle non-migrated content when moving to Codex is using the migration tool's manual-review guidance. It preserves non-migrated content as guidance within the generated Codex artifacts for later review.

Does Codex migration work for both global and project scopes?

Yes, Codex migration works for both global and project scopes. The tool validates targets and generates Codex artifacts tailored to the specified scope, ensuring your Claude Code assets are correctly placed.