agentleFS
ntaffziintaffzii/Skill-Agents/skills/productivity/prompt-improvement/SKILL.md

prompt-improvement

Skill4 starsChanged 3 months agoMITView on GitHub

Improve vague, incomplete, ambiguous, risky, or poorly structured prompts into clear executable prompts for AI agents, coding assistants, automations, reports, research, or model-specific workflows. Use when the user asks to rewrite, clarify, optimize, score, translate, structure, or improve a prompt.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    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:

    Do not invent requirements.

    line 21
  2. Distinctive:

    Ask 1 to 3 concise questions only when missing information changes the correct outcome.

    line 24
  3. Distinctive:

    Add context, requirements, process, output format, quality rules, and language guidance only when useful.

    line 29
  4. Distinctive:

    Keep identifiers, file paths, commands, schema keys, model IDs, and API names unchanged.

    line 30
  5. Distinctive:

    Keep reusable model-facing prompt text in English when it improves portability.

    line 76
  6. Distinctive:

    Do not make prompts longer unless the added structure improves execution.

    line 77
  7. Distinctive:

    Do not remove explicit constraints.

    line 78
  8. Distinctive:

    Do not convert uncertainty into fact.

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Improvement

Turn rough intent into a clear prompt without changing what the user asked for.

Core Principle

Preserve explicit intent. Add assumptions only when labeled.

Workflow

  1. Classify the problem
    • Identify whether the prompt is vague, ambiguous, overbroad, missing inputs, missing output format, missing audience, risky, or already good enough.
  2. Extract intent
    • Separate explicit requirements, inferred goals, missing information, assumptions, constraints, and risks.
    • Do not invent requirements.
  3. Decide whether to ask or rewrite
    • Ask 1 to 3 concise questions only when missing information changes the correct outcome.
    • Proceed with assumptions for low-risk drafting, brainstorming, research, reports, templates, and clear-enough tasks.
  4. Rewrite
    • Make the task executable.
    • Add context, requirements, process, output format, quality rules, and language guidance only when useful.
    • Keep identifiers, file paths, commands, schema keys, model IDs, and API names unchanged.
  5. Check fidelity
    • Confirm the rewrite preserves the user's request.
    • Remove hidden goals.
    • Mark assumptions and open questions clearly.

Default Output

## Improved Prompt

```text
[Prompt ready to use]

What Changed

Assumptions

Questions


## Reusable Prompt Skeleton

```text
Role:

Task:

Context:

Requirements:

Process:

Output Format:

Quality Rules:

Language And Tone:

Rules

  • Respond in the user's language.
  • Keep reusable model-facing prompt text in English when it improves portability.
  • Do not make prompts longer unless the added structure improves execution.
  • Do not remove explicit constraints.
  • Do not convert uncertainty into fact.

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.