Menu

Individual skill

prompt-optimizer

0upvotes

Diagnose and rewrite an underperforming LLM prompt so it produces reliable, well-structured output. Use when asked to improve a prompt, fix a prompt that gives inconsistent or wrong results, reduce hallucination/refusals, or make output follow a format. Produces a rewritten prompt with a diagnosis of what was failing, the specific changes and why, and a small test set to verify the fix.

plugins/pm-ai/skills/prompt-optimizer/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Prompt Optimizer Skill

A weak prompt fails in patterned ways — vague task, no output contract, buried instructions, no examples,
or asking for judgement with nothing to ground it. This skill diagnoses *which* failure mode is in play and
rewrites the prompt to fix it, then hands you a way to check the fix held — so "it's flaky" becomes a specific,
testable change rather than another round of fiddling.

## Working from a brief

You'll often get just the prompt and a vague "it's not working". **Always deliver a full rewrite anyway** —
infer the intended task and output from the prompt's wording, state your assumptions, and rewrite. If the
failing behaviour wasn't described, infer the most likely failure mode from the prompt's structure and say so.
Never hand back only a critique with no rewritten prompt.
Back to top