hermes

Improve a prompt

Diagnoses why a prompt gives weak or inconsistent results and rewrites it with clear context, task, constraints and output format while keeping its intent. Use on any prompt for any AI assistant.

context

Most weak prompts fail for a few reasons that current guidance from the major model providers agrees on: the task is implicit, the context the model needs (audience, purpose, what good looks like) is missing, instructions conflict or are buried, the output format is undefined, inputs are not separated from instructions, and there are no examples where the format is subtle. Modern models follow instructions literally, so vague requests get generic answers. Shouting (ALL CAPS, "CRITICAL", "NEVER EVER") now tends to cause over-application rather than compliance. A better prompt is usually clearer and more specific, not longer.

task

Improve this prompt for :

prompt

Only if [PROBLEM] is given: What goes wrong today:

  1. Work out the prompt's intent: the task, the audience of the output and what a good result looks like. If the intent is ambiguous in a way that changes the rewrite, list the question and state the reading you chose.
  2. Diagnose it against this checklist, citing the exact phrase for each problem:
  • task stated explicitly, as an action and a deliverable;
  • context: why, for whom, and what the model must know;
  • success criteria and a definition of done;
  • output format, length and structure;
  • constraints phrased as what to do, with the reason when it is not obvious;
  • conflicting, duplicated or buried instructions;
  • variable inputs separated from instructions (delimiters or tags) and placeholders kept;
  • examples, when the format or tone is hard to describe, varied enough not to be copied literally;
  • guardrails for facts: what to do when information is missing instead of guessing;
  • filler, vague role-play ("you are a world-class expert") and emphasis that does not change behaviour.
  1. Rewrite the prompt: keep every requirement and placeholder the author had, fix each diagnosed problem, and order it as context, task, constraints, output format, then examples.
  2. Propose two or three test inputs, including one edge case, that would show whether the new version beats the old one.
constraints
  • Keep the author's intent, scope and placeholders exactly; do not add features, tools or requirements they did not ask for. Put suggestions for extra scope under What changed, labelled as optional.
  • Make the prompt as short as it can be while still complete. Do not pad it with generic advice.
  • Stay model-agnostic unless the target names a specific tool; then use that tool's conventions only where they matter.
  • Do not claim the new prompt will perform better; say how to test it.
output format

Diagnosis

A table: problem | evidence (quoted phrase) | fix.

Improved prompt

The full rewritten prompt in one fenced block, ready to paste.

What changed

At most six bullets, most important first.

Test it

Two or three test inputs and what a good output should do for each.

1 required value still a placeholder; the assistant will ask for it.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Prompting and assistants
category
Prompt engineering
level
Intermediate
depth
Start here
risk
read-only
version
v1.0.1 · experimental
reviewed
2026-10-02
aliases
ai-prompt-eng
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install improve-prompt --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill improve-prompt -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the prompting plugin
claude plugin install hodios-prompting@hodios

The plugin brings every entry in this domain at once.

more in prompt engineering

All of Prompt engineering
PromptPrompt engineering

Learn prompting basics

Teaches prompting basics interactively on the learner's own tasks, one technique at a time, with before-and-after prompts, a short exercise and feedback. For beginners to AI assistants.

learn-prompting-basics
PersonaPrompt engineering

AI literacy coach

AI literacy coach who teaches people to use assistants well and critically - what they are good at, how they fail, how to verify outputs and protect privacy. Use for learning to work with AI.

ai-literacy-coach
PromptPrompt engineering

Compress a prompt

Shortens a long prompt while preserving its behaviour, maps every original instruction to where it now lives, reports the real size reduction and lists test inputs to check nothing changed.

compress-prompt
PromptPrompt engineering

Create few-shot examples

Builds a small set of diverse, representative few-shot examples for a task, including tricky and negative cases, balanced so the model learns the rule rather than copying surface patterns.

create-few-shot-examples
PromptPrompt engineering

Diagnose prompt failures

Diagnoses why a prompt produces bad answers from failing examples, traces each failure to a root cause, proposes targeted fixes and a quick regression test set.

diagnose-prompt-failures
PersonaPrompt engineering

Prompt engineer

Prompt engineer who writes clear, testable instructions, iterates against real examples and evals, and avoids model-specific tricks. Use for designing, debugging and maintaining prompts.

prompt-engineer