claude-code-slash-commands

Define and manage Claude Code slash commands via Markdown files with YAML frontmatter.

23|2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/dwmkerr/claude-toolkit --skill claude-code-slash-commands-dwmkerr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-slash-commands
Source: https://github.com/dwmkerr/claude-toolkit/tree/main/plugins/toolkit/skills/claude-code-slash-commands
Command: npx skills add https://github.com/dwmkerr/claude-toolkit --skill claude-code-slash-commands-dwmkerr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables developers to define and manage Claude Code slash commands by authoring compact Markdown definitions, enabling quick deployment of prompts via slash syntax.

Core Features & Use Cases

  • Command scoping: Organize commands by project, personal, or plugin scopes using named directories.
  • Frontmatter-driven configuration: Each command's metadata controls allowed tools, arguments, model selection, and execution context, enabling precise behavior and reuse.
  • Quick Start: Create a Markdown file under the appropriate commands directory with a YAML frontmatter and body describing the prompt.

Quick Start

Create a new slash command by adding a Markdown file under .claude/commands/ or commands/ with a frontmatter and body that contains the prompt instructions.

Frequently Asked Questions about claude-code-slash-commands

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

FAQPage Schema
How do I create custom Claude Code slash commands using Markdown?

You create custom slash commands by adding a Markdown file under .claude/commands/ or commands/, using YAML frontmatter to configure allowed tools and arguments, and a body for prompt instructions.

What is command scoping in Claude Code and how does it organize prompts?

Command scoping in Claude Code organizes slash commands into project, personal, or plugin scopes using named directories, ensuring prompts are only available in their intended execution context.

Can I control which tools and model a Claude Code slash command uses?

Yes, you can control allowed tools, arguments, model selection, and execution context for each Claude Code slash command by defining these settings in the command's YAML frontmatter.

Does building slash commands require any external dependencies or plugins?

No external dependencies are required to build slash commands; you only need to author lightweight Markdown definitions with frontmatter, making deployment quick and dependency-free.

What's the best way to define reusable prompts for Claude Code automation?

The best way to define reusable prompts for Claude Code automation is authoring lightweight Markdown definitions with frontmatter, allowing quick deployment and precise behavior control via slash syntax.

When should I not use Markdown files for Claude Code slash commands?

Markdown slash commands are limited to simple frontmatter schemas and static prompt text loaded into context, so they should not be used when dynamic logic or complex runtime execution is required.