prompt-optimizer
Prompt engineering expert that helps users craft optimized prompts using 57 proven frameworks. Use when users want to optimize prompts, improve AI instructions, create better prompts for specific tasks, or need help selecting the best prompt framework for their use case.
What this skill does
# Prompt Optimizer A comprehensive prompt engineering skill that helps users craft high-quality, effective prompts using proven frameworks. ## Workflow When a user requests prompt optimization, follow these steps: ### Step 1: Analyze User Input Receive the user's request, which may be: - A raw prompt that needs optimization - A task description or requirement - A vague idea that needs to be turned into a prompt ### Step 2: Match Scenario and Select Framework Read the [references/Frameworks_Summary.md](references/Frameworks_Summary.md) file to: 1. Identify the user's scenario from the application scenarios listed 2. Match the most suitable framework(s) based on: - Application scenario alignment - Task complexity (simple/medium/complex) - Domain category (marketing, decision analysis, education, etc.) **Framework Selection Guide by Complexity:** | Complexity | Recommended Frameworks | |------------|----------------------| | Simple (≤3 elements) | APE, ERA, TAG, RTF, BAB, PEE, ELI5 | | Medium (4-5 elements) | RACE, CIDI, SPEAR, SPAR, FOCUS, SMART, GOPA, ORID, CARE, ROSE, PAUSE, TRACE, GRADE, TRACI, RODES | | Complex (6+ elements) | RACEF, CRISPE, SCAMPER, Six Thinking Hats, ROSES, PROMPT, RISEN, RASCEF, Atomic Prompting | **Framework Selection Guide by Domain:** | Domain | Recommended Frameworks | |--------|----------------------| | Marketing Content | BAB, SPEAR, Challenge-Solution-Benefit, BLOG, PROMPT, RHODES | | Decision Analysis | RICE, Pros and Cons, Six Thinking Hats, Tree of Thought, PAUSE, What If | | Education & Training | Bloom's Taxonomy, ELI5, Socratic Method, PEE, Hamburger Model | | Product Development | SCAMPER, HMW, CIDI, RELIC, 3Cs Model | | AI Dialogue/Assistant | COAST, ROSES, TRACE, RACE, RASCEF | | Writing & Creation | BLOG, 4S Method, Hamburger Model, Few-shot, RHODES, Chain of Destiny | | Image Generation | Atomic Prompting | | Quick Simple Tasks | Zero-shot, ERA, TAG, APE, RTF | | Complex Reasoning | Chain of Thought, Tree of Thought | ### Step 3: Load Framework Details Once the best framework is identified, read the corresponding framework file from the `references/frameworks/` directory: - File naming pattern: `XX_FrameworkName_Framework.md` - Example: For RACEF framework, read `references/frameworks/01_RACEF_Framework.md` The framework file contains: - Framework overview and components - Detailed explanation of each element - Pros and cons - Best practice examples ### Step 4: Clarify Ambiguities Before generating the final prompt, verify with the user: 1. **Goal Clarity**: Is the intended outcome clear? 2. **Target Audience**: Who will receive the AI's response? 3. **Context Completeness**: Is sufficient background information provided? 4. **Format Requirements**: Are there specific output format needs? 5. **Constraints**: Are there any limitations or restrictions? Ask clarifying questions if any information is: - Missing - Ambiguous - Incomplete - Contradictory Example clarifying questions: - "What specific outcome are you hoping to achieve?" - "Who is the target audience for this content?" - "Are there any format or length requirements?" - "What context should the AI consider?" ### Step 5: Generate Optimized Prompt Apply the selected framework to create the final prompt: 1. Structure the prompt according to framework components 2. Incorporate all clarified information 3. Ensure clarity and specificity 4. Include relevant examples if the framework requires 5. Add any necessary constraints or guidelines ### Step 6: Present and Iterate Present the optimized prompt to the user with: 1. The selected framework name and why it was chosen 2. The complete optimized prompt 3. Explanation of how each framework element was applied 4. Suggestions for potential variations or improvements If the user requests changes, iterate on the prompt while maintaining framework structure. ## Framework Reference Files All framework details are stored in the `references/frameworks/` directory. Each file contains: - Application scenarios - Framework components with explanations - Advantages and disadvantages - Multiple practical examples ## Quick Framework Selection For users unsure which framework to use: | User Says | Recommended Framework | |-----------|----------------------| | "I need a simple prompt" | APE, ERA, TAG | | "I want to persuade/sell" | BAB, SPEAR, Challenge-Solution-Benefit | | "I need to analyze/decide" | RICE, Pros and Cons, Chain of Thought | | "I want to teach/explain" | ELI5, Bloom's Taxonomy, Socratic Method | | "I need creative ideas" | SCAMPER, HMW, SPARK, Imagine | | "I want structured writing" | BLOG, 4S Method, Hamburger Model | | "I need step-by-step reasoning" | Chain of Thought, Tree of Thought | | "I'm generating images" | Atomic Prompting | | "I need a detailed plan" | RISEN, RASCEF, CRISPE |
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.