CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-to-codex

Migrate supported instruction files, skills, agents, and MCP config into Codex project and global files.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands, a clearly sequenced workflow, explicit validation checkpoints, and a self-healing feedback loop appropriate for a batch/destructive migration. Progressive disclosure is solid, with only minor inline formatting that could be externalized.

DimensionReasoningScore

Conciseness

The body is lean for a complex migration, assuming Claude's competence (no explaining what Codex/MCP is); the report-table format spec and some repetition between Migration Order and Self-Healing Loop are minor trim opportunities.

4 / 5

Actionability

Provides copy-paste-ready bash commands with a defined env var, specific flags (--scan-only, --plan, --doctor, --dry-run, --validate-target), and concrete examples covering the common global/project cases.

5 / 5

Workflow Clarity

A clearly sequenced 10-step Migration Order plus a Self-Healing Loop with explicit validation checkpoints (--validate-target, re-run --dry-run) and an error-recovery feedback loop for a destructive/batch operation.

5 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled one-level-deep reference to references/differences.md (verified present); the inline report-table format spec is a minor organization gap that could live in a reference.

4 / 5

Total

18

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, clearly conveying what the skill migrates and into what targets, but it omits any explicit 'when to use' trigger guidance which caps its completeness. Adding a Use-when clause would lift the weakest dimension.

Suggestions

Append an explicit trigger clause, e.g. 'Use when migrating a Claude Code project or global config to Codex' to satisfy the 'when' requirement and raise completeness.

Consider adding a synonym such as 'Claude Code' or 'convert' to broaden natural trigger-term coverage.

Optionally expand the action verb beyond the single 'Migrate' (e.g. 'Migrate and convert ...') to strengthen specificity.

DimensionReasoningScore

Specificity

Names the migration domain and enumerates four concrete artifact types (instruction files, skills, agents, MCP config) plus the Codex project/global targets, but the single verb 'Migrate' leaves minor coverage gaps versus a fuller action list.

4 / 5

Completeness

Clearly answers 'what' but has no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('Migrate', 'Codex', 'skills', 'agents', 'MCP config') with good coverage, though a few common synonyms ('Claude Code', 'convert') are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Claude Code → Codex migration) with distinct Codex triggers and named artifact types, giving minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/skills

Path

skills/.curated/migrate-to-codex/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.