prompt-level-selection
Guide selection of appropriate prompt level for a task. Use when choosing between simple prompts and complex workflows, applying the seven levels framework, or matching task complexity to prompt investment.
What this skill does
# Prompt Level Selection Skill
Guide selection of the appropriate prompt level for a task using the seven levels framework.
## Purpose
Match task complexity to the right prompt level. Start simple, add complexity only when needed.
## When to Use
- Starting a new prompt
- Upgrading existing prompt
- Unsure which level fits
- Teaching prompt engineering
## The Seven Levels Quick Reference
| Level | Name | Use When |
| --- | --- | --- |
| 1 | High-Level | Simple repeatable task |
| 2 | Workflow | Sequential steps needed |
| 3 | Control Flow | Conditionals or loops |
| 4 | Delegation | Multiple agents needed |
| 5 | Higher-Order | Processing other prompts |
| 6 | Template Meta | Generating prompts |
| 7 | Self-Improving | Knowledge accumulation |
## Decision Tree
```text
Is this a simple, repeatable task?
├── Yes -> Level 1 (High-Level Prompt)
└── No
|
Does it need sequential steps?
├── Yes -> Does it need conditionals/loops?
| ├── Yes -> Does it delegate to agents?
| | ├── Yes -> Level 4 (Delegation)
| | └── No -> Level 3 (Control Flow)
| └── No -> Level 2 (Workflow)
└── No
|
Does it process other prompts?
├── Yes -> Level 5 (Higher-Order)
└── No
|
Does it generate prompts?
├── Yes -> Level 6 (Template Meta)
└── No
|
Does it need to learn over time?
├── Yes -> Level 7 (Self-Improving)
└── No -> Reassess requirements
```
## The 80/20 Rule
> "Levels 3-4 cover 80% of practical use cases."
| Level Range | Coverage | Complexity |
| --- | --- | --- |
| 1-2 | 40% | Low |
| 3-4 | 80% | Medium (Sweet Spot) |
| 5-7 | 20% | High |
**Don't over-engineer.** Most tasks fit in Levels 3-4.
## Selection Process
### Step 1: Understand the Task
Ask:
- What does this task accomplish?
- How often will it be repeated?
- What inputs does it need?
- What outputs does it produce?
### Step 2: Check Complexity Indicators
| Indicator | Points To |
| --- | --- |
| One-time or rare | Level 1 |
| Sequential steps | Level 2+ |
| "If X then Y" | Level 3+ |
| "Run N agents" | Level 4 |
| "Process this spec file" | Level 5 |
| "Create prompts for..." | Level 6 |
| "Learn and improve" | Level 7 |
### Step 3: Start Low, Upgrade If Needed
1. Start with lowest applicable level
2. Build and test the prompt
3. If insufficient, upgrade one level
4. Repeat until task is satisfied
## Level Selection Examples
### Example 1: "Start the dev server"
**Analysis:** Simple, repeatable, no variables
**Level:** 1 (High-Level Prompt)
### Example 2: "Create an implementation plan"
**Analysis:** Sequential steps, needs input, produces output
**Level:** 2 (Workflow Prompt)
### Example 3: "Generate N images with validation"
**Analysis:** Loop required, conditional checking
**Level:** 3 (Control Flow)
### Example 4: "Research topic with 5 parallel agents"
**Analysis:** Multiple agents, aggregation needed
**Level:** 4 (Delegation Prompt)
### Example 5: "Build from this spec file"
**Analysis:** Accepts another prompt/spec as input
**Level:** 5 (Higher-Order)
### Example 6: "Create new slash commands"
**Analysis:** Generates prompts in specific format
**Level:** 6 (Template Meta Prompt)
### Example 7: "Hook expert that learns patterns"
**Analysis:** Accumulates expertise over time
**Level:** 7 (Self-Improving Prompt)
## Output Format
When recommending a level:
```markdown
## Level Selection
**Task:** [description]
**Recommended Level:** [1-7] ([name])
**Rationale:**
- [reason 1]
- [reason 2]
**Key Sections Needed:**
- [section 1]
- [section 2]
**Alternative Consideration:**
Level [N] if [condition]
```
## Red Flags
| Red Flag | Issue | Solution |
| --- | --- | --- |
| Jumping to Level 6-7 | Over-engineering | Start at Level 2-3 |
| Level 1 for complex task | Under-engineering | Add Workflow section |
| Level 4 for single-agent | Unnecessary delegation | Use Level 2-3 |
| No clear level fit | Vague requirements | Clarify task scope |
## Key Quote
> "Three times marks a pattern. Copy whatever you're doing and write it as a high level prompt, then move up the levels from there."
## Cross-References
- @seven-levels.md - Detailed level descriptions
- @prompt-sections-reference.md - Sections for each level
- @stakeholder-trifecta.md - Communication considerations
## Version History
- **v1.0.0** (2025-12-26): Initial release
---
## Last Updated
**Date:** 2025-12-26
**Model:** claude-opus-4-5-20251101
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.