migrate-to-codex

Migrates Claude Code skills and slash commands to native Codex artifacts.

64|6|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/zuharz/ccode-to-codex --skill migrate-to-codex-zuharz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-to-codex
Source: https://github.com/zuharz/ccode-to-codex/tree/main/.codex/skills/migrate-to-codex
Command: npx skills add https://github.com/zuharz/ccode-to-codex --skill migrate-to-codex-zuharz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Migrating Claude Code skills to the Codex ecosystem often loses workflow intent through mechanical transliteration. This skill preserves the source behavior while producing native Codex artifacts.

Core Features & Use Cases

  • Preservation-First Migration: Converts Claude skills into Codex skill packages while maintaining control shape, hard constraints, and direct execution patterns.
  • Batch Surface Migration: Migrates project-local Claude slash commands and command hooks into review-required Codex artifacts in batch mode.
  • Risk Classification & Validation: Classifies migration risk (MECHANICAL_SAFE, MANUAL_REVIEW_REQUIRED, REFACTOR_REQUIRED, BLOCKED), validates runtime coupling, and audits nativeness before marking artifacts native.

Quick Start

Use the migrate-to-codex skill to assess, preview, or migrate a Claude skill into the Codex ecosystem with preservation-first workflow intent.

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 skills to Codex without losing workflow intent?

Migrate Claude Code skills to Codex using a preservation-first approach that converts source behaviors into native Codex skill packages while maintaining control shape, hard constraints, and direct execution patterns.

What is the best way to convert project-local Claude slash commands into Codex artifacts?

Convert project-local Claude slash commands into Codex artifacts using batch surface migration, which processes command hooks and outputs review-required native artifacts in batch mode.

How does risk classification work when migrating Claude skills to the Codex ecosystem?

Risk classification for Claude skill migration assigns categories like MECHANICAL_SAFE, MANUAL_REVIEW_REQUIRED, REFACTOR_REQUIRED, or BLOCKED to validate runtime coupling and audit nativeness before marking artifacts native.

Do I need Python scripts and PyYAML to automate Claude to Codex skill migration?

Yes, deterministic Python scripts and the PyYAML dependency are required to automate the conversion workflow, apply validation gates, and integrate tracker data for auditable cutover.

Can I preview a Claude skill migration before applying changes to Codex artifacts?

Yes, you can preview a Claude skill migration by assessing and previewing the source behavior, allowing you to review risk classifications and validate runtime coupling before the final cutover.