Agent skill · Code Review & Quality

prompt-engineering-patterns

This skill should be used when the user asks to "optimize a prompt", "improve prompt performance", "design a prompt template", "write better prompts", "debug prompt issues", "use chain-of-thought", "structured prompting", "few-shot prompting", or wants to apply advanced prompt engineering patterns for production LLM applications.

Seth Hobson38,331★ · +219/wk · 1 repos on radarProfile →
claude-codecodexcopilotcursorships scriptsMIT
Install
npx skills add wshobson/agents --skill prompt-engineering-patterns --agent claude-code

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

Facts
Files in the skill folder: 10
SKILL.md size: 5 KB
Bundled scripts: yes
Path: plugins/llm-application-dev/skills/prompt-engineering-patterns/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 38,479 · +148 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 Engineering Patterns Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability. ## When to Use This Skill - Designing complex prompts for production LLM applications - Optimizing prompt performance and consistency - Implementing structured reasoning patterns (chain-of-thought, tree-of-thought) - Building few-shot learning systems with dynamic example selection - Creating reusable prompt templates with variable interpolation - Debugging and refining prompts that produce inconsistent outputs - Implementing system prompts for specialized AI assistants - Using structured outputs (JSON mode) for reliable parsing ## Core Capabilities ### 1. Few-Shot Learning - Example selection strategies (semantic similarity, diversity sampling) - Balancing example count with context window constraints - Constructing effective demonstrations with input-output pairs - Dynamic example retrieval from knowledge bases - Handling edge cases through strategic example selection ### 2. Chain-of-Thought Prompting - Step-by-step reasoning elicitation - Zero-shot CoT with "Let's think step by step" - Few-shot CoT with reasoning traces - Self-consistency tec

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Core Capabilities
  3. 1. Few-Shot Learning
  4. 2. Chain-of-Thought Prompting
  5. 3. Structured Outputs
  6. 4. Prompt Optimization
  7. 5. Template Systems
  8. 6. System Prompt Design
  9. Quick Start
  10. Detailed patterns and worked examples
  11. Best Practices
  12. Common Pitfalls
  13. Success Metrics
Ships with 9 files
  • assets/few-shot-examples.json
  • assets/prompt-template-library.md
  • references/chain-of-thought.md
  • references/details.md
  • references/few-shot-learning.md
  • references/prompt-optimization.md
  • references/prompt-templates.md
  • references/system-prompts.md
  • scripts/optimize-prompt.py
More from agents
All skills →
About this skill
What does the prompt-engineering-patterns skill do?

This skill should be used when the user asks to "optimize a prompt", "improve prompt performance", "design a prompt template", "write better prompts", "debug prompt issues", "use chain-of-thought", "structured prompting", "few-shot prompting", or wants to apply advanced prompt engineering patterns for production LLM applications.

How do I install it?

Run `npx skills add wshobson/agents --skill prompt-engineering-patterns --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 wshobson/agents, a repository with 38,479 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