creating-commands
Creates new Claude Code slash commands following best practices. Guides through command structure, naming, arguments, and frontmatter. Use when user wants to create a command, build a slash command, or asks about command best practices.
Best use case
creating-commands is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Creates new Claude Code slash commands following best practices. Guides through command structure, naming, arguments, and frontmatter. Use when user wants to create a command, build a slash command, or asks about command best practices.
Teams using creating-commands should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/creating-commands/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How creating-commands Compares
| Feature / Agent | creating-commands | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Creates new Claude Code slash commands following best practices. Guides through command structure, naming, arguments, and frontmatter. Use when user wants to create a command, build a slash command, or asks about command best practices.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Creating Commands Guides creation of Claude Code slash commands using documented best practices. ## Quick Start For a new command: 1. Ask user for command purpose and arguments needed 2. Generate using appropriate template 3. Validate against checklist For reviewing existing command: 1. Read command file 2. Check against anti-patterns in [reference.md](reference.md) 3. Report issues with fixes ## Workflow: Create New Command ``` Progress: - [ ] Gather requirements (purpose, arguments, scope) - [ ] Choose template (basic, with-args, workflow) - [ ] Generate command file - [ ] Validate against checklist ``` ### Step 1: Gather Requirements Ask user with AskUserQuestion: - What should this command do? (purpose) - Does it need arguments? (none, single, multiple) - Project or personal? (scope) ### Step 2: Choose Template | Type | Template | When to Use | |------|----------|-------------| | Basic | [templates/basic.md](templates/basic.md) | No arguments, simple prompt | | With Args | [templates/with-args.md](templates/with-args.md) | Single or multiple arguments | | Workflow | [templates/workflow.md](templates/workflow.md) | Integrates with skills/agents | ### Step 3: Generate Command Create in appropriate location: - `.claude/commands/` - Project commands (git-tracked) - `~/.claude/commands/` - Personal commands (your machine only) ### Step 4: Validate Run through checklist before finishing: ``` Validation Checklist: - [ ] Name: lowercase with hyphens only - [ ] Name: descriptive, verb-noun format preferred - [ ] Description: explains what command does - [ ] Arguments: documented with argument-hint if used - [ ] Prompt: clear, actionable instructions - [ ] Tools: allowed-tools declared if needed ``` ## Naming Rules **Format**: `verb-noun` or `action` (lowercase, hyphens) - `fix-issue` - `review-pr` - `run-tests` - `optimize` **Constraints**: - Lowercase letters, numbers, hyphens only - No spaces or underscores - Keep concise (1-3 words) ## Command File Format ```markdown --- description: Brief explanation shown in help allowed-tools: - Bash(bash:*) - WebSearch argument-hint: "param_name" --- Your command prompt here. Use $ARGUMENTS for all args or $1, $2 for positional. ``` ## Argument Syntax | Syntax | Usage | Example | |--------|-------|---------| | `$ARGUMENTS` | All arguments as one string | `/cmd foo bar` → `foo bar` | | `$1`, `$2` | Positional arguments | `/cmd foo bar` → `$1=foo`, `$2=bar` | | `@file` | Include file contents | `Review @src/main.ts` | ## Frontmatter Options | Field | Purpose | Required | |-------|---------|----------| | `description` | Shown in help, enables auto-invoke | Recommended | | `allowed-tools` | Tools the command can use | If using tools | | `argument-hint` | Documents expected args | If has args | | `model` | Specific model to use | Optional | ## Example: Basic Command ```markdown --- description: Run all tests and report failures allowed-tools: - Bash(npm:*) --- Run the test suite and summarize results: 1. Execute `npm test` 2. If failures, show failing tests with context 3. Suggest fixes for common issues ``` See [reference.md](reference.md) for detailed best practices and anti-patterns.
Related Skills
creating-github-issues-from-web-research
This skill enhances Claude's ability to conduct web research and translate findings into actionable GitHub issues. It automates the process of extracting key information from web search results and formatting it into a well-structured issue, ready for team action. Use this skill when you need to research a topic and create a corresponding GitHub issue for tracking, collaboration, and task management. Trigger this skill by requesting Claude to "research [topic] and create a ticket" or "find [information] and generate a GitHub issue".
linux-commands-guide
Linux Commands Guide - Auto-activating skill for DevOps Basics. Triggers on: linux commands guide, linux commands guide Part of the DevOps Basics skill category.
creating-data-visualizations
This skill enables Claude to generate data visualizations, plots, charts, and graphs from provided data. It analyzes the data, selects the most appropriate visualization type, and creates a visually appealing and informative graphic. Use this skill when the user requests a visualization, plot, chart, or graph; when data needs to be presented visually; or when exploring data patterns. The skill is triggered by requests for "visualization", "plot", "chart", or "graph".
creating-webhook-handlers
Create webhook endpoints with signature verification, retry logic, and payload validation. Use when receiving and processing webhook events. Trigger with phrases like "create webhook", "handle webhook events", or "setup webhook handler".
creating-kubernetes-deployments
Deploy applications to Kubernetes with production-ready manifests. Supports Deployments, Services, Ingress, HPA, ConfigMaps, Secrets, StatefulSets, and NetworkPolicies. Includes health checks, resource limits, auto-scaling, and TLS termination. Use when working with creating kubernetes deployments. Trigger with 'creating', 'kubernetes', 'deployments'.
creating-apm-dashboards
Execute this skill enables AI assistant to create application performance monitoring (apm) dashboards. it is triggered when the user requests the creation of a new apm dashboard, monitoring dashboard, or a dashboard for application performance. the skill helps ... Use when generating or creating new content. Trigger with phrases like 'generate', 'create', or 'scaffold'.
creating-ansible-playbooks
Execute use when you need to work with Ansible automation. This skill provides Ansible playbook creation with comprehensive guidance and automation. Trigger with phrases like "create Ansible playbook", "automate with Ansible", or "configure with Ansible".
creating-alerting-rules
Execute this skill enables AI assistant to create intelligent alerting rules for proactive performance monitoring. it is triggered when the user requests to "create alerts", "define monitoring rules", or "set up alerting". the skill helps define thresholds, rou... Use when generating or creating new content. Trigger with phrases like 'generate', 'create', or 'scaffold'.
vscode-ext-commands
Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices
creating-oracle-to-postgres-migration-integration-tests
Creates integration test cases for .NET data access artifacts during Oracle-to-PostgreSQL database migrations. Generates DB-agnostic xUnit tests with deterministic seed data that validate behavior consistency across both database systems. Use when creating integration tests for a migrated project, generating test coverage for data access layers, or writing Oracle-to-PostgreSQL migration validation tests.
creating-oracle-to-postgres-migration-bug-report
Creates structured bug reports for defects found during Oracle-to-PostgreSQL migration. Use when documenting behavioral differences between Oracle and PostgreSQL as actionable bug reports with severity, root cause, and remediation steps.
creating-oracle-to-postgres-master-migration-plan
Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies.