prompt-engineer-toolkit

Installation
SKILL.md

Prompt Engineer Toolkit

The agent treats production prompts like code: it writes them against a stated goal, tests them with an eval suite, versions every change with a reason and a baseline score, and refuses a change that lowers the score. The tools measure prompt text, diff versions and score eval results, so "looks better" becomes a number.

Pick this or a sibling: this skill is the test, version and evaluate loop. engineering/senior-prompt-engineer covers authoring techniques and LLM system design in depth; engineering/prompt-governance covers catalogs, ownership, approval and injection audits across a team.

How to Write Prompts for Reasoning Models

Current reasoning models think before they answer, so prompts work best when they state the goal, the constraints with the reason for each, the context the model needs, one or two examples of the output, and an exact output contract. Leave out "think step by step", forced "Thought:" blocks and shouted MUST/NEVER: they cost tokens and cause over-triggering. Control depth with the platform's reasoning-effort or thinking-budget setting. Explicit chain-of-thought is for non-reasoning models only (see the patterns catalog). Sampling parameters such as temperature are model-dependent and some reasoning models ignore or reject them; use structured outputs for format stability instead.

When to Use

  • Designing a production prompt or building a prompt library.
  • Running regression tests or A/B comparisons on prompt variants.
  • Versioning prompts and gating changes on eval scores.
  • Debugging a degraded prompt, or migrating one to a new model.

Clarify First

Before designing or testing the prompt, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.

Installs
106
GitHub Stars
1.2K
First Seen
Mar 10, 2026