# Proofread Content > Proofread and lightly edit sorg Markdown content before publication. Use when the user passes a content file path such as content/nanoglyphs/052-adrift.md, content/articles/*.md, content/fragments/*.md, or another prose-heavy Markdown file and asks for a proofread, spelling/grammar check, minor editorial pass, repeated-word scan, or publication readiness review. Use when this capability is needed. - Skill: `tomevault-io/proofread-content` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/proofread-content` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/proofread-content/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/proofread-content --- # Proofread Content ## Workflow 1. Read the requested file before editing. 2. Preserve frontmatter, Markdown links, image tags, headings, anchors, block quotes, and HTML unless they contain a clear typo. 3. Make direct edits only for clear spelling, grammar, punctuation, duplicated-word, or typo fixes. 4. Keep the author's voice, cadence, humor, contractions, and first-person perspective intact. 5. Do not rewrite paragraphs, change claims, normalize style, or fact-check unless the user explicitly asks. 6. For subjective wording improvements, report suggestions instead of applying them. ## Repeated Words Run the bundled scanner against the file: ```sh python3 .codex/skills/proofread-content/scripts/repetition_scan.py ``` Use the scanner output as leads, not as automatic edits. Ignore repeated terms when repetition is intentional, structural, technical, quoted, part of a name/title, or separated by enough context that it reads naturally. For awkward clusters, suggest specific alternatives that fit the local sentence. Prefer small substitutions over sentence rewrites. ## Proofreading Pass Check the body prose for: - misspellings and homophones - subject/verb agreement - missing or doubled words - punctuation mistakes - malformed Markdown links - obvious typographic inconsistencies - awkward repeated words in nearby sentences Treat TOML frontmatter as metadata. Fix obvious typos in human-facing values like `title`, `hook`, and `image_alt`, but do not reformat metadata or change dates, paths, slugs, or image URLs. ## Output When edits are made, summarize them briefly and mention the file path. Include any remaining optional editorial suggestions separately. When no direct edits are safe, say so and provide a concise list of suggested changes with enough context to find them. Do not paste the full article back to the user. --- > Source: [brandur/sorg](https://github.com/brandur/sorg) — distributed by [TomeVault](https://tomevault.io).