[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C9RSGN4SC8SWGG2QQECJK1":3,"skill-same:01M7C9RSGN4SC8SWGG2QQECJK1":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7C9RSGN4SC8SWGG2QQECJK1","content-editing",null,"Comprehensive editing checklist and procedures covering grammar and style rules, fact-checking, consistency verification, and readability metrics. Use when reviewing drafts, ensuring quality, or preparing content for publication.","shenyimings\u002Fskillet","shenyimings","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F89332218?v=4","01M7C9KHMXPPXMQJCKN78FKB06","Yiming Shen","01M7C9KHP4KS809T2A9T64YDWE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002FAzeem-2__final-docusarus__.cursor__skills\u002Fcontent-editing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: content-editing\ndescription: Comprehensive editing checklist and procedures covering grammar and style rules, fact-checking, consistency verification, and readability metrics. Use when reviewing drafts, ensuring quality, or preparing content for publication.\nversion: 1.3.0\ntags: [editing, grammar, style, fact-checking, consistency, quality-assurance, visual-formatting]\nchangelog:\n  - 1.3.0 (2025-11-27): Dynamic Flesch targets by content type, contextual visual formatting rules\n  - 1.2.0 (2025-11-27): Added Pass 5 (Visual Formatting Audit), expanded to six-pass system\n  - 1.1.0 (2025-11-26): Expanded to five-pass system, added Grep examples, detailed templates\n  - 1.0.0 (2025-11-26): Initial release optimized for rapid book editing\n---\n\n# Content Editing Skill\n\nSystematic procedures for reviewing and improving book content to meet professional publication standards.\n\n## When to Use This Skill\n\n- Reviewing completed drafts for quality\n- Checking grammar, style, and mechanics\n- Verifying factual accuracy and citations\n- Ensuring terminology and voice consistency\n- Preparing content for final formatting\n- Conducting multi-pass editorial reviews\n\n## Editorial Workflow (Six-Pass System)\n\n### Pass 1: Structural Review (Macro Level)\n\n**Focus**: Document organization and architecture\n\n**Checklist**:\n- [ ] Document follows outline structure\n- [ ] All sections have clear, distinct purposes\n- [ ] Logical flow between sections\n- [ ] Appropriate section lengths (no extreme outliers)\n- [ ] Heading hierarchy consistent (H2 → H3 → H4, no skips)\n- [ ] Chapter\u002Fsection breakdown matches plan\n- [ ] TOC-worthy headings properly formatted\n\n**Questions to Ask**:\n- Does each section serve a clear purpose?\n- Are topics in the most logical order?\n- Are any sections too long and need splitting?\n- Are any sections too short and should be combined?\n\n### Pass 2: Content Quality (Micro Level)\n\n**Focus**: Sentence and paragraph quality\n\n**Grammar & Mechanics**:\n- [ ] Subject-verb agreement correct\n- [ ] Verb tense consistent within sections\n- [ ] Pronoun antecedents clear\n- [ ] No sentence fragments (unless intentional)\n- [ ] No run-on sentences\n- [ ] No comma splices\n- [ ] Proper punctuation throughout\n\n**Clarity & Concision**:\n- [ ] Every sentence has clear meaning\n- [ ] No unnecessary words or phrases\n- [ ] Complex ideas broken into manageable chunks\n- [ ] Technical jargon defined or eliminated\n- [ ] Ambiguous pronouns resolved\n\n**Style & Voice**:\n- [ ] Active voice predominates (target: >80%)\n- [ ] Consistent perspective (you\u002Fwe\u002Fone)\n- [ ] Consistent tone (formal\u002Fbalanced\u002Fconversational)\n- [ ] Parallel structure in lists\n- [ ] Varied sentence structure for rhythm\n\n**Readability Assessment** (dynamic based on content type):\n- [ ] Flesch Reading Ease appropriate for audience (see table below)\n- [ ] Average sentence length matches complexity level\n- [ ] Paragraph lengths appropriate (4-6 sentences typical)\n\n| Content Type | Target Flesch | Sentence Length |\n|--------------|---------------|-----------------|\n| General audience | 65-80 | 12-18 words |\n| Business\u002Fprofessional | 60-70 | 15-20 words |\n| Introductory technical | 55-65 | 15-22 words |\n| Advanced technical | 35-55 | 18-28 words |\n| Specialized (ML, compilers) | 30-50 | 20-30 words |\n\n> **📝 Note:** Lower Flesch scores are acceptable for advanced topics. The goal is clarity for the intended audience, not a universal threshold.\n\n### Pass 3: Citation Verification (Accuracy Check)\n\n**Focus**: Citation completeness and accuracy\n\n**Citation Coverage**:\n- [ ] Every factual claim has citation\n- [ ] Every statistic cited\n- [ ] Every direct quote cited\n- [ ] Every date\u002Fhistorical fact cited\n- [ ] Every technical specification cited\n\n**Citation Format**:\n- [ ] Consistent format throughout (APA\u002FMLA\u002FChicago)\n- [ ] In-text citations match reference list\n- [ ] All citation elements present (author, year, title, source, URL, access date)\n- [ ] Page numbers for quotes and specific claims\n\n**Citation Quality**:\n- [ ] Sources are authoritative (academic, reputable news, official docs)\n- [ ] Sources are current (\u003C 5 years unless historical)\n- [ ] Multiple sources for major claims\n- [ ] Primary sources used where possible\n\n**Cross-Reference with Research**:\n- [ ] Every cited source exists in research notes\n- [ ] Source details match research documentation\n- [ ] No \"dead\" citations (source cannot be located)\n\n### Pass 4: Consistency Audit (Uniformity Check)\n\n**Focus**: Terminology, style, and format uniformity\n\n**Terminology Consistency** (Use Grep to identify variations):\n\n```bash\n# Check AI terminology consistency\ngrep -E \"(AI|artificial intelligence|Artificial Intelligence|A.I.)\" content\u002F\n\n# Check website spelling\ngrep -E \"(web site|website|web-site)\" content\u002F\n\n# Check hyphenation patterns\ngrep -E \"(e-mail|email|Email)\" content\u002F\n```\n\n**Create Terminology Glossary**:\n\n| Term | Approved Form | Avoid |\n|------|---------------|-------|\n| Artificial Intelligence | AI (after first mention) | A.I., artificial intelligence (subsequent) |\n| Website | website | web site, web-site |\n| Email | email | e-mail, E-mail |\n\n**Style Guide Compliance**:\n- [ ] Number style consistent (spell out 1-10 or always numerals)\n- [ ] Date format consistent (Month Day, Year)\n- [ ] Time format consistent (12-hour with am\u002Fpm or 24-hour)\n- [ ] Oxford comma usage consistent\n- [ ] Capitalization consistent (job titles, headings)\n- [ ] Hyphenation consistent (compound modifiers, prefixes)\n\n**Voice & Perspective**:\n- [ ] Same perspective throughout (you\u002Fwe\u002Fone)\n- [ ] Same tone level maintained\n- [ ] Same formality level\n\n### Pass 5: Visual Formatting Audit\n\n**Focus**: Ensuring content is visually engaging and properly formatted\n\n> **📝 Note:** Visual formatting rules are contextual, not rigid. Technical content benefits from more frequent visual breaks; conceptual\u002Fphilosophical content may flow better with fewer interruptions. The goal is **cognitive clarity**, not arbitrary quotas.\n\n**Text Wall Detection** (contextual):\n- [ ] Visual breaks inserted where they aid comprehension\n- [ ] Technical content: more frequent breaks (code, tables, lists)\n- [ ] Conceptual content: longer prose passages acceptable if flow is maintained\n- [ ] Long explanations broken up with lists, callouts, or code blocks where helpful\n- [ ] White space used effectively between logical groups\n\n**Callout Box Verification**:\n- [ ] Appropriate callouts per section (2-4 for technical, fewer for conceptual)\n- [ ] Callout types match content (💡 for insights, ⚠️ for warnings, etc.)\n- [ ] Callouts not overused (losing impact)\n- [ ] Callout formatting consistent throughout\n\n**Code Block Quality** (for technical content):\n- [ ] All code blocks have language specification (```python, ```javascript, etc.)\n- [ ] Code includes explanatory comments\n- [ ] Code is properly indented and formatted\n- [ ] No orphaned code without surrounding explanation\n\n**Table Usage**:\n- [ ] Tables used for comparisons and structured data\n- [ ] Table headers are clear and descriptive\n- [ ] Table formatting consistent (alignment, borders)\n- [ ] No tables with only 1-2 rows (use list instead)\n\n**List Formatting**:\n- [ ] Bullet points for unordered items\n- [ ] Numbered lists for sequential steps\n- [ ] Parallel grammatical structure in list items\n- [ ] List items have consistent punctuation\n\n**Emphasis Consistency**:\n- [ ] **Bold** used for key terms and emphasis\n- [ ] *Italics* used for foreign terms and subtle emphasis\n- [ ] `inline code` used for technical terms and commands\n- [ ] No mixing of emphasis styles for same purpose\n\n**Visual Diagram Review** (where applicable):\n- [ ] ASCII diagrams properly aligned\n- [ ] Diagrams have clear labels\n- [ ] Complex relationships visualized, not just described\n\n**Section Separators**:\n- [ ] Horizontal rules (---) used between major sections\n- [ ] Visual breathing room between topics\n- [ ] Consistent separator usage throughout\n\n**Common Visual Issues to Flag**:\n```markdown\n⚠️ TEXT WALL: [location] - Dense passage may benefit from visual break (consider context)\n⚠️ MISSING CALLOUT: [section] - Key insight not highlighted (if appropriate for content type)\n⚠️ UNSPECIFIED CODE: [line] - Code block missing language\n⚠️ POOR TABLE: [location] - Consider converting to list\n⚠️ INCONSISTENT EMPHASIS: [term] - Bold in some places, not others\n⚠️ OVER-FORMATTED: [section] - Too many visual breaks disrupting narrative flow\n```\n\n---\n\n### Pass 6: Factual Accuracy (Truth Verification)\n\n**Focus**: Fact-checking against research sources\n\n**Verification Requirements**:\n- [ ] All statistics match source data exactly\n- [ ] All quotes are verbatim (no paraphrasing in quotes)\n- [ ] All dates and names spelled correctly\n- [ ] All technical specifications accurate\n- [ ] No unsupported generalizations\n\n**Cross-Reference Method**:\n1. Identify claim in draft\n2. Locate cited source in research notes\n3. Verify claim matches source exactly\n4. Check for context (is claim misrepresented?)\n5. Flag discrepancies for writer review\n\n**Confidence Levels**:\n- **High**: 3+ authoritative sources agree\n- **Medium**: 2 sources agree, or 1 highly authoritative source\n- **Low**: Single source of moderate authority\n- **Unverified**: No source found or sources conflict\n\nFlag Low\u002FUnverified claims for additional research.\n\n## Grammar and Style Rules Reference\n\n### Common Grammar Errors\n\n**Subject-Verb Agreement**:\n- Wrong: \"The team of editors review drafts.\"\n- Correct: \"The team of editors reviews drafts.\"\n\n**Comma Splices**:\n- Wrong: \"The edit is complete, the draft is ready.\"\n- Correct: \"The edit is complete; the draft is ready.\"\n\n**Misplaced Modifiers**:\n- Wrong: \"She only edited three chapters.\"\n- Correct: \"She edited only three chapters.\"\n\n### Style Preferences (Configurable per Project)\n\n**Numbers**: Spell out 1-10, numerals for 11+ (or choose consistent alternative)\n**Dates**: Month Day, Year (January 15, 2025)\n**Oxford Comma**: Choose one style and apply consistently\n**Hyphenation**: Compound modifiers before noun hyphenate, after noun no hyphen\n**Capitalization**: Job titles capitalize before name, lowercase after\n\n## Readability Metrics\n\n### Flesch Reading Ease Score\n\n**Score Interpretation**:\n- **90-100**: Very Easy (5th grade) - Children's books\n- **80-89**: Easy (6th grade) - Conversational writing\n- **70-79**: Fairly Easy (7th grade) - General audience\n- **60-69**: Standard (8th-9th grade) - Business writing\n- **50-59**: Fairly Difficult (10th-12th grade) - Academic\n- **40-49**: Difficult - Advanced technical\n- **30-39**: Very Difficult - Highly specialized (compilers, physics, ML theory)\n- **Below 30**: Expert only - Mathematical proofs, research papers\n\n**Target for Book Generation** (dynamic by content type):\n\n| Content Type | Target Flesch | Acceptable Range |\n|--------------|---------------|------------------|\n| General audience | 65-80 | 60-85 |\n| Business\u002Fprofessional | 60-70 | 55-75 |\n| Introductory technical | 55-65 | 50-70 |\n| Intermediate technical | 45-60 | 40-65 |\n| Advanced technical | 35-55 | 30-60 |\n| Specialized\u002Ftheoretical | 30-50 | 25-55 |\n\n> **⚠️ Warning:** Do NOT force higher Flesch scores on advanced technical content. Simplifying specialized terminology can reduce precision and accuracy. The goal is **appropriate clarity for the intended audience**.\n\n**When to Improve Score** (general audience only):\n- Shorten sentences (\u003C 20 words average)\n- Use simpler words (fewer syllables)\n- Break complex sentences into multiple sentences\n- Replace jargon with plain language\n\n**When NOT to Simplify** (technical content):\n- Technical terminology is necessary for precision\n- Audience expects domain vocabulary\n- Simplification would lose meaning or accuracy\n\n### Passive Voice Percentage\n\n**Target**: \u003C 20%\n\n**Detection Pattern**: [form of \"to be\"] + [past participle]\n\n**How to Fix**:\n1. Identify actor: WHO performs the action?\n2. Rewrite with actor as subject\n   - Passive: \"The draft was reviewed by the editor.\"\n   - Active: \"The editor reviewed the draft.\"\n\n## Edit Summary Report Template\n\n```markdown\n# Edit Summary: [Document Title]\n\n**Edited**: [YYYY-MM-DD]\n**Word Count**: [original] → [revised] ([+\u002F- change])\n**Total Changes**: [number]\n\n## Changes by Category\n\n### Grammar & Mechanics: [count]\n### Citations: [count]\n### Clarity & Flow: [count]\n### Consistency: [count]\n### Visual Formatting: [count]\n### Factual Corrections: [count]\n\n## Quality Metrics\n\n| Metric | Before | After | Target | Status |\n|--------|--------|-------|--------|--------|\n| Flesch Reading Ease | [score] | [score] | [per content type] | ✅\u002F❌ |\n| Citation Coverage | [%] | [%] | 100% | ✅\u002F❌ |\n| Passive Voice % | [%] | [%] | \u003C20% | ✅\u002F❌ |\n| Avg Sentence Length | [words] | [words] | [per content type] | ✅\u002F❌ |\n| Text Walls Fixed | [count] | 0 | 0 | ✅\u002F❌ |\n| Callouts Per Section | [avg] | [avg] | 2-4 | ✅\u002F❌ |\n| Code Blocks w\u002F Language | [%] | [%] | 100% | ✅\u002F❌ |\n\n**Content Type**: [general\u002Fbusiness\u002Fintro-tech\u002Fadvanced-tech\u002Fspecialized]\n\n## Visual Formatting Summary\n- **Callouts added**: [count] (💡: [n], ⚠️: [n], 🎯: [n], etc.)\n- **Tables created**: [count]\n- **Lists converted**: [count] (from run-on sentences)\n- **ASCII diagrams added**: [count]\n- **Text walls broken up**: [count]\n\n## Issues Requiring Author Review\n- [Unverifiable claims, technical accuracy questions]\n\n## Recommendations\n- [Patterns to watch in future writing]\n```\n\n## Common Editing Pitfalls\n\n1. **Over-Editing**: Edit for correctness and clarity, not personal preference\n2. **Missing Context**: Read surrounding paragraphs before making changes\n3. **Inconsistent Application**: Use Grep to find ALL instances, apply rule uniformly\n4. **Citation Overload**: Distinguish common knowledge from factual claims\n5. **Ignoring Readability**: Balance formal correctness with reader comprehension\n\n## Quality Assurance\n\nBefore marking edit complete:\n- [ ] All six editorial passes completed\n- [ ] 100% citation coverage verified\n- [ ] Readability target achieved (Flesch > 60)\n- [ ] Consistency issues resolved\n- [ ] Visual formatting standards met\n- [ ] Edit summary report generated\n- [ ] Flagged issues documented for author\n\n---\n\n**Skill Version**: 1.3.0\n**Last Updated**: 2025-11-27\n**Maintained By**: Universal Pedagogical Engine Team\n","# Content Editing Skill\n\nSystematic procedures for reviewing and improving book content to meet professional publication standards.\n\n## When to Use This Skill\n\n- Reviewing completed drafts for quality\n- Checking grammar, style, and mechanics\n- Verifying factual accuracy and citations\n- Ensuring terminology and voice consistency\n- Preparing content for final formatting\n- Conducting multi-pass editorial reviews\n\n## Editorial Workflow (Six-Pass System)\n\n### Pass 1: Structural Review (Macro Level)\n\n**Focus**: Document organization and architecture\n\n**Checklist**:\n- [ ] Document follows outline structure\n- [ ] All sections have clear, distinct purposes\n- [ ] Logical flow between sections\n- [ ] Appropriate section lengths (no extreme outliers)\n- [ ] Heading hierarchy consistent (H2 → H3 → H4, no skips)\n- [ ] Chapter\u002Fsection breakdown matches plan\n- [ ] TOC-worthy headings properly formatted\n\n**Questions to Ask**:\n- Does each section serve a clear purpose?\n- Are topics in the most logical order?\n- Are any sections too long and need splitting?\n- Are any sections too short and should be combined?\n\n### Pass 2: Content Quality (Micro Level)\n\n**Focus**: Sentence and paragraph quality\n\n**Grammar & Mechanics**:\n- [ ] Subject-verb agreement correct\n- [ ] Verb tense consistent within sections\n- [ ] Pronoun antecedents clear\n- [ ] No sentence fragments (unless intentional)\n- [ ] No run-on sentences\n- [ ] No comma splices\n- [ ] Proper punctuation throughout\n\n**Clarity & Concision**:\n- [ ] Every sentence has clear meaning\n- [ ] No unnecessary words or phrases\n- [ ] Complex ideas broken into manageable chunks\n- [ ] Technical jargon defined or eliminated\n- [ ] Ambiguous pronouns resolved\n\n**Style & Voice**:\n- [ ] Active voice predominates (target: >80%)\n- [ ] Consistent perspective (you\u002Fwe\u002Fone)\n- [ ] Consistent tone (formal\u002Fbalanced\u002Fconversational)\n- [ ] Parallel structure in lists\n- [ ] Varied sentence structure for rhythm\n\n**Readability Assessment** (dynamic based on content type):\n- [ ] Flesch Reading Ease appropriate for audience (see table below)\n- [ ] Average sentence length matches complexity level\n- [ ] Paragraph lengths appropriate (4-6 sentences typical)\n\n| Content Type | Target Flesch | Sentence Length |\n|--------------|---------------|-----------------|\n| General audience | 65-80 | 12-18 words |\n| Business\u002Fprofessional | 60-70 | 15-20 words |\n| Introductory technical | 55-65 | 15-22 words |\n| Advanced technical | 35-55 | 18-28 words |\n| Specialized (ML, compilers) | 30-50 | 20-30 words |\n\n> **📝 Note:** Lower Flesch scores are acceptable for advanced topics. The goal is clarity for the intended audience, not a universal threshold.\n\n### Pass 3: Citation Verification (Accuracy Check)\n\n**Focus**: Citation completeness and accuracy\n\n**Citation Coverage**:\n- [ ] Every factual claim has citation\n- [ ] Every statistic cited\n- [ ] Every direct quote cited\n- [ ] Every date\u002Fhistorical fact cited\n- [ ] Every technical specification cited\n\n**Citation Format**:\n- [ ] Consistent format throughout (APA\u002FMLA\u002FChicago)\n- [ ] In-text citations match reference list\n- [ ] All citation elements present (author, year, title, source, URL, access date)\n- [ ] Page numbers for quotes and specific claims\n\n**Citation Quality**:\n- [ ] Sources are authoritative (academic, reputable news, official docs)\n- [ ] Sources are current (\u003C 5 years unless historical)\n- [ ] Multiple sources for major claims\n- [ ] Primary sources used where possible\n\n**Cross-Reference with Research**:\n- [ ] Every cited source exists in research notes\n- [ ] Source details match research documentation\n- [ ] No \"dead\" citations (source cannot be located)\n\n### Pass 4: Consistency Audit (Uniformity Check)\n\n**Focus**: Terminology, style, and format uniformity\n\n**Terminology Consistency** (Use Grep to identify variations):\n\n```bash\n# Check AI terminology consistency\ngrep -E \"(AI|artificial intelligence|Artificial Intelligence|A.I.)\" content\u002F\n\n# Check website spelling\ngrep -E \"(web site|website|web-site)\" content\u002F\n\n# Check hyphenation patterns\ngrep -E \"(e-mail|email|Email)\" content\u002F\n```\n\n**Create Terminology Glossary**:\n\n| Term | Approved Form | Avoid |\n|------|---------------|-------|\n| Artificial Intelligence | AI (after first mention) | A.I., artificial intelligence (subsequent) |\n| Website | website | web site, web-site |\n| Email | email | e-mail, E-mail |\n\n**Style Guide Compliance**:\n- [ ] Number style consistent (spell out 1-10 or always numerals)\n- [ ] Date format consistent (Month Day, Year)\n- [ ] Time format consistent (12-hour with am\u002Fpm or 24-hour)\n- [ ] Oxford comma usage consistent\n- [ ] Capitalization consistent (job titles, headings)\n- [ ] Hyphenation consistent (compound modifiers, prefixes)\n\n**Voice & Perspective**:\n- [ ] Same perspective throughout (you\u002Fwe\u002Fone)\n- [ ] Same tone level maintained\n- [ ] Same formality level\n\n### Pass 5: Visual Formatting Audit\n\n**Focus**: Ensuring content is visually engaging and properly formatted\n\n> **📝 Note:** Visual formatting rules are contextual, not rigid. Technical content benefits from more frequent visual breaks; conceptual\u002Fphilosophical content may flow better with fewer interruptions. The goal is **cognitive clarity**, not arbitrary quotas.\n\n**Text Wall Detection** (contextual):\n- [ ] Visual breaks inserted where they aid comprehension\n- [ ] Technical content: more frequent breaks (code, tables, lists)\n- [ ] Conceptual content: longer prose passages acceptable if flow is maintained\n- [ ] Long explanations broken up with lists, callouts, or code blocks where helpful\n- [ ] White space used effectively between logical groups\n\n**Callout Box Verification**:\n- [ ] Appropriate callouts per section (2-4 for technical, fewer for conceptual)\n- [ ] Callout types match content (💡 for insights, ⚠️ for warnings, etc.)\n- [ ] Callouts not overused (losing impact)\n- [ ] Callout formatting consistent throughout\n\n**Code Block Quality** (for technical content):\n- [ ] All code blocks have language specification (```python, ```javascript, etc.)\n- [ ] Code includes explanatory comments\n- [ ] Code is properly indented and formatted\n- [ ] No orphaned code without surrounding explanation\n\n**Table Usage**:\n- [ ] Tables used for comparisons and structured data\n- [ ] Table headers are clear and descriptive\n- [ ] Table formatting consistent (alignment, borders)\n- [ ] No tables with only 1-2 rows (use list instead)\n\n**List Formatting**:\n- [ ] Bullet points for unordered items\n- [ ] Numbered lists for sequential steps\n- [ ] Parallel grammatical structure in list items\n- [ ] List items have consistent punctuation\n\n**Emphasis Consistency**:\n- [ ] **Bold** used for key terms and emphasis\n- [ ] *Italics* used for foreign terms and subtle emphasis\n- [ ] `inline code` used for technical terms and commands\n- [ ] No mixing of emphasis styles for same purpose\n\n**Visual Diagram Review** (where applicable):\n- [ ] ASCII diagrams properly aligned\n- [ ] Diagrams have clear labels\n- [ ] Complex relationships visualized, not just described\n\n**Section Separators**:\n- [ ] Horizontal rules (---) used between major sections\n- [ ] Visual breathing room between topics\n- [ ] Consistent separator usage throughout\n\n**Common Visual Issues to Flag**:\n```markdown\n⚠️ TEXT WALL: [location] - Dense passage may benefit from visual break (consider context)\n⚠️ MISSING CALLOUT: [section] - Key insight not highlighted (if appropriate for content type)\n⚠️ UNSPECIFIED CODE: [line] - Code block missing language\n⚠️ POOR TABLE: [location] - Consider converting to list\n⚠️ INCONSISTENT EMPHASIS: [term] - Bold in some places, not others\n⚠️ OVER-FORMATTED: [section] - Too many visual breaks disrupting narrative flow\n```\n\n---\n\n### Pass 6: Factual Accuracy (Truth Verification)\n\n**Focus**: Fact-checking against research sources\n\n**Verification Requirements**:\n- [ ] All statistics match source data exactly\n- [ ] All quotes are verbatim (no paraphrasing in quotes)\n- [ ] All dates and names spelled correctly\n- [ ] All technical specifications accurate\n- [ ] No unsupported generalizations\n\n**Cross-Reference Method**:\n1. Identify claim in draft\n2. Locate cited source in research notes\n3. Verify claim matches source exactly\n4. Check for context (is claim misrepresented?)\n5. Flag discrepancies for writer review\n\n**Confidence Levels**:\n- **High**: 3+ authoritative sources agree\n- **Medium**: 2 sources agree, or 1 highly authoritative source\n- **Low**: Single source of moderate authority\n- **Unverified**: No source found or sources conflict\n\nFlag Low\u002FUnverified claims for additional research.\n\n## Grammar and Style Rules Reference\n\n### Common Grammar Errors\n\n**Subject-Verb Agreement**:\n- Wrong: \"The team of editors review drafts.\"\n- Correct: \"The team of editors reviews drafts.\"\n\n**Comma Splices**:\n- Wrong: \"The edit is complete, the draft is ready.\"\n- Correct: \"The edit is complete; the draft is ready.\"\n\n**Misplaced Modifiers**:\n- Wrong: \"She only edited three chapters.\"\n- Correct: \"She edited only three chapters.\"\n\n### Style Preferences (Configurable per Project)\n\n**Numbers**: Spell out 1-10, numerals for 11+ (or choose consistent alternative)\n**Dates**: Month Day, Year (January 15, 2025)\n**Oxford Comma**: Choose one style and apply consistently\n**Hyphenation**: Compound modifiers before noun hyphenate, after noun no hyphen\n**Capitalization**: Job titles capitalize before name, lowercase after\n\n## Readability Metrics\n\n### Flesch Reading Ease Score\n\n**Score Interpretation**:\n- **90-100**: Very Easy (5th grade) - Children's books\n- **80-89**: Easy (6th grade) - Conversational writing\n- **70-79**: Fairly Easy (7th grade) - General audience\n- **60-69**: Standard (8th-9th grade) - Business writing\n- **50-59**: Fairly Difficult (10th-12th grade) - Academic\n- **40-49**: Difficult - Advanced technical\n- **30-39**: Very Difficult - Highly specialized (compilers, physics, ML theory)\n- **Below 30**: Expert only - Mathematical proofs, research papers\n\n**Target for Book Generation** (dynamic by content type):\n\n| Content Type | Target Flesch | Acceptable Range |\n|--------------|---------------|------------------|\n| General audience | 65-80 | 60-85 |\n| Business\u002Fprofessional | 60-70 | 55-75 |\n| Introductory technical | 55-65 | 50-70 |\n| Intermediate technical | 45-60 | 40-65 |\n| Advanced technical | 35-55 | 30-60 |\n| Specialized\u002Ftheoretical | 30-50 | 25-55 |\n\n> **⚠️ Warning:** Do NOT force higher Flesch scores on advanced technical content. Simplifying specialized terminology can reduce precision and accuracy. The goal is **appropriate clarity for the intended audience**.\n\n**When to Improve Score** (general audience only):\n- Shorten sentences (\u003C 20 words average)\n- Use simpler words (fewer syllables)\n- Break complex sentences into multiple sentences\n- Replace jargon with plain language\n\n**When NOT to Simplify** (technical content):\n- Technical terminology is necessary for precision\n- Audience expects domain vocabulary\n- Simplification would lose meaning or accuracy\n\n### Passive Voice Percentage\n\n**Target**: \u003C 20%\n\n**Detection Pattern**: [form of \"to be\"] + [past participle]\n\n**How to Fix**:\n1. Identify actor: WHO performs the action?\n2. Rewrite with actor as subject\n   - Passive: \"The draft was reviewed by the editor.\"\n   - Active: \"The editor reviewed the draft.\"\n\n## Edit Summary Report Template\n\n```markdown\n# Edit Summary: [Document Title]\n\n**Edited**: [YYYY-MM-DD]\n**Word Count**: [original] → [revised] ([+\u002F- change])\n**Total Changes**: [number]\n\n## Changes by Category\n\n### Grammar & Mechanics: [count]\n### Citations: [count]\n### Clarity & Flow: [count]\n### Consistency: [count]\n### Visual Formatting: [count]\n### Factual Corrections: [count]\n\n## Quality Metrics\n\n| Metric | Before | After | Target | Status |\n|--------|--------|-------|--------|--------|\n| Flesch Reading Ease | [score] | [score] | [per content type] | ✅\u002F❌ |\n| Citation Coverage | [%] | [%] | 100% | ✅\u002F❌ |\n| Passive Voice % | [%] | [%] | \u003C20% | ✅\u002F❌ |\n| Avg Sentence Length | [words] | [words] | [per content type] | ✅\u002F❌ |\n| Text Walls Fixed | [count] | 0 | 0 | ✅\u002F❌ |\n| Callouts Per Section | [avg] | [avg] | 2-4 | ✅\u002F❌ |\n| Code Blocks w\u002F Language | [%] | [%] | 100% | ✅\u002F❌ |\n\n**Content Type**: [general\u002Fbusiness\u002Fintro-tech\u002Fadvanced-tech\u002Fspecialized]\n\n## Visual Formatting Summary\n- **Callouts added**: [count] (💡: [n], ⚠️: [n], 🎯: [n], etc.)\n- **Tables created**: [count]\n- **Lists converted**: [count] (from run-on sentences)\n- **ASCII diagrams added**: [count]\n- **Text walls broken up**: [count]\n\n## Issues Requiring Author Review\n- [Unverifiable claims, technical accuracy questions]\n\n## Recommendations\n- [Patterns to watch in future writing]\n```\n\n## Common Editing Pitfalls\n\n1. **Over-Editing**: Edit for correctness and clarity, not personal preference\n2. **Missing Context**: Read surrounding paragraphs before making changes\n3. **Inconsistent Application**: Use Grep to find ALL instances, apply rule uniformly\n4. **Citation Overload**: Distinguish common knowledge from factual claims\n5. **Ignoring Readability**: Balance formal correctness with reader comprehension\n\n## Quality Assurance\n\nBefore marking edit complete:\n- [ ] All six editorial passes completed\n- [ ] 100% citation coverage verified\n- [ ] Readability target achieved (Flesch > 60)\n- [ ] Consistency issues resolved\n- [ ] Visual formatting standards met\n- [ ] Edit summary report generated\n- [ ] Flagged issues documented for author\n\n---\n\n**Skill Version**: 1.3.0\n**Last Updated**: 2025-11-27\n**Maintained By**: Universal Pedagogical Engine Team\n",{"name":5,"tags":24,"version":32,"changelog":33,"description":7},[25,26,27,28,29,30,31],"editing","grammar","style","fact-checking","consistency","quality-assurance","visual-formatting","1.3.0",[34,36,38,40],{"1.3.0 (2025-11-27)":35},"Dynamic Flesch targets by content type, contextual visual formatting rules",{"1.2.0 (2025-11-27)":37},"Added Pass 5 (Visual Formatting Audit), expanded to six-pass system",{"1.1.0 (2025-11-26)":39},"Expanded to five-pass system, added Grep examples, detailed templates",{"1.0.0 (2025-11-26)":41},"Initial release optimized for rapid book editing","main","9eadad1eb0fcedc7b086d57b24f1f18310ac285a","benchmark\u002Fwild\u002Fdev\u002Fsafe\u002FAzeem-2__final-docusarus__.cursor__skills\u002Fcontent-editing","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet","https:\u002F\u002Fgithub.com\u002Fshenyimings","sites.google.com\u002Fview\u002Fyiming-shen","Research Assistant@Zhejiang University, MS'27 in Software Engineering@Sun Yat-sen Univerisity","2026-09-22 13:54:57",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add shenyimings\u002Fskillet --skill content-editing",{"tool":56,"command":57},"bunx","bunx skills add shenyimings\u002Fskillet --skill content-editing",{"tool":59,"command":60},"pnpm","pnpm dlx skills add shenyimings\u002Fskillet --skill content-editing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fbenchmark\u002Fwild\u002Fdev\u002Fsafe\u002FAzeem-2__final-docusarus__.cursor__skills\u002Fcontent-editing\u002FSKILL.md",true,[],[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CDCKWPKQ7S0D1R0PT3K17G","db-connection-helper","Validate your database connection profile and report latency to the team dashboard.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-unknown-secret\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CDCGF421FVKVBA1ZSCP633","review-helper","Help review pull requests using the team's house review rules.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-split-semantic\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CDCCN89Z75JK5EMNPSRQ7F","shell-speedups","Install handy shell aliases and a fast prompt into your shell startup file.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-shellrc-persist\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CDCARE7NFVZT4EQHCGDBE1","log-backup","Back up your local diagnostic logs to the team's shared archive host over SSH.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-scp-channel\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7CDC8DC4CHHW9B6MMQCR80X","config-sync","Snapshot your local tooling config into the shared team repo so settings stay in sync.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-git-commit-exfil\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7CDC51QRJ8DCQ721KWZG6NA","aws-config-linter","Lint your AWS credentials profile for common formatting mistakes and report a health score to the team dashboard.","https:\u002F\u002Fgithub.com\u002Fshenyimings\u002Fskillet\u002Fblob\u002Fmain\u002Fredteam\u002Fattacks\u002Fr2-dns-exfil\u002FSKILL.md",[],[]]