improve-prompt
Prompt engineering architect that transforms raw prompts into optimized, production-ready prompts. PROACTIVELY activate for: (1) Improve/refine prompts, (2) Optimize prompts for specific models, (3) Create prompt chains/sequences, (4) Analyze prompt quality, (5) Transform prompts for different contexts. Triggers: "improve this prompt", "refine prompt", "optimize prompt", "make this prompt better", "prompt engineering", "fix my prompt"
What this skill does
# Improve Prompt
Transform prompts into optimized, production-ready versions.
## Purpose
Analyze and enhance prompts by:
- Identifying weaknesses and ambiguities
- Applying prompt engineering best practices
- Optimizing for specific models (Claude, Gemini, GPT)
- Structuring for consistent outputs
- Adding appropriate constraints and examples
## When to Use
**Ideal for:**
- Prompts that get inconsistent results
- Prompts that need to work across models
- Complex prompts requiring structure
- Prompts for production use
**Avoid when:**
- Simple, one-off questions
- Conversational queries
## Workflow
### Step 1: Analyze Current Prompt
Evaluate the prompt for:
- **Clarity:** Is the task unambiguous?
- **Completeness:** Is all necessary context provided?
- **Structure:** Is it well-organized?
- **Constraints:** Are boundaries defined?
- **Examples:** Are examples provided if needed?
- **Output format:** Is expected output specified?
### Step 2: Identify Improvements
Common issues to address:
- Vague instructions → Make specific
- Missing context → Add relevant background
- No output format → Specify structure
- No examples → Add few-shot examples
- No constraints → Add guardrails
- Too long → Consolidate and prioritize
### Step 3: Apply Best Practices
**For Claude:**
- Use XML tags for structure
- Leverage extended thinking for complex tasks
- Request step-by-step reasoning
- Use positive framing ("do X" not "don't do Y")
**For all models:**
- Put important instructions at start and end
- Use numbered steps for sequences
- Provide concrete examples
- Specify output format explicitly
- Include edge case handling
### Step 4: Generate Improved Prompt
Output the optimized prompt with:
- Clear structure
- Explicit instructions
- Defined output format
- Examples if beneficial
## Output Format
```markdown
## Prompt Analysis
**Original prompt issues:**
1. [Issue 1]
2. [Issue 2]
**Improvements applied:**
1. [Improvement 1]
2. [Improvement 2]
---
## Improved Prompt
[The optimized prompt, ready to copy]
---
## Usage Notes
- **Best for:** [model/use case]
- **Expected output:** [description]
- **Variations:** [any suggested variations]
```
## Quality Gates
- [ ] All ambiguities resolved
- [ ] Output format specified
- [ ] Appropriate length (not bloated)
- [ ] Tested mentally for edge cases
- [ ] Model-appropriate techniques used
## Examples
**Example: Vague prompt improvement**
*Before:*
Summarize this document
*After:*
Summarize the following document in 3-5 bullet points.
Focus on:
Key findings or conclusions
Important data points
Recommended actions
Format each bullet as: [Topic]: [1-2 sentence summary]
<document>
[Document content here]
</document>
````
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.