القائمة
Use this skill when the user wants to polish the wording of plain text documents and English embedded in source code, cutting filler and AI tells.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use this skill when the user wants to diagnose flaws in argumentation in English prose, without rewriting it.
Use this skill when the user wants to proofread a `.srt` subtitle file produced by Whisper or another voice-to-text engine.
Use this skill when the user wants to format plain text documents with one sentence per line.
استنادا إلى تصنيف SOC المهني
| name | rewrite-prose |
| description | Use this skill when the user wants to polish the wording of plain text documents and English embedded in source code, cutting filler and AI tells. |
Preserve tone of voice. Preserve meaning exactly. Ask author when sentence is ambiguous. Replace awkward constructions with cleaner ones of same meaning.
Use present tense instead of will, except when future is point.
Cut clichés like at the end of the day or needless to say.
Cut low-hanging fruit and circle back too.
Cut tautologies like end result, each and every, or free gift.
Cut throat-clearing openers like it is worth noting or here is the thing.
Cut manufactured not just X, but Y contrast and state point directly.
Replace vague declarative like the reasons are structural with specifics.
Drop empty absolutes like always or never unless they hold literally.
Rewrite any sentence engineered to read like pull-quote.
Use Oxford comma in lists of three or more.
Complete every list or name its category.
Drop trailing etc., and so on, and so forth, or ellipses.
Separate two clauses with period or recast sentence rather than em dash.
Prefer active voice unless actor is unknown or irrelevant.
Give every verb subject that can perform it.
Cut false agency where abstraction acts like person.
Name real actor in phrases like the decision emerges.
Cut filler words like very, really, just, and actually.
Cut basically and essentially too.
Replace very X with stronger single word.
Replace in order to with to.
Prefer Anglo-Saxon words over Latinate.
Use use instead of utilize, and start instead of commence.
Drop that when removal does not hurt readability.
Replace double negatives like not uncommon with positive word.
Keep parallel grammar across list items.
Resist reflexive three-item rhythm when two items say enough.
Vary sentence length so rhythm never turns metronomic.
Split sentences carrying two ideas joined by and or but.
Lead with real subject instead of there is or there are, which delay it.
Cut hedging words like perhaps, maybe, arguably, and sort of.
Use them only when uncertainty is real.
When writing for AI agents, place one thought per paragraph. Headings carry no trailing period. In Markdown, place URLs at bottom as reference definitions. Use shortcut links in body text.
Spell numbers one through nine as words. Write numbers from ten upward as digits. Keep digits in tables, code, versions, and measurements.
Preserve author's vocabulary and stylistic choices. Preserve quoted text, code, and proper names. Preserve domain jargon that already follows its field's convention. Make smallest change that fixes problem.
Show original next to non-trivial rewrite. Ask author to confirm meaning survives. Read result once and remove anything that still sounds machine-generated.
Reflow every touched sentence when file uses one-sentence-per-line layout. Leave existing line breaks alone otherwise.
Polish this draft.
At the end of the day, we utilized the system in order to basically improve things.
Return this version.
We used the system to improve throughput.