AI Draft Polish Card
Purpose
Use this skill when a user has a rough email, post, proposal, note, announcement, reply, or short document that needs to become clearer quickly. The output is a visible polish card: original intent, audience, must-keep points, final draft, tone notes, cut list, and unsupported-claim flags.
This is a prompt-only writing workflow. It improves clarity, structure, tone, and concision, but it does not invent facts, credentials, results, quotes, dates, prices, statistics, endorsements, citations, or promises.
Use This Skill When
Use this skill when the user asks to:
- Polish a rough email before sending it.
- Rewrite a post, proposal, pitch, bio, update, reply, or announcement.
- Make writing clearer, shorter, warmer, firmer, more professional, or easier to scan.
- Keep specific facts or phrases intact while improving the rest.
- See what changed, what was cut, and what still needs verification.
Do not use it to create deceptive claims, fake testimonials, impersonation, hidden persuasion, unsupported guarantees, or facts the user did not provide.
Best Inputs
Ask for the minimum needed, then proceed with placeholders if details are missing.
- Rough draft text.
- Audience or recipient.
- Goal of the message.
- Desired tone, such as warm, direct, concise, executive, friendly, firm, apologetic, promotional, or neutral.
- Must-keep points, phrases, dates, names, numbers, constraints, or legal/compliance wording.
- Things to avoid, such as sounding salesy, defensive, too casual, too long, or too apologetic.
- Length target or channel, such as email, LinkedIn post, internal update, proposal section, SMS, or landing page copy.
Do not ask for secrets, passwords, private keys, one-time codes, full financial details, or confidential material that is not needed for the rewrite.
Workflow
- Capture the draft. Read the rough text and identify the likely purpose, current strengths, and confusing sections.
- Confirm audience and goal. State the recipient, desired action, channel, and tone. If missing, make a conservative assumption and label it.
- Protect must-keep facts. Extract names, dates, numbers, commitments, constraints, promises, claims, and required phrases before rewriting.
- Flag unsupported claims. Mark claims that need a source, proof, permission, or user confirmation. Do not strengthen or invent them.
- Polish the draft. Improve structure, opening, flow, clarity, emphasis, sentence length, transitions, and ending while preserving meaning.
- Create a cut list. List removed or compressed material and why it was cut.
- Review the final card. Provide the final draft plus tone notes, fact-preservation notes, unresolved questions, and optional alternate subject lines or hooks when useful.
Output Format
Return the polish card in this order:
- Draft Snapshot
| Field | Detail |
|---|---|
| Audience | |
| Goal | |
| Channel | |
| Desired tone | |
| Must-keep points | |
| Assumptions made |
- Final Draft
A copy-ready polished version. Preserve all user-provided facts unless they are clearly marked as uncertain.
- Tone Notes
A short explanation of how the tone was adjusted and why.
- Before and After Highlights
| Area | Before | After | Reason |
|---|---|---|---|
| Opening | |||
| Structure | |||
| Clarity | |||
| Call to action |
- Cut List
| Removed or compressed text | Reason | Risk if needed |
|---|---|---|
- Unsupported or Unclear Claims
| Claim or detail | Why it needs confirmation | Safe wording used |
|---|---|---|
- Optional Variants
Include only if helpful: subject lines, shorter version, warmer version, firmer version, or social-post hook.
Style Rules
- Preserve the user's intended meaning.
- Prefer clear verbs, short paragraphs, and a concrete call to action.
- Keep the user's voice when possible; do not over-polish into generic corporate language.
- Use brackets for missing details, such as [DATE], [NAME], or [LINK].
- If the original draft is emotionally charged, keep the response calm and fair without erasing the user's point.
- If the user asks for a very short version, prioritize message purpose and required facts over flourish.
Safety Boundary
- Do not invent details, statistics, quotes, awards, results, credentials, references, client names, product capabilities, legal claims, medical claims, financial claims, or availability.
- Do not hide uncertainty. Flag unsupported claims and offer safe, qualified wording.
- Do not fabricate personal experiences, testimonials, endorsements, receipts, screenshots, citations, or attachments.
- Do not write impersonation, phishing, fraud, harassment, extortion, or manipulative pressure messages.
- Do not advise on regulated legal, medical, tax, investment, immigration, or employment decisions beyond plain-language drafting support.
- Do not ask the user to paste unnecessary secrets or credentials.
Example Prompts
- "Polish this email to my manager. Keep the deadline and budget details exactly as written."
- "Make this proposal intro clearer and less salesy."
- "Turn this rough post into a concise LinkedIn update."
- "Rewrite this reply so it sounds firm but not rude."
- "Polish this announcement and show me what you cut."
Install-First Success Path
Input: User pastes a rough email draft: "hey team just wanted to let everyone know the Q3 numbers are in and we did pretty good overall, revenue is up 12% which is cool, also we need to talk about the Seattle project timeline shift..."
Steps:
1. Identify the draft type: internal team update
2. Assess tone, clarity, and structure issues: too casual, run-on, mixed topics
3. Polish: restructure into clear sections (Q3 results, Seattle timeline), tighten language, keep all factual details intact
4. Present the polished version with a changelog: what was cut, what was reworded, what was restructured
5. Offer tone variants if the user wants more/less formal
Output: A polished draft with a transparent edit log. The user sees exactly what changed, can accept or revert any edit, and sends the improved version with confidence.
