Migrate Claude Code Slash Commands to Portable Agent Skills

Where this fits

Your team has spent months curating .claude/commands/ slash commands. Then someone asks: "Can Codex or Copilot use these too?" Instead of rewriting prompts for each runtime, you reach for claude-command-converter. It migrates existing command files into the standard skills/*/SKILL.md format, so the same capability stays portable across AI coding assistants. The skill works best during a migration or when you want to standardize command definitions before a tooling change.

Why agents benefit

• Converts Claude Code frontmatter into SKILL.md YAML while preserving the description and structured metadata.
• Handles Claude-specific fields such as handoffs by mapping them into portable next-agent hints, so workflow context is not lost.
• Leaves the original .md file intact, making the migration reversible and auditable.
• Produces predictable output paths and filenames, so agents can discover the new skill without manual path mapping.
• Lets agents reuse proven command logic instead of reimplementing prompts from scratch in another runtime.

Practical scenarios

Moving from Claude Code to a mixed-agent team

Your organization standardizes on Claude Code, but a new project will use Codex CLI. Convert the existing slash commands once, then share the generated skills across both toolchains.

Standardizing before a monorepo extraction

A large repository has scattered .claude/commands/ files. You need a single skills/ directory that every agent in the monorepo can load. The converter gives you a consistent starting point.

Refreshing legacy command files

Old command files have useful logic but inconsistent frontmatter. Running them through the converter forces a uniform structure and exposes missing metadata before you invest in cleanup.

Add it to your agent workflow

Install the skill with:

npx skills add dceoy/speckit-agent-skills --skill claude-command-converter

Then ask your agent to run a conversion:

# Convert .claude/commands/release.md to skills/release/SKILL.md
Use claude-command-converter to convert .claude/commands/release.md into a skill.

The skill will ask for the source path if you omit it, and it will default the target skill name to the command filename.

Compare before adopting

Check whether the converter preserves custom YAML fields or only core metadata. See if it is updated as the Agent Skills spec evolves, and test how it handles handoffs with multiple agents. For a small set of commands, hand-rolling SKILL.md files may be simpler; for a large command library, this converter saves real time. You can review the skill listing at https://www.openagentskill.com/skills/dceoy-claude-command-converter to see how it fits into the broader ecosystem.

Why it is worth tracking

With 129 stars and an active speckit-agent-skills repository, this skill shows real community momentum. The stronger signal is that it targets the standard Agent Skills format rather than a vendor-specific schema, which means converted output should age well as runtimes change. Evaluate it before your next slash-command cleanup if you want portable agent capabilities instead of another lock-in.