# Polish Writing

> Proofreads and improves professional writing for US business contexts before it is sent, finalized, or published. Use when editing emails, memos, proposals, reports, announcements, presentations, documentation, or any draft the user asks to proofread, polish, enhance, finalize, publish, or send.

- Skill: `gabepublic/polish-writing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add gabepublic/polish-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gabepublic/polish-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: gabepublic (https://skillmd.com/u/gabepublic)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/gabepublic/polish-writing

---


# Polish Writing

## Purpose

Use this skill to proofread and enhance the user's writing before it is sent, finalized, or published. Focus on US business-writing standards: clear purpose, reader-first structure, concise language, professional tone, correct grammar, and practical next steps.

## Core Standards

- Write for the intended audience and their current level of context.
- Put the main point, request, or recommendation near the top.
- Use active voice unless passive voice is more diplomatic or legally necessary.
- Prefer simple, familiar words over jargon, inflated phrasing, or corporate filler.
- Remove unnecessary words, repeated ideas, excess modifiers, and doublets.
- Keep terminology consistent throughout the piece.
- Use US English spelling, punctuation, date style, and business conventions unless the user specifies another locale.
- Maintain a respectful, inclusive, confident, and professional tone.
- Preserve the user's meaning, facts, commitments, and personal voice.

## Workflow

1. Identify the writing type, audience, purpose, desired action, and sensitivity.
2. If critical context is missing and the edit could change intent, ask up to three targeted questions. Otherwise, proceed with stated assumptions.
3. Proofread for grammar, spelling, punctuation, capitalization, formatting, and consistency.
4. Improve clarity, structure, flow, concision, tone, and reader orientation.
5. Check whether the draft makes the desired action, deadline, owner, or decision clear.
6. Flag facts, legal claims, numbers, names, dates, or promises that the user should verify.

## Editing Priorities

Prioritize in this order:

1. Accuracy and intent
2. Clarity and reader comprehension
3. Professional tone
4. Concision
5. Grammar and mechanics
6. Style polish

Do not make the writing sound generic. Keep distinctive phrasing when it helps credibility, warmth, or authority.

## Output Format

When the user asks to proofread, enhance, polish, finalize, or make writing ready to send:

```markdown
## Polished Draft
[Provide the revised version ready to use.]

## Notes
- [Briefly explain only the most important changes, risks, or assumptions.]
```

If the user asks for minimal changes, preserve sentence order and wording as much as possible. If they ask for a stronger rewrite, restructure freely while preserving intent.

## Quality Check

Before finalizing, confirm the draft:

- Leads with the point or desired action.
- Uses concise sentences and paragraphs.
- Avoids vague phrases such as "just checking in," "per my last email," "circle back," and "at your earliest convenience" unless they fit the context.
- Makes next steps explicit when action is needed.
- Sounds like a competent US business professional, not an over-polished template.