prompt-engineer

Skill Directory

Resolve SKILL_DIR to the absolute directory containing this SKILL.md, as shown by the current host, before using any bundled path below. Before a shell command uses $SKILL_DIR, assign it in that command or replace it with the resolved path. It is not a host-exported environment variable.

Prompt Optimizer

Optimizes system prompts by applying research-backed prompt engineering patterns. This skill operates through human-in-the-loop phases: understand, plan, propose changes, receive approval, then integrate.

Purpose and Success Criteria

A well-optimized prompt achieves three things:

1. Behavioral clarity: The agent knows exactly what to do in common cases and how to handle edge cases.
2. Appropriate scope: Complex tasks get systematic decomposition; simple tasks don't trigger overthinking.
3. Grounded changes: Every modification traces to a specific pattern with documented behavioral impact.

Optimization is complete when:

• Every change has explicit pattern attribution from the reference document
• No section contradicts another section
• The prompt matches its operating context (tool-use vs. conversational, token constraints, failure modes)
• Human has approved both section-level changes and full integration

When to Use This Skill

Use when the user provides a prompt and wants it improved, refined, or reviewed for best practices.

Do NOT use for:

• Writing prompts from scratch (different skill)
• Prompts that are already working well and user just wants validation (say so, don't force changes)
• Non-prompt content (documentation, code, etc.)

Required Resources

Before ANY analysis, read the appropriate pattern reference(s). Each reference contains a Technique Selection Guide table mapping domains, trigger conditions, stacking compatibility, conflicts, and expected effects.

Single-Turn Reference (Always Read)

$SKILL_DIR/references/prompt-engineering-single-turn.md