Agent skill · Code Review & Quality

prompt-optimizer

This skill should be used when users request help optimizing, improving, or refining their prompts or instructions for AI models. Use this skill when users provide vague, unclear, or poorly structured prompts and need assistance transforming them into clear, effective, and well-structured instructions that AI models can better understand and execute. This skill applies comprehensive prompt engineering best practices to enhance prompt quality, clarity, and effectiveness.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill prompt-optimizer-ckanner-agent-skills --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/ai-llm/prompt-optimizer-ckanner-agent-skills/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 Optimizer ## Overview This skill transforms user-provided prompts into high-quality, clear, and effective instructions optimized for AI models. Apply proven prompt engineering principles to enhance clarity, specificity, structure, and effectiveness. The skill uses a systematic workflow to analyze, identify improvement opportunities, and restructure prompts based on industry best practices. ## When to Use This Skill Activate this skill when users: - Explicitly request prompt optimization or improvement - Provide vague or unclear instructions that need refinement - Ask for help making their requests more effective - Submit poorly structured prompts that would benefit from reorganization - Request guidance on how to better communicate with AI models - Present complex tasks that need to be broken down into clearer instructions ## Optimization Workflow Follow this systematic process to optimize any prompt: ### Step 1: Analyze the Original Prompt Examine the user's prompt and identify: **Clarity issues:** - Ambiguous terms or vague requirements - Implicit assumptions that should be explicit - Missing context or background information **Specificity gaps:** - Lack of concrete cons

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Optimization Workflow
  4. Step 1: Analyze the Original Prompt
  5. Step 2: Identify the Core Intent
  6. Step 3: Apply Optimization Principles
  7. Step 4: Consider Advanced Techniques
  8. Step 5: Present the Optimized Prompt
  9. Step 6: Iterate Based on Feedback
  10. Practical Guidelines
  11. Reference Resources
  12. Quality Standards
  13. Common Optimization Patterns
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the prompt-optimizer skill do?

This skill should be used when users request help optimizing, improving, or refining their prompts or instructions for AI models. Use this skill when users provide vague, unclear, or poorly structured prompts and need assistance transforming them into clear, effective, and well-structured instructions that AI models can better understand and execute. This skill applies comprehensive prompt engineering best practices to enhance prompt quality, clarity, and effectiveness.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill prompt-optimizer-ckanner-agent-skills --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