Skip to main content
skill CX Codex

prompt-optimize — Claude Code skill: what it does, how to install

prompt-optimize is a Claude Code skill that iteratively refines an existing prompt against your evaluation command, keeping only edits that improve the score.

MIT ★ 185 updated 2026-06-30

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add gaasher/Agent-Loop-Skills
/plugin install agent-loops@agent-loop-skills
Open on GitHub

What prompt-optimize does

The skill runs an evolutionary optimization loop around a single prompt file. Each round identifies the main weakness in the current draft and applies one targeted operator: clarity, extra context, explicit examples, decomposition, structure, or guardrails. It then runs your evaluation command, reads the score from the final output line, and keeps the change if the metric improved. Otherwise, it reverts back to the previous best snapshot stored in ./sandbox.

The loop runs until it hits your target score, runs out of iteration budget (10 by default), or plateaus after several non-improving attempts. The evaluation script is treated as a black box and never modified.

Running this loop requires an existing prompt and a working evaluation command. It will not write a brand-new prompt from scratch or tune model hyperparameters. The command must emit either a raw number or a JSON object containing a score key on its last line.

What it helps with

  • raise an existing prompt's accuracy against automated benchmark scripts
  • search for better prompt formulations without manual rollbacks of degraded scores
  • diagnose prompt weaknesses using metric scores and returned test feedback
  • track iterative prompt snapshots and outcomes in a structured ledger file

Example prompts for the agent

  • Optimize the prompt in prompts/classifier.txt using python evaluate.py
  • Improve system_prompt.md to hit a 0.90 score running npm run bench:eval
  • Run the prompt optimization loop on prompt.txt using pytest eval_suite.py with a budget of 12

How to install prompt-optimize

1Plugin marketplace

/plugin marketplace add gaasher/Agent-Loop-Skills
/plugin install agent-loops@agent-loop-skills

This installs the whole agent-loops plugin with all its skills

2Skills CLI (Vercel)

npx skills add gaasher/Agent-Loop-Skills --skill prompt-optimize -a claude-code

3Manually: put the files in place

~/.claude/skills/prompt-optimize/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/prompt-optimize/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about prompt-optimize

How to install prompt-optimize in Claude Code?

Add the marketplace source with /plugin marketplace add gaasher/Agent-Loop-Skills, then run /plugin install agent-loops@agent-loop-skills.

What does prompt-optimize do?

It applies single-operator adjustments to a prompt file, checks each modification with your evaluation command, and keeps only the edits that increase your metric.

What output format does the evaluation command need?

The evaluation command must print either a bare scalar number or a JSON line like {"score": <number>, "feedback": "..."} on its very last line.

Source text

SKILL.md · MIT
---
name: prompt-optimize
description: >
  Use when the user has a prompt that feeds a system they can already score, and wants that prompt
  automatically improved to raise the score against their own evaluation command. Makes one targeted
  quality edit per iteration — clarity, context, specificity, structure, examples, decomposition,
  guardrails — re-runs the user's eval to measure the metric, and keeps the edit only if the metric
  improves, else reverts; loops to a target, plateau, or budget. The metric is whatever the user's
  eval command prints (task accuracy, an LLM-judge score, a pass rate, a tool-call success rate); the
  loop is metric-agnostic and never edits the eval. Not for writing a prompt from scratch, not for
  tuning model weights or hyperparameters, and not for one-off manual prompt edits without a score.
metadata:
  version: "0.1.0"
---

# Prompt Optimize Loop

An **evolutionary optimizer for a prompt** (OpenEvolve / AlphaEvolve-style). The artifact is a prompt
that feeds the user's system; the feedback signal is a **scalar metric printed by the user's own
evaluation command**. Each iteration proposes one quality-focused edit, re-runs the eval, and keeps
the edit only if the metric improves — evolving the prompt toward higher scores. The eval is a
black-box oracle the loop runs but never edits, so the optimization tracks what actually matters
rather than gaming a number.

## When to use

Use this when the user has a prompt and a command that scores the system using it, and wants the
prompt improved to raise that score. Default to diagnosing the prompt's biggest current weakness each
round and applying the one operator that addresses it; if the eval feedback points elsewhere, follow
the feedback. Not for authoring a prompt from nothing, tuning weights/hyperparameters, or making a
single manual edit with no score to compare against.

## Setup

Resolve bindings interactively. If `loop.run.yaml` exists in the working dir, load it, confirm the
values in one line, and skip to the loop. Otherwise: on Claude Code (the `AskUserQuestion` tool is
available) infer a likely value for each binding and present it as the recommended option; on other
hosts ask each as a quoted plain-text prompt. Then write `loop.run.yaml` (format:
`examples/run.example.yaml`) and confirm the values before creating any other files.

| binding | meaning | default | how to infer |
|---|---|---|---|
| `<prompt_file>` | the prompt to optimize — the artifact the loop evolves | — | scan the working dir for the prompt/template file the eval reads |
| `<eval_cmd>` | **required.** Command that scores the current `<prompt_file>`; prints the metric (see output convention below). Treated as a black box — never edited | — | ask the user; look for `eval`/`score`/`bench` scripts |
| `<objective>` | `maximize` or `minimize`, plus one line on what the metric measures | `maximize` | ask the user |
| `<target>` | optional score at which to stop early | — | ask the user; else leave unbound |
| `<sandbox_root>` | where prompt snapshots + ledger live | `./sandbox` | — |
| `<budget>` | max iterations | 10 | — |
| `<patience>` | stop after N consecutive non-improving iterations (plateau) | 3 | — |

**Eval output convention.** `<eval_cmd>` must print, on its **last line**, either a JSON object
`{"score": <number>, "feedback": "<optional notes/errors>", ...any extra metrics...}` or a bare
number. Higher is better unless `<objective>` is `minimize`. The `feedback` field, when present, is
the richest signal — read it like AlphaEvolve's artifacts side-channel to decide the next edit.

**Eval runs in the user's environment.** `<eval_cmd>` may call an inference endpoint or any tooling the
user has installed; the loop just shells out and reads the last line. If instead the prompt is executed
by *you* (interactive development with no separate endpoint), first run the current prompt over the
user's eval inputs to produce outputs, write them where `<eval_cmd>` reads, then run `<eval_cmd>` to
score them.

## The loop

Copy this checklist and tick items off:
- [ ] Iteration 0 — baseline: run `<eval_cmd>` on `<prompt_file>`, record its score as the current best, snapshot the prompt.
- [ ] Diagnose the prompt's single biggest weakness from the latest score, the eval feedback, and the history.
- [ ] Apply one targeted edit (one operator from the toolkit) to `<prompt_file>`.
- [ ] Measure: re-run `<eval_cmd>` and read the new score from its last line.
- [ ] Keep if the metric improves (require a margin if the eval is stochastic), else revert to the best snapshot.
- [ ] Append a ledger row; if stuck, branch from an earlier high-scoring variant; stop on `<target>`, plateau (`<patience>`), or `<budget>`.

**Iteration 0 — baseline.** Run `<eval_cmd>`, record its score as the best, snapshot `<prompt_file>`
to `<sandbox_root>/iter0/`, and start the history (`{iter, edit, score, feedback}` per row).

**Then, until stop (target, plateau, or budget):**

1. **Diagnose.** From the latest score, the `<eval_cmd>` feedback, and recent history, name the
   prompt's single biggest current weakness — the one thing most likely holding the metric back.
2. **Make one targeted edit** — pick the toolkit operator that addresses that weakness:
   - **Clarity** — remove ambiguity, contradictions, and vague wording.
   - **Context** — supply missing domain knowledge, definitions, or background the task needs.
   - **Specificity** — make instructions concrete; pin down the output format; define what "good" is.
   - **Structure** — order the prompt into steps/sections; add a short checklist.
   - **Examples** — add one or two demonstrations of the desired input → output.
   - **Decomposition** — split a complex instruction into explicit ordered sub-steps.
   - **Guardrails** — state edge cases and what to avoid.

   One change per iteration, so its effect on the metric is attributable.
3. **Measure.** Snapshot the edited prompt to `<sandbox_root>/iter<N>/`, run `<eval_cmd>`, and read the
   new score off the last line.
4. **Keep or revert.** **Keep** if the metric improves per `<objective>` (if the eval is stochastic,
   require a small margin so noise alone does not drive a keep); otherwise **revert** `<prompt_file>`
   to the previous best snapshot. Append `{edit, score, feedback}` to the history either way.
5. **Escape local optima.** If the score has not improved for a couple of iterations, stop making tiny
   tweaks — branch from an earlier high-scoring snapshot, or try a bolder restructuring (a different
   decomposition, a fresh set of examples). Diversity beats grinding the same local hill.

When stopping, restore the **best** prompt to `<prompt_file>` and report the score trajectory, which
edits moved the metric (and which did not), and the final prompt.

## Ledger

`<sandbox_root>/ledger.tsv`, tab-separated, never commas in the text. Header:
```
iter	score	status	edit
```
`status` ∈ {`baseline`, `keep`, `revert`}. Example (metric = task accuracy, maximize):
```
iter	score	status	edit
0	0.42	baseline	original prompt
1	0.61	keep	specificity: define each output label and the exact output format
2	0.61	revert	examples: add 3 few-shot demos — no metric gain
3	0.78	keep	context: add the domain rules the task assumes but never states
```
Report the **best** iteration, not necessarily the last.

## Constraints
- **The metric is the user's.** Never edit `<eval_cmd>`, its data, or its scoring — that games the
  number instead of improving the prompt, and the eval is the only ground truth the loop has.
- **Optimize the prompt only, and preserve the task's intent.** Improve *how* the task is instructed,
  not *what* is being asked; do not tailor the prompt to exploit eval quirks that would break real use.
- **One edit per iteration**, and compare the *metric* by re-running the full `<eval_cmd>`, not a single
  sample, so each score delta is attributable to that one edit.
- **Report the best variant, not the last.** The sandbox is self-contained — no `../` escapes.
- Do not pause the loop to ask whether to continue; run until target, plateau, or budget.

## Stops
- **Target** — the score reaches `<target>` (if set).
- **Plateau** — no iteration improved the best for `<patience>` consecutive rounds (every non-improving
  iteration counts toward patience; a keep resets it).
- **Budget** — `<budget>` iterations reached.

© gaasher · MIT · gaasher/Agent-Loop-Skills

Similar skills

All skills for AI and ML →

From the same set26

The whole set →
literature-search literature-search searches academic papers across Semantic Scholar and arXiv, walks citation trees, and extracts snippets using only the Python standard library. CX Codex +1 ★ 185repo stars data-analysis The data-analysis skill explores a dataset by testing hypotheses and writes up findings backed by reproducible numbers. Use it for open-ended discovery, not to diagnose a known failure. CX Codex +1 ★ 185repo stars red-team red-team finds weaknesses in content filters, classifiers and APIs through adversarial stress-testing — generates attack inputs and builds a catalogue of failures. CX Codex +1 ★ 185repo stars anomaly-investigation anomaly-investigation is a Claude Code skill that investigates a known spike, drop, or outlier by testing possible causes against data. CX Codex +1 ★ 185repo stars power-analysis power-analysis is a Claude Code skill for sizing a two-group study and drafting its preregistration. It runs during planning, before data collection, for A/B tests, simple RCTs, and evaluations of two models or configurations. CX Codex +1 ★ 185repo stars claim-verify claim-verify is a Claude Code skill that checks data-backed claims in draft reports against raw datasets. It recalculates metrics and stress-tests fragile conclusions. CX Codex +1 ★ 185repo stars literature-survey literature-survey is a Claude Code skill that maps research sources against claims. It runs for questions that need a cited survey of agreement, disputes, and gaps. CX Codex +1 ★ 185repo stars optimize-loop optimize-loop is a skill that runs an edit-measure-revert loop for code modules or SQL queries, keeping changes only when correctness holds and a cost metric falls. CX Codex +1 ★ 185repo stars

Project sponsors

Companies that keep this analytics open