SlashCommandCreator Skill
Purpose
Create production-ready custom slash commands following ai-agents quality standards.
When to Use
- •User requests "create slash command for [purpose]"
- •Repetitive prompts identified in workflow
- •Converting manual workflows to automation
- •Need reusable, documented command patterns
5-Phase Workflow
Phase 1: Discovery & Analysis
Agent Mode: Analyst
Tasks:
- •Clarify user intent: What prompt is being repeated?
- •Search existing commands:
ls .claude/commands/**/*.md - •Decision: Slash command vs skill (see decision matrix in CLAUDE.md)
- •Apply 11 thinking models from skillcreator framework
- •Document findings in
.agents/analysis/slashcommand-[name]-analysis.md
Deliverable: Analysis document with recommendation
Phase 2: Design
Agent Mode: Architect
Tasks:
- •Command naming (namespace conventions)
- •Argument design:
- •Simple commands: use
$ARGUMENTS - •Complex commands: use
$1,$2,$3(positional)
- •Simple commands: use
- •Frontmatter schema:
- •
description(trigger-based per creator-001) - •
argument-hint(if using arguments) - •
allowed-tools(if using bash!or file@) - •
model(opus for complex reasoning) - •
disable-model-invocation(if pure prompt template)
- •
- •Dynamic context evaluation:
- •Bash execution (
!git log --oneline -5) - •File references (
@.agents/HANDOFF.md)
- •Bash execution (
- •Extended thinking evaluation:
- •Add
ultrathinkkeyword for complex reasoning (>5 steps) - •Token budget consideration (<31,999 tokens)
- •Add
Deliverable: Design specification with frontmatter + prompt
Phase 3: Multi-Agent Validation
Agent Mode: Orchestrator (coordinates 4 agents)
Agents:
- •
Security:
- •Review
allowed-toolsconstraints - •Flag overly permissive wildcards
- •Verify bash commands are safe
- •Review
- •
Architect:
- •Check for duplication (similar existing commands)
- •Verify appropriate scope (not too broad/narrow)
- •Validate namespace conventions
- •
Independent-Thinker:
- •Challenge necessity: Is this really needed?
- •Propose alternatives
- •Question assumptions
- •
Critic:
- •Frontmatter completeness check
- •Trigger-based description validation
- •Argument-hint clarity
Unanimous Approval Required: All 4 agents must approve.
<!-- WHY: Ensures no single agent dimension (security, scope, necessity, completeness) is overlooked. Prevents security vulnerabilities from passing due to focus on functionality alone. Pattern proven by skillcreator 3.2.0 multi-agent synthesis. -->Invocation Pattern:
# Security review Task(subagent_type="security", prompt="Review allowed-tools for command: [spec]") # Architecture review Task(subagent_type="architect", prompt="Check for duplication: [spec]") # Challenge necessity Task(subagent_type="independent-thinker", prompt="Is this command truly needed? [spec]") # Frontmatter completeness Task(subagent_type="critic", prompt="Validate frontmatter completeness: [spec]")
Deliverable: Validation report with approvals or revision requests
Phase 4: Implementation
Agent Mode: Implementer
Tasks:
- •Run
pwsh .claude/skills/slashcommandcreator/scripts/New-SlashCommand.ps1 - •Create
.claude/commands/[namespace]/[command].md - •Write frontmatter + prompt body
- •Test invocation with sample arguments
- •Update command catalog (if exists)
Deliverable: Working slash command file
Phase 5: Quality Gates (Automatic)
Agent Mode: Implementer (automatic validation)
Tasks:
- •Run
pwsh .claude/skills/slashcommandcreator/scripts/Validate-SlashCommand.ps1 -Path [file] - •Fix violations if any
- •Re-run validation until exit code 0
- •Commit with conventional commit message
Deliverable: Validated slash command ready for use
Invocation Examples
SlashCommandCreator: create command for exporting Forgetful memories to JSON SlashCommandCreator: design slash command for running security audit create slash command that summarizes recent PR comments
Decision Matrix: Slash Command vs Skill
Use Slash Command When:
- •Prompt is <200 lines
- •No multi-step conditional logic
- •Simple argument substitution
- •No external script orchestration
Use Skill When:
- •Prompt is >200 lines
- •Multi-agent coordination required
- •Complex PowerShell logic
- •Requires Pester tests
Quality Gates Checklist
Before marking complete:
- • Frontmatter has
description(trigger-based) - • Frontmatter has
argument-hint(if uses arguments) - • Frontmatter has
allowed-tools(if uses bash/file refs) - • No overly permissive wildcards in
allowed-tools - • Description follows trigger-based pattern (creator-001)
- • File is <200 lines (or converted to skill)
- • Passes
markdownlint-cli2validation - • Passes
Validate-SlashCommand.ps1validation - • Tested with sample arguments
- • Committed with conventional commit message
References
- •
.agents/analysis/custom-slash-commands-research.md - •
.agents/planning/slashcommandcreator-skill-spec.md - •
notes/slashcommand-best-practices.md