proofread

star 13

Proofread publish-ready drafts for clarity, correctness, and links.

kevinslin By kevinslin schedule Updated 5/14/2026

name: proofread description: Proofread publish-ready drafts for clarity, correctness, and links. dependencies: []

Proofread

Overview

Review a draft that is about to be published and surface issues before it goes live. Focus on correctness, clarity, and publication readiness rather than voice changes unless the user asks for rewrites.

Default to critique, not rewriting. Report issues and the smallest correction that would fix them, but do not offer a tightened, revised, or rewritten version unless the user explicitly asks for one.

When the user asks to see the fixed document, provide a corrected draft that only auto-fixes spelling and grammar issues. Preserve the author's style, word choice, structure, sentence order, and emphasis. Do not tighten, polish, rewrite, or improve prose beyond the smallest grammar or spelling correction needed.

Review checklist

Check the draft for:

  1. Spelling mistakes and typos.
  2. Grammar mistakes.
  3. Repeated terms or repetitive phrasing such as "It was interesting that X, and it was interesting that Y."
  4. Logical errors or factual mistakes.
  5. Weak arguments that could be strengthened.
  6. Empty or placeholder links.

Working style

  1. Read the full draft once before marking issues.
  2. Quote the exact problematic text or point to the specific claim.
  3. Explain why it is a problem in one sentence.
  4. Prefer the smallest correction that fixes the issue.
  5. Mark unverified factual claims as verify when the draft makes a claim that may be wrong but cannot be confirmed from the provided context.
  6. Distinguish hard errors from optional improvements.
  7. Do not include a rewritten draft, tightened version, or polished alternative unless the user explicitly asks for a rewrite or fixed document.
  8. For a requested fixed document, only correct spelling and grammar; do not change style or word choice unless a grammar fix requires the smallest possible adjustment.

Output format

Use these sections when reporting findings:

  • Errors: spelling, grammar, broken links, and clear logical or factual problems.
  • Improvements: repetitive phrasing or weak arguments that could be stronger.
  • Clean: state this explicitly when no issues are found.
  • Corrected draft: include this only when the user asks to see the fixed document; apply only spelling and grammar fixes, preserving style and word choice.

Only provide corrected or rewritten copy when the user explicitly asks for it. Otherwise, keep the response to findings plus minimal inline fixes. When providing corrected copy, label it as grammar and spelling fixes rather than a rewrite.

Install via CLI
npx skills add https://github.com/kevinslin/skills --skill proofread
Repository Details
star Stars 13
call_split Forks 0
navigation Branch main
article Path SKILL.md
Occupations
More from Creator