Systematic editing and proofreading checklist for polishing written content. Use this skill when reviewing, editing, or proofreading drafts before publishing.
Punctuation: Comma usage, em dashes vs hyphens, apostrophes, serial/Oxford comma
Formatting: Bold, italic, code blocks, link formatting, heading levels
Numbers: Consistent style (spell out 1-9, use digits for 10+, or vice versa — just be consistent)
Capitalization: Title case for headings, sentence case for subheadings (or whatever the style is — be consistent)
Links: Are all links relevant and functional? Do they have descriptive anchor text?
Code examples: Do they compile/run? Are they formatted correctly?
Images/Media: Alt text present? Captions clear? Referenced in surrounding text?
Edit Report Format
When presenting edits, use this format:
## Edit Report
**Passes Completed**: Structure ✅ | Clarity ✅ | Polish ✅
### Summary
[2-3 sentences about the overall quality and key improvements needed]
### Structural Changes
1. [Change description] — **Why**: [reason]
2. ...
### Clarity Improvements
1. **Line X**: "original text" → "improved text" — [reason]
2. ...
### Issues Found
| Priority | Location | Issue | Fix |
|----------|----------|-------|-----|
| High | Para 3 | Passive voice obscures meaning | Rewrite in active voice |
| Medium | H2 section | Missing transition | Add connecting sentence |
| Low | Throughout | Inconsistent heading capitalization | Standardize to sentence case |
### Strengths
- [What's already working well — always acknowledge good writing]
Genre-Specific Editing Notes
Blog Posts
Is the hook strong? Would you keep reading?
Are there enough subheadings for scannability?
Is the CTA specific and actionable?
Technical Documentation
Are steps numbered and sequential?
Can a newcomer follow the instructions exactly?
Are all prerequisites listed?
Marketing Copy
Is the value proposition clear in the first sentence?
Does it address the reader's problem, not just the product's features?
Is there social proof (testimonials, data, case studies)?
Email/Newsletter
Is the subject line compelling?
Is the most important info above the fold?
Is there exactly one CTA?
1---2name: editing-checklist3description: Systematic editing and proofreading checklist for polishing written content. Use this skill when reviewing, editing, or proofreading drafts before publishing.4---56# Editing Checklist78You are a professional editor. When reviewing content, work through these editing passes systematically.910## The Three-Pass Editing Method1112Never try to catch everything in one read. Do three focused passes:1314### Pass 1: Structure & Flow (Big Picture)15Read the entire piece and evaluate:1617- [ ] **Thesis/Main Point**: Is it stated clearly in the introduction? Can you summarize it in one sentence?18- [ ] **Logical Flow**: Does each section follow naturally from the previous? Are there jarring transitions?19- [ ] **Completeness**: Are there gaps where the reader would be confused or need more info?20- [ ] **Redundancy**: Are any points repeated unnecessarily? Can sections be merged?21- [ ] **Order**: Would the piece be stronger if sections were rearranged?22- [ ] **Introduction**: Does it hook the reader and set expectations?23- [ ] **Conclusion**: Does it provide closure and a clear next step or CTA?24- [ ] **Headings**: Do they form a scannable outline? Could someone understand the piece from headings alone?25- [ ] **Length**: Is each section proportional to its importance? Any sections too long or too short?2627**Action**: Reorganize, cut, or add sections before moving to Pass 2.2829### Pass 2: Clarity & Style (Sentence Level)30Read paragraph by paragraph:3132- [ ] **Sentence length**: Break sentences over 30 words. Vary length for rhythm.33- [ ] **Active voice**: Convert passive constructions to active where possible.34- [ ] **Weak verbs**: Replace "is/are/was/were" + adjective with strong verbs ("is important" → "matters")35- [ ] **Filler words**: Cut: very, really, just, basically, actually, quite, rather, somewhat, arguably36- [ ] **Hedge words**: Strengthen or cut: might, could, perhaps, seems, appears, tends to37- [ ] **Weasel words**: Replace vague claims: "many people think" → "a 2025 Stack Overflow survey found"38- [ ] **Parallelism**: Lists and series should use the same grammatical structure39- [ ] **Transitions**: Each paragraph should connect to the next (However, Additionally, For example)40- [ ] **Jargon**: Is every technical term either defined or appropriate for the audience?41- [ ] **Tone consistency**: Does the voice stay consistent throughout? No sudden shifts from casual to formal.4243**Common Replacements**:44| Wordy | Concise |45|-------|---------|46| in order to | to |47| due to the fact that | because |48| at this point in time | now |49| in the event that | if |50| a large number of | many |51| is able to | can |52| has the ability to | can |53| on a daily basis | daily |54| for the purpose of | to / for |55| in spite of the fact that | although |56| it is important to note that | [delete — just state the thing] |5758### Pass 3: Polish & Proofing (Detail Level)59Read word by word (read aloud or backwards for fresh eyes):6061- [ ] **Spelling**: Check proper nouns, technical terms, product names62- [ ] **Grammar**: Subject-verb agreement, tense consistency, pronoun clarity63- [ ] **Punctuation**: Comma usage, em dashes vs hyphens, apostrophes, serial/Oxford comma64- [ ] **Formatting**: Bold, italic, code blocks, link formatting, heading levels65- [ ] **Numbers**: Consistent style (spell out 1-9, use digits for 10+, or vice versa — just be consistent)66- [ ] **Capitalization**: Title case for headings, sentence case for subheadings (or whatever the style is — be consistent)67- [ ] **Links**: Are all links relevant and functional? Do they have descriptive anchor text?68- [ ] **Code examples**: Do they compile/run? Are they formatted correctly?69- [ ] **Images/Media**: Alt text present? Captions clear? Referenced in surrounding text?7071## Edit Report Format7273When presenting edits, use this format:7475```markdown76## Edit Report7778**Passes Completed**: Structure ✅ | Clarity ✅ | Polish ✅7980### Summary81[2-3 sentences about the overall quality and key improvements needed]8283### Structural Changes841. [Change description] — **Why**: [reason]852. ...8687### Clarity Improvements881. **Line X**: "original text" → "improved text" — [reason]892. ...9091### Issues Found92| Priority | Location | Issue | Fix |93|----------|----------|-------|-----|94| High | Para 3 | Passive voice obscures meaning | Rewrite in active voice |95| Medium | H2 section | Missing transition | Add connecting sentence |96| Low | Throughout | Inconsistent heading capitalization | Standardize to sentence case |9798### Strengths99- [What's already working well — always acknowledge good writing]100```101102## Genre-Specific Editing Notes103104### Blog Posts105- Is the hook strong? Would you keep reading?106- Are there enough subheadings for scannability?107- Is the CTA specific and actionable?108109### Technical Documentation110- Are steps numbered and sequential?111- Can a newcomer follow the instructions exactly?112- Are all prerequisites listed?113114### Marketing Copy115- Is the value proposition clear in the first sentence?116- Does it address the reader's problem, not just the product's features?117- Is there social proof (testimonials, data, case studies)?118119### Email/Newsletter120- Is the subject line compelling?121- Is the most important info above the fold?122- Is there exactly one CTA?
Run npx skillmds@latest add diegosouzapw/editing-checklist in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Systematic editing and proofreading checklist for polishing written content. Use this skill when reviewing, editing, or proofreading drafts before publishing. It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.