migrate-to-codex

Convert Claude Code instructions, skills, agents, and MCP config into Codex artifacts.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Canepro/codex-skills --skill migrate-to-codex-canepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-codex
Source: https://github.com/Canepro/codex-skills/tree/main/skills/migrate-to-codex
Command: npx skills add https://github.com/Canepro/codex-skills --skill migrate-to-codex-canepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the migration of Claude Code constructs (instructions, skills, agents, and MCP config) into Codex-compatible artifacts.

Core Features & Use Cases

  • Convert Claude Code instructions, skills, and subagents into Codex formats and project config.
  • Migrate MCP/settings and generate .codex/config.toml with compatibility notes and manual-review guidance.
  • Enable plan/doctor workflows to validate artifacts before final migration.

Quick Start

Run the migrator to convert Claude Code surfaces (instructions, skills, subagents, and MCP config) into Codex-compatible 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 assets to Codex?

To migrate Claude Code assets to Codex, use this tool to convert instructions, skills, agents, and MCP config into Codex-compatible artifacts. It generates .codex/.agents outputs along with a validation plan.

What is the process for converting Claude Code subagents into Codex formats?

Converting Claude Code subagents into Codex formats involves transforming project and global scope configurations into .codex/config.toml files. The migration includes generating compatibility notes and manual-review guidance for validation.

Does the Claude Code to Codex migration support MCP config and settings?

Yes, the Claude Code to Codex migration supports MCP config and settings. It migrates these settings and generates the necessary .codex/config.toml file, providing compatibility notes for manual review.

Can I validate Codex artifacts before completing the migration from Claude Code?

Yes, you can validate Codex artifacts before completing the migration from Claude Code. The tool enables plan and doctor workflows to validate migrated instructions, skills, and agents before finalizing.

What's the best way to scale Codex-based automation after migrating from Claude Code?

The best way to scale Codex-based automation after migrating from Claude Code is to convert all project assets into Codex formats with optional hooks and references. This enables full automation and scaling capabilities.

Are there limitations when migrating global and project scope Claude Code assets to Codex?

A key limitation when migrating global and project scope Claude Code assets to Codex is the need for manual review. The tool generates compatibility notes and validation artifacts to guide necessary manual adjustments.