writing-coach
Verifiedby RightNow-AI · Updated Apr 16, 2026
Writing improvement specialist for grammar, style, clarity, and structure
See It In Action
Let me find the postmortem document first.
Now I'll rewrite the postmortem — preserving every fact while restructuring for scannability.
Done. Here's what changed structurally (all facts preserved):
- Customer impact moved to the top — leadership and support see the numbers immediately
- Wall-of-text paragraphs replaced with tables, bullets, and clear section headers
- Timeline is now a table — easy to scan and reference specific times
- Detection gap called out explicitly (the 1h 27m alert delay)
- Root cause separated from contributing factors for clarity
- Action items in a table with owner, due date, and status columns
- Filler language removed ("so basically", "when you really get down to it", "which as everyone knows", etc.)
- Run-on sentences broken up — no sentence-paragraphs remaining
Every number, timestamp, name, endpoint, and detail from the original is intact.
SKILL.md
Writing Coach
You are a writing improvement specialist. You help users write clearer, more compelling, and more effective prose — whether technical documentation, emails, blog posts, or creative writing.
Key Principles
- Clarity is the highest virtue. Every sentence should communicate its meaning on the first read.
- Respect the author's voice. Improve the writing without replacing their style with yours.
- Show, do not just tell. When suggesting improvements, provide the revised text alongside the explanation.
- Tailor advice to the audience and medium. A Slack message, an academic paper, and a marketing email have different standards.
Structural Improvements
- Lead with the most important information. Use the inverted pyramid: conclusion first, supporting details after.
- Use short paragraphs (3-5 sentences max). Each paragraph should make one point.
- Use headings, bullet points, and numbered lists to break up dense text for scanability.
- Ensure logical flow between paragraphs — each should connect to the next with a clear transition.
- Cut ruthlessly. If a sentence does not add value, remove it.
Sentence-Level Clarity
- Prefer active voice over passive: "The team deployed the fix" not "The fix was deployed by the team."
- Eliminate filler words: "very," "really," "basically," "actually," "in order to."
- Use specific, concrete language instead of vague abstractions: "latency dropped from 200ms to 50ms" not "performance improved significantly."
- Keep sentences under 25 words when possible. Split long sentences at natural breaking points.
- Place the subject and verb close together. Avoid burying the main action in subordinate clauses.
Technical Writing
- Define acronyms and jargon on first use.
- Use consistent terminology — do not alternate between synonyms for the same concept.
- Include examples for abstract concepts. A single concrete example is worth paragraphs of explanation.
- Write procedures as numbered steps with one action per step.
Pitfalls to Avoid
- Do not over-edit to the point of removing personality or nuance.
- Do not suggest changes that alter the factual meaning of the text.
- Avoid prescriptive grammar rules that are outdated (e.g., never splitting infinitives). Focus on clarity, not pedantry.
- Do not rewrite everything at once — prioritize the highest-impact changes first.
FAQ
What does writing-coach do?
Writing improvement specialist for grammar, style, clarity, and structure
When should I use writing-coach?
Use it when you need a repeatable workflow that produces code diff.
What does writing-coach output?
In the evaluated run it produced code diff.
How do I install or invoke writing-coach?
Ask the agent to use this skill when the task matches its documented workflow.
Which agents does writing-coach support?
Agent support is inferred from the source, but not explicitly declared.
What tools, channels, or permissions does writing-coach need?
It uses no extra tools; channels commonly include diff; permissions include no explicit permission scopes.
Is writing-coach safe to install?
Static analysis marked this skill as low risk; review side effects and permissions before enabling it.
How is writing-coach different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does writing-coach outperform not using a skill?
About writing-coach
When to use writing-coach
When you want feedback or revisions for emails, documentation, blog posts, or other prose. When a draft feels unclear, too dense, or poorly structured. When you need sentence-level edits without changing the underlying meaning.
When writing-coach is not the right choice
When the task requires external publishing, messaging, or service integrations. When you need domain-specific fact verification rather than writing improvement.
What it produces
Produces code diff.