New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Claude Command Converter

by dceoy in dceoy/speckit-agent-skills

Convert Claude Code commands (.claude/commands/.md) to standard Agent Skills (skills//SKILL.md).

AGPL-3.0Auto-check passedAgent Workflows

Install Claude Command Converter

skills CLI
$ npx skills add dceoy/speckit-agent-skills --skill claude-command-converter -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dceoy/speckit-agent-skills claude-command-converter --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dceoy/speckit-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/claude-command-converter .claude/skills/claude-command-converter && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
claude-command-converter
GitHub stars
146
Token cost
~1.4k tokens
SKILL.md length
386 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Convert Claude Code commands (.claude/commands/.md) to standard Agent Skills (skills//SKILL.md).

  • Works in 8 steps: Read the source command from… → Extract metadata → Determine skill name → …
  • Migrating slash commands to portable skill format
  • SKILL.md covers When to Use, Inputs, Format Differences and Conversion Workflow, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Claude Command Converter is an agent skill from dceoy/speckit-agent-skills. Convert Claude Code commands (.claude/commands/.md) to standard Agent Skills (skills//SKILL.md). Use when migrating slash commands to portable skill format, creating skills from existing commands, or standardizing command definitions across AI runtimes.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Hooks and plugins and Spec-driven development. The repository describes itself as: Agent skills for Spec Kit. The licence is AGPL-3.0.

When your agent uses it

  • Migrating slash commands to portable skill format
  • Creating skills from existing commands
  • Standardizing command definitions across AI runtimes

Example prompts

  • “/claude-command-converter”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Read the source command from .claude/commands/.
  2. Extract metadata
  3. Determine skill name
  4. Create skill directory: skills//
  5. Transform content to SKILL.md format
  6. Remove runtime-specific content
  7. Validate skill structure
  8. Report conversion result

What it can do on your machine

Read from SKILL.md and the folder at commit 52e6e7d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Claude Command Converter loads about 1.4k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 386 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dceoy/speckit-agent-skills at commit 52e6e7d, republished under its AGPL-3.0 licence (© dceoy). 386 words, ~1,412 tokens.

Download SKILL.mdSave it as .claude/skills/claude-command-converter/SKILL.md (or your agent's skills folder).
name
claude-command-converter
description
Convert Claude Code commands (.claude/commands/*.md) to standard Agent Skills (skills/*/SKILL.md). Use when migrating slash commands to portable skill format, creating skills from existing commands, or standardizing command definitions across AI runtimes.

Claude Command Converter

Convert Claude Code commands to standard Agent Skills format for portability across AI coding assistants.

When to Use

  • Migrating existing .claude/commands/*.md files to skills/*/SKILL.md format.
  • Creating portable skills from Claude Code-specific commands.
  • Standardizing command definitions for use with Claude Code, Codex CLI, GitHub Copilot, and other runtimes.

Inputs

  • Source command file path (e.g., .claude/commands/my-command.md).
  • Optional: target skill name (defaults to command filename without extension).

If input is missing, ask for the source command file path.

Format Differences

Claude Code Command Format

Location: .claude/commands/<command-name>.md

yaml
---
description: Short description of the command
handoffs:
  - label: Next Action
    agent: other.command
    prompt: Trigger prompt
    send: true
---
## User Input

\`\`\`text
$ARGUMENTS
\`\`\`

[Command instructions...]
Standard Agent Skill Format

Location: skills/<skill-name>/SKILL.md

yaml
---
name: skill-name
description: Complete description including what the skill does and when to use it.
---

# Skill Title

## When to Use

- Scenario 1
- Scenario 2

## Inputs

- Required input 1
- Optional input 2

## Workflow

1. Step 1
2. Step 2
...

## Outputs

- Output file 1
- Output file 2

Conversion Workflow

  1. Read the source command from .claude/commands/.

  2. Extract metadata:

    • description from YAML frontmatter.
    • handoffs for related skills/next steps.
    • $ARGUMENTS handling for inputs.

  3. Determine skill name:

    • Convert command.name.md → command-name (replace dots with hyphens).
    • Use kebab-case for multi-word names.

  4. Create skill directory: skills/<skill-name>/

  5. Transform content to SKILL.md format:

    • Frontmatter: Keep name and description only.
    • Enhance description: Expand to include when to use the skill.
    • Convert $ARGUMENTS: Document as Inputs section.
    • Structure workflow: Extract steps into numbered Workflow section.
    • Add "When to Use": Derive from command context and description.
    • Add "Outputs": List generated files/artifacts.
    • Convert handoffs: Add "Next Steps" section referencing related skills.

  6. Remove runtime-specific content:

    • Remove ## User Input section with $ARGUMENTS block.
    • Remove handoffs from frontmatter (move to prose).
    • Remove /command.name references (use skill names instead).

  7. Validate skill structure:

    • Frontmatter has name and description only.
    • Body has clear sections (When to Use, Inputs, Workflow, Outputs).
    • No TODO placeholders remain.
    • No runtime-specific variables like $ARGUMENTS.

  8. Report conversion result:

    • Source command path.
    • Generated skill path.
    • Key transformations applied.
    • Manual review recommendations.
Show full SKILL.md (118 more words)Show less

Transformation Rules

Claude CommandAgent Skill
$ARGUMENTSInputs section describing expected user input
handoffs:Next Steps section with skill references
/command.nameskill-name (kebab-case)
agent: foo.barfoo-bar skill reference
description: in frontmatterdescription: expanded with triggers
Inline ## User InputRemoved; documented in Inputs

Example Conversion

Input: .claude/commands/speckit.specify.md

yaml
---
description: Create feature specification from natural language.
handoffs:
  - label: Build Technical Plan
    agent: speckit.plan
---
## User Input

\`\`\`text
$ARGUMENTS
\`\`\`

The text the user typed after `/speckit.specify`...

Output: skills/speckit-specify/SKILL.md

yaml
---
name: speckit-specify
description: Create or update a feature specification from a natural language feature description.
---

# Spec Kit Specify Skill

## When to Use

- The user wants a new or updated feature spec from a natural language description.

## Inputs

- Feature description from the user.
- Repo context with `.specify/` scripts and templates.

If the description is missing or unclear, ask a targeted question before continuing.

## Workflow

...

## Outputs

- `specs/<feature>/spec.md`
- `specs/<feature>/checklists/requirements.md`

## Next Steps

After generating spec.md:

- **Plan** technical implementation with speckit-plan.
- **Clarify** specification requirements with speckit-clarify.

Key Rules

  • Preserve all workflow logic and instructions.
  • Remove runtime-specific constructs ($ARGUMENTS, handoffs, /slash-commands).
  • Expand terse descriptions to include usage triggers.
  • Use imperative voice in workflow steps.
  • Keep skills self-contained and portable.
  • Don't add extraneous documentation files (README, CHANGELOG, etc.).

Next Steps

After conversion:

  • Review generated SKILL.md for completeness.
  • Delete unused example files in scripts/, references/, assets/.
  • Update AGENTS.md/CLAUDE.md skill inventory if applicable.
  • Create symlinks for runtime integration if needed.

© dceoy, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/claude-command-converter of dceoy/speckit-agent-skills.

Open the folder on GitHubat commit 52e6e7d

Compare with similar skills

Claude Command Converter next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Claude Command Converter compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Claude Command Converter this skilldceoy/speckit-agent-skills146—~1.4kAutomated safety check: PassAGPL-3.0
Readyprekuter/dryforge4101 repos~6.8kAutomated safety check: PassApache-2.0
Migrationprekuter/dryforge4101 repos~3.2kAutomated safety check: PassApache-2.0
Goprekuter/dryforge4101 repos~7.2kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Ready

    prekuter/dryforge

    Understand what you mean before anything is built. An agent skill from prekuter/dryforge.

    410 GitHub starsUsed in 1 repo~6.8k tokens
    Agent WorkflowsAuto-check passed

  • Migration

    prekuter/dryforge

    Bring an existing codebase into Dryforge, once. An agent skill from prekuter/dryforge.

    410 GitHub starsUsed in 1 repo~3.2k tokens
    Agent WorkflowsAuto-check passed

  • Go

    prekuter/dryforge

    Carry out the intent approved in ready, as meant, and prove it with checks that actually ran.

    410 GitHub starsUsed in 1 repo~7.2k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

More from dceoy/speckit-agent-skills

  • Speckit Baseline

    dceoy/speckit-agent-skills

    Generate feature specifications by analyzing existing source code.

    146 GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed

Categories

Questions about Claude Command Converter

What does Claude Command Converter do?

Convert Claude Code commands (.claude/commands/.md) to standard Agent Skills (skills//SKILL.md). Claude Command Converter is an agent skill from dceoy/speckit-agent-skills.md).

When should I use Claude Command Converter?

Claude Command Converter fits situations like: migrating slash commands to portable skill format; creating skills from existing commands; standardizing command definitions across AI runtimes.

How do I install Claude Command Converter in Claude Code?

Run `npx skills add dceoy/speckit-agent-skills --skill claude-command-converter -a claude-code`. Or copy the skill folder (skills/claude-command-converter in dceoy/speckit-agent-skills) into .claude/skills/claude-command-converter in your project. Claude Code loads it when a task matches its description.

How do I install Claude Command Converter in Codex?

Run `npx skills add dceoy/speckit-agent-skills --skill claude-command-converter -a codex`. Or copy the skill folder (skills/claude-command-converter in dceoy/speckit-agent-skills) into .agents/skills/claude-command-converter in your project. Codex loads it when a task matches its description.

Can I use Claude Command Converter in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dceoy/speckit-agent-skills --skill claude-command-converter -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/claude-command-converter, .gemini/skills/claude-command-converter, .github/skills/claude-command-converter and .opencode/skills/claude-command-converter in your project.

What does Claude Command Converter need to run?

SKILL.md names no scripts, command-line tools or credentials: Claude Command Converter is instructions for the agent only.

Does Claude Command Converter access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Claude Command Converter safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Claude Command Converter use?

Claude Command Converter is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Claude Command Converter use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Claude Command Converter?

Skills that share tags, products or a category with Claude Command Converter: Ready (prekuter/dryforge, 410 stars), Migration (prekuter/dryforge, 410 stars), Go (prekuter/dryforge, 410 stars) and Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Claude Command Converter?

dceoy (a GitHub user) maintains it in dceoy/speckit-agent-skills, which has 146 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 28, 2026.

Source: dceoy/speckit-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.