create-command

Create Claude Code slash commands with structured frontmatter and markdown.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/andy-austin/quipu --skill create-command-andy-austin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-command
Source: https://github.com/andy-austin/quipu/tree/main/.claude/skills/create-command
Command: npx skills add https://github.com/andy-austin/quipu --skill create-command-andy-austin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, best-practices workflow for creating Claude Code slash commands, ensuring consistent frontmatter, argument handling, and clear usage guidance.

Core Features & Use Cases

  • Enforces a standard command structure with frontmatter guidelines (name, description, allowed-tools, model, argument-hint)
  • Supports both project-scoped and personal commands, with clear organization and discoverability
  • Includes comprehensive Quick Start guidance to accelerate command creation and testing

Quick Start

Create a new slash command by adding a Markdown file under the appropriate project or personal commands path and define its behavior in frontmatter and content.

Frequently Asked Questions about create-command

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

FAQPage Schema
How do I create Claude Code slash commands with consistent frontmatter?

To create Claude Code slash commands, you add a Markdown file with well-formed frontmatter including name, description, and argument-hint, then define the command behavior and examples in the markdown body. This enforces consistent prompt design across repositories.

What is the required structure for a Claude Code slash command template?

A Claude Code slash command template requires a frontmatter section with name, description, allowed-tools, model, and argument-hint fields, accompanied by a clear markdown body that defines usage guidance and examples for rapid prompt deployment.

Can I use slash commands for both personal workflows and project-scoped automation?

Yes, slash commands support both project-scoped and personal workflows. You place the Markdown file under the appropriate commands path to standardize tooling, invocation patterns, and prompt templates for either context.

What's the best way to standardize prompt design and invocation patterns across repositories?

Standardizing prompt design across repositories is best achieved by enforcing a consistent command structure with frontmatter metadata and a clear markdown body, allowing teams to rapidly deploy repeatable command templates.

Do I need any dependencies to automate slash command validation and design?

No dependencies are required to automate slash command validation and design. The process relies entirely on defining a well-formed frontmatter and a clear markdown body within your project or personal commands directory.

Why are my Claude Code slash commands not showing up or working correctly?

Slash commands may not work if the frontmatter is malformed or missing required fields like name, description, and argument-hint. Ensuring a well-structured frontmatter and a clear markdown body resolves validation and discoverability issues.