migrate-to-codex Skill
Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files. Published by openai in skills.
Decision snapshot
Is this a fit?
Developers using skills, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is migrate-to-codex Skill?
Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files. Published by openai in skills. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using skills
Declared skill metadata
- Source file: skills/.curated/migrate-to-codex/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use migrate-to-codex Skill
- Use it for developers using skills.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/skills
- Skill file: skills/.curated/migrate-to-codex/SKILL.md
What it does
Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files.
Skill instructions
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
Verified compatibility and discovery
Frequently asked questions
What is migrate-to-codex?
migrate-to-codex is a open-source AI agent skill with Copy skill directory. Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files.
Who is migrate-to-codex best for?
migrate-to-codex is best for reusing agent instructions, scripts, and references.
How do I install migrate-to-codex?
Install or run migrate-to-codex using Copy skill directory. Check migrate-to-codex for the latest setup command.
Is migrate-to-codex actively maintained?
migrate-to-codex may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
