command-creator

Create standardized slash command files for Claude Code plugins.

5|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/basher83/agent-auditor --skill command-creator-basher83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: command-creator
Source: https://github.com/basher83/agent-auditor/tree/main/skills/command-creator
Command: npx skills add https://github.com/basher83/agent-auditor --skill command-creator-basher83

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design slash commands for Claude Code plugins, with a frontmatter description and a structured Markdown body that instructs Claude in a consistent, reusable format.

Core Features & Use Cases

  • Command structure: ensures each command is a Markdown file with a frontmatter description, steps, output format, and examples
  • Naming & Syntax: uses kebab-case filenames; instructions written from Claude's perspective
  • Official Docs Alignment: references to plugin docs for command specs

Quick Start

Create a command: commands/generate-tests.md with description "Generate tests for a file" and include steps and output format.

Frequently Asked Questions about command-creator

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

FAQPage Schema
How do I create slash commands for Claude Code plugins?

Create slash commands as Markdown files in a commands/ directory with YAML frontmatter containing a description field, followed by structured steps and output format. Name files in kebab-case and write instructions from Claude's perspective to define command behavior, arguments, and tool restrictions.

What structure should a slash command file have?

A slash command file requires YAML frontmatter with a description, a Markdown body with stepwise guidance, argument hints, output format specification, and examples. The file format ensures consistency across plugin commands and clarifies what Claude should do when the command runs.

Can I customize command arguments and tool restrictions in slash commands?

Yes, slash commands support argument hints and tool restrictions defined within the Markdown body. Include these specifications in the stepwise guidance so Claude knows which tools to use and what parameters users can pass when invoking the command.

Do I need to follow a naming convention for command files?

Yes, command files must use kebab-case filenames and reside in the commands/ directory. This standardized naming and location structure ensures Claude Code plugins recognize and load commands consistently across different plugin implementations.

What's the best way to document command behavior for Claude?

Write clear Claude-perspective instructions in the Markdown command body that describe the task, expected steps, output format, and worked examples. This guidance helps Claude execute the command reliably and produce consistent results across different invocations.

How does slash command automation reduce plugin development friction?

Standardized command files with frontmatter and structured formatting eliminate repetitive setup work. By defining description, arguments, and instructions once in a template format, developers reuse the structure across multiple commands without customizing boilerplate for each new plugin addition.