agentleFS
ji-hun-gitji-hun-git/how-to-use-ai/skills/prompt-improver/SKILL.md

prompt-improver

Skill0 starsChanged 7 days agoMITView on GitHub

Turns a rough request or weak prompt into a strong one. Use when the user asks to write, improve, review or debug a prompt, system prompt, custom instructions, an agent's instructions, or a reusable template; or when a prompt keeps producing poor results. Checks the six elements (role, context, instruction, format, constraints, examples), predicts likely failures, and returns a tested, leaner prompt.

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Constraints: only the rules that truly matter (about five or fewer), each with a reason

    line 18
  2. Distinctive:

    Role: only for tone or perspective.

    line 20
  3. Distinctive:

    Trim: Remove ALL-CAPS emphasis, "think step by step" for reasoning models, threats, tips, flattery of the model, and duplicate rules.

    line 23

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Prompt improver

Good prompts are not long; they leave little for the model to guess. Improve prompts by filling the gaps that cause failures and deleting what doesn't help.

Steps

  1. Understand the job. Identify the task, audience, where the output will be used, and what "done" looks like. If these are missing and matter, ask (at most three questions).
  2. Check the six elements and note what's missing or weak:
    • Context (most important): purpose, audience, situation, source material
    • Instruction: the exact action and the done criteria
    • Format: structure, length, tone
    • Constraints: only the rules that truly matter (about five or fewer), each with a reason
    • Examples: 2–5 varied examples if style or format is hard to describe (try none first for reasoning models)
    • Role: only for tone or perspective; it doesn't improve accuracy
  3. Predict failures. List the most likely ways the prompt could fail: misunderstanding (ambiguity), omission (too many requirements, buried in a long input), fabrication (no source, no permission to say "I don't know"), sycophancy (asking for opinions on "my" work).
  4. Rewrite. Return the improved prompt in a code block. Put long documents first and the question last; separate parts with consistent tags or headings; add "If something isn't in the material, say so" where facts matter. Use clearly marked placeholders for facts you don't have (policies, prices, limits, names), and keep invented example values out of the prompt: the model will treat them as real.
  5. Trim. Remove ALL-CAPS emphasis, "think step by step" for reasoning models, threats, tips, flattery of the model, and duplicate rules.
  6. Explain and test. Give a short table of what changed and why, and suggest 3–5 test inputs (including an edge case) to compare old vs. new.

Evidence

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.