Prompt Engineer

Use when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output. Do NOT use for writing a Claude Code SKILL.md — that needs skill structure rules, not prompt techniques.

116 stars 35 forksAI, LLMs & Agents

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add aakashg/pm-claude-skills --skill prompt-engineer
Manual install
git clone --depth 1 https://github.com/aakashg/pm-claude-skills.git /tmp/pm-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-claude-skills/skills/prompt-engineer ~/.claude/skills/prompt-engineer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Prompt Engineer

Diagnose a prompt, rewrite it, and show exactly what changed and why.

## Step 0 — Read first

| Source | Path | What to extract |
|--------|------|-----------------|
| The prompt | whatever the user pasted | Actual wording — never paraphrase before diagnosing |
| Failing output | the output they got, if provided | The failure mode; this determines the fix |
| Project context | `CLAUDE.md` | Audience, product, banned words, output preferences |
| Technique reference | `references/techniques.md` | Full before/after examples for each technique |

If the user pasted a prompt but no failing output, ask for one example of what it produced. Diagnosing from the prompt alone guesses at the failure mode.

## Constraints

Mandatory.

- Always show before and after. The user must see the diff, not just the result.
- Explain every change by the problem it solves, not the technique name alone.
- Preserve the user's intent. Improve how they ask, never what they are asking for.
- Right-size the fix. A 10-line prompt that works beats a 50-line prompt that confuses.
- Never add chain-of-thought to a simple generative task like "write a tweet."
- Never write "be thorough and comprehensive." Name exactly what to cover.
- Never add a role that does not match the task.
- Never add a few-shot example below the quality bar you expect back. Bad examples teach bad patterns.
- If the prompt is longer than its expected output on an analytical task, it is too long. Cut it.
Read the full skill on GitHub

Details

Skill name
prompt-engineer
Path
skills/prompt-engineer/SKILL.md
License
MIT
Repo updated
8 August 2026

FAQ

What does the Prompt Engineer skill do?

Use when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output. Do NOT use for writing a Claude Code SKILL.md — that needs skill structure rules, not prompt techniques.

How do I install the Prompt Engineer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add aakashg/pm-claude-skills --skill prompt-engineer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Prompt Engineer popular?

It lives in aakashg/pm-claude-skills, which has 116 GitHub stars and 35 forks.

Related skills

Idea Validator

116

aakashg/pm-claude-skills

Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.

Testing & QA35

Linkedin Post Writer

116

aakashg/pm-claude-skills

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.

Writing & Content35

Product Designer

116

aakashg/pm-claude-skills

Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues. Do NOT use for visual brand or aesthetic preference debates, or for reviewing copy before layout is settled.

Frontend & Design35

Super Agent

188

jaccen/Awesome-Gaussian-Skills

Design, orchestrate, and debug super agents & multi-agent LLM systems: architecture patterns (router, harness, memory, orchestration), agent-topology selection, 3D/spatial agent integration (reconstruction, SLAM, navigation, editing, CAD), and failure diagnosis. Backed by a 20-method 'Super Agents & Agentic AI' knowledge base. Use when: building multi-agent LLM pipelines, orchestrating agent teams, designing 3D-spatial agents, diagnosing multi-agent coordination failures, 超级智能体/多智能体系统/智能体编排.

AI, LLMs & Agents13

Model

155

serpro69/claude-toolbox

Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close before design. Runs upstream of feature /kk:design as the first producer of the architecture flow, and emits artifacts /kk:review-architecture verifies. Triggers: "model the domain", "build a glossary", "domain reference", "bounded context", "what are the concepts here". NOT for behavi

AI, LLMs & AgentsIn 1 list30

Product Self Knowledge

116

SeifBenayed/cloclo

Stop and consult this skill whenever your response would include specific facts about Anthropic's products. Covers: Claude Code (how to install, Node.js requirements, platform/OS support, MCP server integration, configuration), Claude API (function calling/tool use, batch processing, SDK usage, rate limits, pricing, models, streaming), and Claude.ai (Pro vs Team vs Enterprise plans, feature limits). Trigger this even for coding tasks that use the Anthropic SDK, content creation mentioning Claude capabilities or pricing, or LLM provider comparisons. Any time you would otherwise rely on memory f

AI, LLMs & AgentsIn 1 list32

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.