Agent skill · Testing & QA

prompt-engineer

Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot learning, creating system prompts with personas and guardrails, building JSON/function-calling schemas, or developing prompt evaluation frameworks to measure and improve model performance.

Jeffallangithub.com/JeffallanGitHub ↗
claude-codeMIT
Install
npx skills add Jeffallan/claude-skills --skill prompt-engineer --agent claude-code

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

Facts
Files in the skill folder: 7
SKILL.md size: 6 KB
Bundled scripts: none
Version: 1.2.0
Declared author: https://github.com/Jeffallan
Path: skills/prompt-engineer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 10,871 · +100 this week
Language: Python
Read our review of the source →

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

From the SKILL.md

# Prompt Engineer Expert prompt engineer specializing in designing, optimizing, and evaluating prompts that maximize LLM performance across diverse use cases. ## When to Use This Skill - Designing prompts for new LLM applications - Optimizing existing prompts for better accuracy or efficiency - Implementing chain-of-thought or few-shot learning - Creating system prompts with personas and guardrails - Building structured output schemas (JSON mode, function calling) - Developing prompt evaluation and testing frameworks - Debugging inconsistent or poor-quality LLM outputs - Migrating prompts between different models or providers ## Core Workflow 1. **Understand requirements** — Define task, success criteria, constraints, and edge cases 2. **Design initial prompt** — Choose pattern (zero-shot, few-shot, CoT), write clear instructions 3. **Test and evaluate** — Run diverse test cases, measure quality metrics - **Validation checkpoint:** If accuracy < 80% on the test set, identify failure patterns before iterating (e.g., ambiguous instructions, missing examples, edge case gaps) 4. **Iterate and optimize** — Make one change at a time; refine based on failures, reduce tokens, improve relia

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Core Workflow
  3. Reference Guide
  4. Prompt Examples
  5. Zero-shot vs. Few-shot
  6. Before/After Optimization
  7. Constraints
  8. MUST DO
  9. MUST NOT DO
  10. Output Templates
  11. Coverage Note
Ships with 6 files
  • references/context-management.md
  • references/evaluation-frameworks.md
  • references/prompt-optimization.md
  • references/prompt-patterns.md
  • references/structured-outputs.md
  • references/system-prompts.md
More from claude-skills
All skills →
About this skill
What does the prompt-engineer skill do?

Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot learning, creating system prompts with personas and guardrails, building JSON/function-calling schemas, or developing prompt evaluation frameworks to measure and improve model performance.

How do I install it?

Run `npx skills add Jeffallan/claude-skills --skill prompt-engineer --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 Jeffallan/claude-skills, a repository with 10,871 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