Agent skill · software engineering · openai
migrate-to-codex
Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files.
Why this skill is useful
Adds a comprehensive migration script that automates the transfer of configurations and artifacts to Codex, which the AI cannot generate on its own.
What it needs
Requires codex-cli installed locally. About 4k tokens when loaded. Last updated 2026-07-14. 24,594 stars on the source repository.
What this skill does
Migrate to Codex Autonomy Keep going until the selected migration is completely done: run the migrator, inspect the report, fix migrated Codex instructions/skills/agents/MCP config, and re-run checks without stopping to ask for confirmation of the next step. If the user has selected a target, do not ask before creating, editing, replacing, or deleting generated Codex artifacts in that target (AGENTS.md, .codex/, .agents/, or ~/.codex/). Preserve unrelated existing Codex config entries in .codex/config.toml or ~/.codex/config.toml, such as notify, projects, marketplaces, or unrelated MCP servers; do not ask about them unless they fail validation or directly conflict with the migration. Do not edit source Claude Code files (.claude/, ~/.claude/, .mcp.json, or .claude.json), unrelated project code, secrets, or another repository. Migration Order Run the migration in this order for each selected global or project source: 1. Start by using Codex's built-in TODO/task list tool. Do not create MIGRATIONTODOS.md or any TODO file unless the user explicitly asks. The TODO list input has a plan array whose items each have step and status; use statuses pending, inprogress, and completed. Make the TODOs specific to the selected artifacts. Before finishing, update the TODO list so every finished step is marked completed and no step remains inprogress. Use literal source → Codex target labels, for example: Inspect .claude/commands → Codex skills/prompts Inspect .claude/agents → .codex/agents Inspect .mcp.json → .codex/config.toml MCP servers Inspect .claude/settings.json hooks → .codex/hooks.json Migrate safe selected artifacts → Codex files Validate generated .codex/config.toml Validate generated .codex/agents Report migrated artifacts and manual-review items 2. Read references/differences.md (and refresh Codex docs if its Docs last checked date is old). 3. Scan and inspect before writing: --scan-only lists active and inactive source surfaces. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills openai/migrate-to-codex