write-better
Improve, rewrite, edit, or review prose so it is clear, direct, useful, and natural without inventing facts or erasing the author's voice. Use when drafting or revising emails, documentation, reports, essays, messages, UI copy, explanations, or other prose; when the user asks to write better, humanize text, remove AI-sounding language, tighten wording, improve clarity or tone, or make an action easier to understand. Do not use for translation or factual research unless writing quality is also part of the request.
plannotator · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add plannotator/write-better --skill write-better技能说明
name: write-better description: Improve, rewrite, edit, or review prose so it is clear, direct, useful, and natural without inventing facts or erasing the author's voice. Use when drafting or revising emails, documentation, reports, essays, messages, UI copy, explanations, or other prose; when the user asks to write better, humanize text, remove AI-sounding language, tighten wording, improve clarity or tone, or make an action easier to understand. Do not use for translation or factual research unless writing quality is also part of the request.
Writing guidance for AI agents
Write so the reader understands the point, the evidence, and the next action without rereading. Protect the reader's attention. Prefer plain language, concrete details, and useful structure.
1. Start with the useful part
Put the main point in the first one or two sentences.
For professional communication, lead with one of these:
- the request
- the decision
- the conclusion
- the result
- the problem
- the relevant fact
Add context after the reader knows why they are reading.
Bad:
I wanted to reach out to provide some context regarding the project timeline.
Better:
The release will move from May 12 to May 19 because the payment tests are still failing.
Brief context may come first when the reader needs it to interpret sensitive, legal, safety-related, or surprising information correctly.
2. Make every sentence earn its place
Every sentence should change what the reader knows, decides, or does.
A sentence may contribute:
- a fact
- a definition
- a reason
- evidence
- a condition
- a constraint
- a consequence
- an exception
- a warning
- a decision
- an action
- a concrete example
Delete sentences that only announce, emphasize, summarize, or decorate a point already made.
Common filler:
- "That distinction matters."
- "It is important to note that..."
- "The practical mental model is simple."
- "This highlights the importance of..."
- "Here is what you need to know."
- "In today's rapidly changing environment..."
- "At its core..."
- "The real question is..."
State the information instead.
3. Preserve information, not length
Keep the original facts, requirements, qualifications, and necessary examples.
You may:
- delete empty sentences
- merge paragraphs
- remove repeated explanations
- shorten examples
- reorder information
- replace abstractions with concrete language
Do not preserve the original paragraph count or sentence count. A padded five-paragraph draft may need to become two paragraphs.
4. Use plain language
Prefer familiar words and direct constructions.
Use:
- "use" instead of "utilize"
- "help" instead of "facilitate"
- "improve" instead of "enhance"
- "use" instead of "leverage"
- "is" instead of "serves as"
- "has" instead of "boasts"
- "can" instead of "has the ability to"
Treat these words as warnings:
delve, leverage, robust, seamless, streamline, utilize, comprehensive, holistic, facilitate, optimize, harness, navigate, landscape, realm, foster, empower, crucial, essential, pivotal, significantly
Keep one when it has a precise technical meaning. Remove it when it adds polish without precision.
Good:
The compiler optimizes repeated lookups.
Weak:
The platform optimizes the customer journey through seamless automation.
5. Be concrete
Use names, dates, numbers, owners, systems, and observable actions.
Weak:
We should improve cross-functional alignment to streamline delivery.
Better:
Priya will send the revised API schema to the mobile team by Tuesday. The team will confirm the migration date by Thursday.
Prefer language the reader can picture happening.
Replace abstract nouns with actions when possible:
- "conduct an evaluation of" becomes "evaluate"
- "make a determination" becomes "decide"
- "provide assistance" becomes "help"
- "perform an inspection" becomes "inspect"
6. Put actions in usable form
For requests, specify:
- who should act
- what they should do
- when it is due
- what completion looks like
Weak:
Let me know your thoughts.
Better:
Please confirm the revised launch date by Thursday at 3 p.m.
Prefer one main outcome per message. Several related actions may appear together when each one is explicit. Number them when order, ownership, or completion matters.
7. Match the genre
Clarity does not require the same voice everywhere.
For documentation:
- describe current behavior
- explain how to use it
- state constraints and failure conditions
- include examples only when they remove ambiguity
- avoid promotional language and personality
For workplace messages:
- use the tone appropriate to the relationship
- keep politeness brief
- make the request easy to identify
- avoid unnecessary formality
For essays and personal writing:
- preserve genuine opinions, uncertainty, humor, and irregularities
- do not manufacture quirks to appear human
- do not add tangents, fragments, or fake self-corrections unless they belong to the author's voice
Match the genre before matching stylistic mannerisms.
8. Preserve the author's voice
When a writing sample is available, study:
- sentence length
- vocabulary
- paragraph openings
- punctuation
- degree of formality
- transition habits
- humor
- recurring phrases
Keep meaningful irregularities. Do not replace the author's voice with a generic casual style.
Do not add personality merely to signal that a human wrote the text.
9. Avoid rhetorical packaging
Do not turn ordinary information into slogans, aphorisms, or miniature speeches.
Avoid formulas such as:
- "It is not X. It is Y."
- "It is not just about X. It is about Y."
- "X is the language of Y."
- "X becomes a trap."
- "The future of X is Y."
- "What really matters is..."
- "The heart of the matter is..."
Use corrective contrast only when the reader is likely to hold the mistaken belief and correcting it affects their actions.
Weak:
阅读完整来源 ↗This is not merely a performance improvement.