migration-dashboard

Track migration progress and prioritize next artifacts from migration-state.json.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Migrating Claude Code skills and agents to the Codex ecosystem often involves scattered progress tracking, unclear prioritization, and missed drift or nativeness review steps. This Skill eliminates that guesswork by centralizing all migration status, planning, and review data in one accessible dashboard.

Core Features & Use Cases

  • Progress Tracking: Reports migration status, drift detection, velocity metrics, and nativeness review state directly from the migration tracker.
  • Batch Planning: Recommends the next set of artifacts to migrate based on dependency order and priority, unblocking downstream work.
  • Nativeness Review Management: Surfaces artifacts pending nativeness review, routes to the appropriate review flow, and tracks review outcomes.
  • Use Case: For a team migrating 50+ Claude skills to Codex, use this dashboard to instantly see which artifacts are blocked, which need review next, and how fast the migration is progressing.

Quick Start

Use the migration-dashboard skill to show the current migration status and the next recommended batch of artifacts to migrate.

Frequently Asked Questions about migration-dashboard

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

FAQPage Schema
How do I track progress when migrating Claude Code skills to the Codex ecosystem?

To track Claude Code to Codex migration progress, you need a centralized dashboard that reads migration state data and reports status, drift detection, and velocity metrics. This eliminates scattered tracking by surfacing blocked artifacts and next steps.

What is the best way to prioritize which artifacts to migrate next during an ecosystem migration?

Prioritizing artifact migration requires batch planning based on dependency order and priority. A migration dashboard identifies content drift and recommends the next set of artifacts, unblocking downstream work and ensuring dependencies are resolved correctly.

How does nativeness review queue management work for migrated artifacts?

Nativeness review queue management surfaces artifacts pending review, routes them to the appropriate flow, and tracks outcomes. This ensures migrated skills meet ecosystem standards before finalizing the migration state.

Can I manage a large scale migration of 50+ skills to Codex without losing track of dependencies?

Managing large scale migration of 50+ skills requires dependency resolution and state validation. A tracker-driven dashboard handles this scale by instantly showing which artifacts are blocked and validating migration state data.

Why does content drift happen during Claude to Codex migration and how do I detect it?

Content drift happens when migrated artifacts fall out of sync with the source ecosystem. You detect it by continuously refreshing migration state data, which identifies drift and flags artifacts requiring nativeness review.