Command Development

Create Claude Code slash commands with YAML frontmatter and argument validation.

2|1|Updated Apr 9, 2026

Search Tags:#workflow automation #claude code #slash commands #plugin development #frontmatter #bash execution #dynamic arguments

Ready to run

npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill command-development-timgranlundmarsden

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Command Development
Source: https://github.com/timgranlundmarsden/claude-agent-flow/tree/main/skills/command-development
Command: npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill command-development-timgranlundmarsden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you design and maintain Claude Code slash commands that are consistent, discoverable, and safe to use, instead of scattering one-off prompts and brittle workflow instructions across your project.

Core Features & Use Cases

Slash Command Structure: Define command files with clear Markdown content and YAML frontmatter so Claude can execute them predictably.
Dynamic Inputs and File Access: Use positional arguments, argument hints, file references, and bash output to build commands that adapt to context.
Plugin-Ready Workflows: Organize commands for Claude Code plugins, reference plugin resources portably, and coordinate with skills, agents, and hooks.
Validation and Safety: Restrict tools, validate inputs, handle errors gracefully, and document behavior for maintainable team workflows.

Quick Start

Use the command development skill to draft a new Claude Code slash command with frontmatter, arguments, and safe tool restrictions for your workflow.

Frequently Asked Questions about Command Development

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

FAQPage Schema

How do I create Claude Code slash commands with dynamic arguments?▼

You can create Claude Code slash commands by defining Markdown files with YAML frontmatter and reusable prompt patterns to handle positional arguments, argument hints, and file references for adaptable automation.

What is the best way to structure plugin workflows for Claude Code?▼

The best way to structure plugin workflows is to organize command files with clear Markdown content, portable plugin paths, and YAML metadata so Claude can execute them predictably and coordinate with skills and hooks.

How do I validate inputs and restrict tools in Claude Code commands?▼

To validate inputs and restrict tools in Claude Code commands, you can enforce YAML metadata rules, apply tool restrictions, handle errors gracefully, and document behavior for safe, maintainable team workflows.

Can I use bash execution and file references inside Claude Code commands?▼

Yes, you can use bash execution and file references inside Claude Code commands by configuring the Markdown frontmatter to inject dynamic context and script output directly into your prompt patterns.

Why are my custom Claude Code commands not working predictably?▼

Custom Claude Code commands often fail when YAML frontmatter is misconfigured, plugin paths are non-portable, or tool restrictions are too broad, making troubleshooting patterns essential for reliable execution.