Create Level 6 template meta-prompts that generate other prompts. Use when building prompt generators, designing high-leverage meta-prompts, or creating templates that scaffold other prompts.
Creates Level 6 meta-prompts that generate other prompts in a specified format. Use when building prompt libraries, standardizing team workflows, or creating prompt scaffolding templates.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install google-ecosystem@melodic-softwareThis skill is limited to using the following tools:
Create Level 6 template meta-prompts - the highest leverage prompts that generate other prompts.
Build prompts that create other prompts in a specific format. This is the highest leverage prompt engineering pattern.
High-Level Description -> [Meta-Prompt] -> New Prompt in Specified Format
Fetch current documentation for accuracy:
## Documentation
Slash Commands: https://docs.anthropic.com/en/docs/claude-code/slash-commands
Settings: https://docs.anthropic.com/en/docs/claude-code/settings
Why: Ensures generated prompts follow current best practices.
The exact format generated prompts should follow:
<!-- markdownlint-disable MD033 MD025 MD003 MD040 -->## Specified Format
<prompt purpose - high level description>
<NAME_OF_DYNAMIC_VARIABLE>: $1 <NAME_OF_STATIC_VARIABLE>: <STATIC_VALUE>
Why: Consistency across all generated prompts.
How to generate the prompt:
## Workflow
- We're building a new prompt to satisfy the HIGH_LEVEL_PROMPT
- Ultra Think - operating a prompt that builds a prompt
- Fetch documentation in parallel with Task tool
- Think through static vs dynamic variables
- Save to .claude/commands/<name>.md
What should generated prompts look like?
Design the exact structure:
## Specified Format
```md
[Your template here with placeholders]
Use <placeholder> for values the meta-prompt fills in.
Include relevant documentation URLs:
## Documentation
- Source 1: [URL]
- Source 2: [URL]
Consider using Task tool for parallel fetching.
How does the meta-prompt generate prompts?
## Workflow
1. Parse HIGH_LEVEL_PROMPT for requirements
2. Fetch documentation (in parallel if multiple)
3. Design prompt structure
4. Determine variables (dynamic vs static)
5. Create workflow steps
6. Output in Specified Format
7. Save to appropriate location
Ensure generated prompts are valid:
## Validation
Before outputting:
- [ ] Frontmatter is valid YAML
- [ ] Title is action-oriented
- [ ] Variables use SCREAMING_SNAKE_CASE
- [ ] Workflow has numbered steps
- [ ] Saved to correct location
---
allowed-tools: Write, Edit, WebFetch, Task
description: Create a new prompt in specified format
argument-hint: [high level prompt description]
model: opus
---
# MetaPrompt
Based on the HIGH_LEVEL_PROMPT, follow the Workflow to create a new prompt in the Specified Format.
## Variables
HIGH_LEVEL_PROMPT: $ARGUMENTS
## Documentation
Slash Commands: https://docs.anthropic.com/en/docs/claude-code/slash-commands
Settings: https://docs.anthropic.com/en/docs/claude-code/settings
## Workflow
1. Parse HIGH_LEVEL_PROMPT to understand requirements
2. Fetch documentation using Task tool in parallel
3. Design prompt structure based on requirements
4. Determine variables:
- What inputs from user? (dynamic)
- What fixed values? (static)
5. Create workflow steps (numbered, sequential)
6. Design output format (Report section)
7. Validate against Specified Format
8. Save to .claude/commands/<kebab-case-name>.md
## Specified Format
<!-- markdownlint-disable MD033 MD025 MD003 MD040 MD024 -->
```text
---
allowed-tools: <tools needed>
description: <clear description>
argument-hint: [<expected args>]
model: opus
---
# <Action-Oriented Title>
<Purpose: 1-2 sentences>
## Variables
<DYNAMIC_VAR>: $1
<STATIC_VAR>: <value>
## Workflow
1. <First step>
2. <Second step>
3. <Third step>
## Report
<Output format>
## Report
Prompt created: .claude/commands/<name>.md
Purpose: <brief description>
Variables: <count> dynamic, <count> static
Add domain knowledge to the template:
## Domain Context
This meta-prompt creates prompts for [domain]:
- Common patterns: [patterns]
- Required tools: [tools]
- Standard variables: [variables]
Support multiple output formats:
## Templates
### Slash Command Template
[template 1]
### Agent Template
[template 2]
## Workflow
1. Determine which template fits
2. Generate using appropriate template
When creating a meta-prompt:
## Meta-Prompt Design
**Purpose:** Generate [type] prompts
**Target Format:**
- Sections: [list]
- Frontmatter: [fields]
- Output location: [path]
**Documentation Sources:**
- [source 1]
- [source 2]
**Generated:**
[meta-prompt content]
"Level six, the template meta prompt, is the most powerful prompt you can write. It's the prompt that creates your other prompts."
"Highest leverage - prompts creating prompts."
Date: 2025-12-26 Model: claude-opus-4-5-20251101
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.