hermes

Polish English written by a non-native speaker

Polishes English written by a non-native professional into natural, idiomatic text in the right register, and lists their recurring error patterns with one-line rules so they improve over time.

context

Professionals who write in English as a second language usually know exactly what they mean; the problems are articles, prepositions, verb tenses, word order, false friends, collocations ("make a research" instead of "do research"), and register that is too formal or too blunt for English readers. A plain proofread fixes the text but teaches nothing, so the same errors come back next week. The writer needs the text fixed, the few changes that affect meaning or impression called out, and their own recurring patterns explained with simple rules they can apply themselves. Over-editing is a real risk: rewriting everything into a native-speaker style the writer could never reproduce, or "correcting" valid international English, makes them feel their English is worse than it is.

task

Polish this text to natural English.Only if [WRITER_FIRST_LANGUAGE] is given: The writer's first language is .

text

  1. If the text is empty, ask for it and stop.
  2. Fix errors in grammar, articles, prepositions, tense and aspect, word order, collocations, false friends and punctuation. Replace phrases that are grammatical but unnatural with what an English-speaking professional would write.
  3. Adjust register to : for business, direct and polite, with softened requests ("Could you…" rather than "You must…") and no archaic formality ("Kindly do the needful", "Herewith"); for academic, precise and hedged appropriately; for casual, relaxed but clear.
  4. Keep the writer's meaning, structure, content and level of detail. Keep their voice: do not replace simple correct words with fancier ones, and do not change correct sentences just to sound more native.
  5. Call out the changes that matter most: anything that changed or could have changed the meaning, and anything that could make the writer sound rude, too informal or unsure. Put these first.
  6. Identify the writer's three to five recurring patterns (errors that appear more than once, or a type of error), each with an example from their text, the correction, and a one-line rule they can remember. If the first language is given and the pattern is a well-known transfer from it, mention that briefly and only when you are confident.
  7. Quote one to three phrases from their text that already work well, so they keep using them. Choose only genuinely good ones; for a very short or heavily corrected text, write "None this time" rather than praising something weak.
constraints
  • Do not add content, claims or politeness formulas the writer did not intend.
  • Keep technical terms, names, numbers and quoted material unchanged.
  • Use the spelling variety the text mostly uses (US or UK); if mixed, choose the dominant one and say so.
  • Explanations in simple English, short sentences, no linguistic jargon beyond common terms like "article" or "preposition".
  • Be encouraging and factual; do not comment on the writer's English level.
output format

Polished text

The full polished text.

Changes that matter

Up to five bullets: original → polished, and why it matters (meaning or impression).

Your patterns

Table: Pattern · Example from your text · Correction · Rule to remember.

Phrases to keep

One to three bullets quoting what already works well, or "None this time".

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
Writing and communication
category
Editing
level
Beginner
made for
Anyone, personal use, Language learner, Researcher / scientist, Software engineer
risk
read-only
version
v1.0.1 · incubating
reviewed
2026-10-03
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 edit-non-native-english --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill edit-non-native-english -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the writing-communication plugin
claude plugin install hodios-writing-communication@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Editing
PromptEditing

Proofread a text

Corrects grammar, spelling, punctuation and consistency errors in the chosen English variety, preserving the author's voice, and lists each change with the rule behind it.

proofread-text
PromptEditing

Rewrite a text for tone

Rewrites a text in a target tone or register, such as warmer, firmer or more formal, without changing its facts, asks or commitments, and shows which tone dials moved.

rewrite-for-tone
PromptLanguage learning

Correct my sentences

Corrects a learner's sentences in a target language, explains each error briefly at their CEFR level and gives a natural version. Use for writing practice and homework checks.

correct-my-sentences
PromptEditing

Simplify a text to plain language

Rewrites a text in plain language at a target reading level while keeping every fact, obligation, right, deadline and condition intact, and shows a meaning check against the original.

simplify-to-plain-language
PromptEditing

Tighten prose

Tightens prose by cutting filler, redundancy and weak verbs toward a target reduction while keeping the author's voice, meaning and necessary qualifiers, and reports what it cut.

tighten-prose
PromptEditing

Build an editorial style sheet

Builds an editorial style sheet from a manuscript, recording spelling, capitalisation, hyphenation, numbers, terms, names and formatting decisions, and flags every inconsistency with its locations.

build-style-sheet