prompt-optimization
Analyze and improve existing prompts for better performance
What this skill does
# Prompt Optimization Skill for analyzing and improving existing prompts. ## Optimization Workflow ``` 1. ANALYZE current prompt ↓ 2. IDENTIFY issues ↓ 3. APPLY corrections ↓ 4. VALIDATE improvement ↓ 5. DOCUMENT changes ``` ## Analysis Checklist ### Clarity - [ ] Unambiguous instructions? - [ ] Clearly defined objective? - [ ] Precise vocabulary? ### Structure - [ ] Well-delimited sections? - [ ] Logical order? - [ ] Clear hierarchy? ### Completeness - [ ] Output format defined? - [ ] Error cases handled? - [ ] Examples if needed? ### Guardrails - [ ] Explicit limits? - [ ] Forbidden behaviors listed? - [ ] Appropriate security? ## Common Problems and Solutions ### 1. Vague Instructions **Before:** ``` Write a good summary. ``` **After:** ``` Write a 100-150 word summary that: 1. Captures the main idea in the first sentence 2. Includes 2-3 supporting key points 3. Uses accessible language (high school level) 4. Avoids technical jargon ``` ### 2. Lack of Context **Before:** ``` Analyze this code. ``` **After:** ``` Analyze this Python code focusing on: - Performance (algorithmic complexity) - Readability (PEP 8 conventions) - Security (OWASP vulnerabilities) Context: Code for production REST API, 10k requests/day. ``` ### 3. Undefined Format **Before:** ``` Give me recommendations. ``` **After:** ``` Provide 3-5 recommendations in this format: ## Recommendation [N]: [Short title] **Impact:** [High/Medium/Low] **Effort:** [High/Medium/Low] **Action:** [1-2 sentence description] ``` ### 4. No Error Handling **Before:** ``` Translate this text to French. ``` **After:** ``` Translate this text to French. IF the text is already in French: → Indicate "The text is already in French" and suggest style improvements. IF the text contains technical jargon: → Keep technical terms in English with translation in parentheses. IF the text is too long (>1000 words): → Ask for confirmation before proceeding. ``` ### 5. Insufficient Emphasis **Before:** ``` Don't make up information. ``` **After:** ``` CRITICAL - ZERO TOLERANCE: NEVER make up information. IF uncertain → Explicitly say "I'm not sure about..." IF no data → Say "I don't have this information" ``` ## Improvement Techniques ### Add Chain-of-Thought ```markdown # Addition Before answering, think step by step: 1. What exactly is being asked? 2. What information do I have? 3. What is the best approach? 4. Are there pitfalls to avoid? ``` ### Add Examples ```markdown # Addition ## Examples ### Good example Input: [...] Output: [Expected output] ### Bad example (to avoid) Input: [...] Incorrect output: [What we don't want] Why incorrect: [Explanation] ``` ### Strengthen Guardrails ```markdown # Addition ## Forbidden (STRICT) - [Forbidden behavior 1] - [Forbidden behavior 2] ## Required (ALWAYS) - [Required behavior 1] - [Required behavior 2] ``` ## Optimization Report Format ```markdown # Optimization of [Prompt Name] ## Before/After Score | Criterion | Before | After | |-----------|--------|-------| | Clarity | X/10 | Y/10 | | Structure | X/10 | Y/10 | | Completeness | X/10 | Y/10 | | Guardrails | X/10 | Y/10 | | **Total** | **X/40** | **Y/40** | ## Identified Issues 1. [Issue 1] 2. [Issue 2] ## Applied Changes | Before | After | Reason | |--------|-------|--------| | [...] | [...] | [...] | ## Optimized Prompt --- [THE COMPLETE PROMPT] --- ## Recommended Tests - [ ] Standard case test - [ ] Edge case test 1 - [ ] Edge case test 2 ``` ## Forbidden - Never change the original meaning of the prompt - Never add unrequested features - Never remove existing guardrails - Never make the prompt longer without justification
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.