meta-command

Create and validate Claude Code slash commands with structured frontmatter and safety checks.

1|Updated May 18, 2025
One-click install
npx skills add https://github.com/practical-stack/astro-blog-kit --skill meta-command-practical-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-command
Source: https://github.com/practical-stack/astro-blog-kit/tree/main/.claude/skills/meta-command
Command: npx skills add https://github.com/practical-stack/astro-blog-kit --skill meta-command-practical-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and validating Claude Code slash commands consistently, reducing ambiguity and errors.

Core Features & Use Cases

  • Standardized frontmatter and structure for new commands.
  • Integrated workflow guidance with phase-based design and testing.
  • Clear guidelines for skill integration, safety, and validation.

Quick Start

Create a new command file under .claude/commands, define frontmatter, and validate it with /organize-command.

Frequently Asked Questions about meta-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, define a new command file under .claude/commands and use /organize-command to validate structured frontmatter, ensuring predictable behavior and reducing ambiguity.

How do I integrate domain skills into Claude Code command workflows?

Integrate domain skills into command workflows by defining skill references within the command frontmatter, guiding phase-based design to orchestrate interactions while maintaining safety and validation checks.

What safety checks are enforced when orchestrating Claude Code commands?

Orchestrator commands enforce safety checks that validate structured frontmatter, verify skill references, and restrict destructive actions to ensure predictable behavior across integrated workflow phases.

Why does my Claude Code command validation fail during workflow integration?

Command validation fails when frontmatter is unstructured, skill references are missing, or unsafe tool usage is detected, preventing unpredictable behavior and destructive actions within the orchestrator workflow.

Can I use phase-based design to test Claude Code commands before deployment?

Yes, phase-based design guides the testing of Claude Code commands by integrating validation checks throughout the workflow, ensuring safe tool usage and predictable behavior before full deployment.

What is the best way to structure frontmatter for Claude Code orchestrator commands?

The best way to structure frontmatter for Claude Code orchestrator commands is to use standardized formatting with clear skill references, validated through /organize-command to ensure safe tool usage and predictable behavior.