prompt-improver
Analyze and improve plugin prompts, skill definitions, and command instructions for clarity, safety, and effectiveness. Use when the user asks to "improve a prompt", "review a skill", "enhance instructions", "make this prompt better", "optimize this command", or "audit prompt quality".
What this skill does
# Prompt Improver This skill automatically analyzes and improves plugin prompts, SKILL.md files, command definitions, and agent instructions. ## Overview The prompt-improver skill evaluates plugin content across five dimensions — clarity, safety, effectiveness, completeness, and conciseness — then provides scored assessments and concrete rewrites. ## When to Use This Skill This skill activates when you need to: - Review and improve a SKILL.md file's instructions - Enhance command or agent markdown definitions - Audit prompt quality across a plugin - Optimize instructions for better Claude performance - Ensure prompts follow marketplace best practices ## Instructions 1. **Identify the target** — Locate the SKILL.md, command, or agent file to analyze 2. **Read the content** — Use Read tool to get the full file contents 3. **Score each dimension** on a 1-5 scale: - **Clarity (1-5)**: Are instructions unambiguous? - **Safety (1-5)**: Does it avoid encouraging dangerous operations? - **Effectiveness (1-5)**: Will it reliably produce intended results? - **Completeness (1-5)**: Are edge cases addressed? - **Conciseness (1-5)**: Is it free of unnecessary verbosity? 4. **Identify improvements** — List specific weaknesses with line references 5. **Generate rewrites** — Provide improved versions preserving original intent 6. **Apply changes** — If requested, use Edit tool to apply improvements ## Output Format ``` ## Prompt Analysis: [filename] ### Scores | Dimension | Score | Notes | |-----------|-------|-------| | Clarity | X/5 | ... | | Safety | X/5 | ... | | Effectiveness | X/5 | ... | | Completeness | X/5 | ... | | Conciseness | X/5 | ... | **Overall: X/25** ### Improvements 1. [Specific improvement with before/after] ### Suggested Rewrite [Full improved prompt text] ``` ## Best Practices - Preserve the original author's intent and style - Prioritize safety improvements over stylistic ones - Keep suggestions actionable and specific - Reference marketplace conventions from CLAUDE.md - Validate frontmatter fields match the 2026 spec ## Examples ### Example 1: Improving a vague skill description **Before:** ```yaml description: Does stuff with code ``` **After:** ```yaml description: | Analyze source code for common anti-patterns and suggest refactoring improvements. Use when the user asks to "review code quality", "find code smells", or "refactor this file". ``` ### Example 2: Adding missing safety guidance **Before:** ```markdown Delete all temporary files from the project. ``` **After:** ```markdown Identify temporary files (*.tmp, *.bak, *.swp) in the project. List them for user confirmation before deletion. Never delete files outside the project root. ``` ## Prerequisites - A plugin directory containing at least one SKILL.md, command, or agent markdown file - Read access to the target plugin's `.claude-plugin/plugin.json` for context - Familiarity with the [2026 SKILL.md frontmatter spec](https://docs.anthropic.com/en/docs/claude-code/plugins) ## Output The skill produces a structured analysis report containing: - **Score card**: 5 dimensions rated 1-5 with notes and an overall score out of 25 - **Improvement list**: Specific weaknesses with file paths and line references - **Suggested rewrite**: Full improved prompt text preserving original intent ## Error Handling | Error | Cause | Resolution | |-------|-------|------------| | No SKILL.md found | Target path has no skill files | Verify the plugin path and check for `skills/*/SKILL.md` | | Invalid frontmatter | YAML parsing failure in target file | Report the specific YAML error and suggest corrections | | Empty skill body | File has frontmatter but no instructions | Flag as critical and generate a starter template | ## Resources - [Claude Code plugins documentation](https://docs.anthropic.com/en/docs/claude-code/plugins) — official plugin and SKILL.md spec - [Prompt engineering guide](https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering) — Anthropic best practices for prompt design - Marketplace conventions: see the repository CLAUDE.md for field requirements and structure
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.