Agent skill · Code Review & Quality

prompt-improvement

Meta-skill for improving and optimizing prompts using Anthropic's prompt engineering best practices. Provides the 4-step improvement workflow (example identification, initial draft, chain of thought refinement, example enhancement), keyword registries for documentation lookup, and decision trees for improvement strategies. Use when improving prompts, optimizing for accuracy, adding chain of thought reasoning, structuring with XML tags, enhancing examples, or iterating on prompt quality. Delegates to docs-management skill for official prompt engineering documentation.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill prompt-improvement --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 11 KB
Bundled scripts: none
Allowed tools: ReadGlobGrepSkillBash
Path: skills/ai-llm/prompt-improvement/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Prompt Improvement ## MANDATORY: Query Official Documentation First > **STOP - Before improving ANY prompt, you MUST invoke the docs-management skill.** > > This is NOT optional guidance - it is a required execution step. ### Required: Query Documentation via docs-management Skill **Invoke the `docs-management` skill BEFORE making any improvements:** Search for relevant documentation using natural language: - Primary query: "prompt engineering chain of thought XML tags" - Read the top results returned by the skill ### Why Documentation Query is Required - **Training data is stale** - Your knowledge may be outdated - **Official docs are canonical** - Anthropic's current best practices - **Prevents hallucination** - Ground improvements in real documentation - **Ensures accuracy** - Latest Claude 4.x guidance ### Recommended Query Topics Query at least ONE of these topics based on your improvement needs: - **Chain of thought:** "chain of thought thinking tags reasoning" - **XML structure:** "XML tags structure prompts formatting" - **Examples/multishot:** "multishot prompting examples few-shot" - **Claude 4.x best practices:** "Claude 4 prompting best practices" ### Verification Che

What's inside
Steps it walks through
  1. MANDATORY: Query Official Documentation First
  2. Required: Query Documentation via docs-management Skill
  3. Why Documentation Query is Required
  4. Recommended Query Topics
  5. Verification Checkpoint
  6. Overview
  7. When to Use This Skill
  8. Quick Decision Tree
  9. The 4-Step Improvement Workflow
  10. Step 1: Example Identification
  11. Step 2: Initial Draft
  12. Step 3: Chain of Thought Refinement
  13. Step 4: Example Enhancement
  14. What You Get After Improvement
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the prompt-improvement skill do?

Meta-skill for improving and optimizing prompts using Anthropic's prompt engineering best practices. Provides the 4-step improvement workflow (example identification, initial draft, chain of thought refinement, example enhancement), keyword registries for documentation lookup, and decision trees for improvement strategies. Use when improving prompts, optimizing for accuracy, adding chain of thought reasoning, structuring with XML tags, enhancing examples, or iterating on prompt quality. Delegates to docs-management skill for official prompt engineering documentation.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill prompt-improvement --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going