← ClaudeAtlas

copy-longformlisted

Structured copyediting workflow for long-form text (ebooks, reports, whitepapers, long blog posts, decks, internal docs). Produces a tracked edit-list file as the source of truth, scrubs AI-writing tells per Wikipedia: Signs of AI writing, then walks the user page-by-page or chapter-by-chapter through every edit. Claude maintains a progress marker inside the edit-list file so a compacted or new session can resume from exactly where the previous one stopped. Use when the user wants to copyedit existing text rather than draft from scratch, asks for an "edit pass" / "copyedit" / "polish pass" / "anti-AI scrub" on a doc, or invokes /copy-longform.
risukisu/marketing-skills · ★ 4 · AI & Automation · score 77
Install: claude install-skill risukisu/marketing-skills
# Copy Longform A workflow skill for working through a defined document with structured feedback. Produces replacement copy, new paragraphs, reframed sections, and fresh prose where needed, always in context of an existing source document, a defined voice ruleset, and locked decisions. A single edit-list file doubles as the tracker, so progress survives across sessions. The skill assumes the structure already exists: a document, sections, defined slots where prose belongs, and feedback or direction guiding what changes. It does not start from raw notes or fuzzy ideas where the shape has not been decided. ## When this skill applies Trigger on any of: - "/copy-longform" or "/copyedit" - "Help me edit this [ebook/report/whitepaper/long post]" - "Run an edit pass on..." - "Copyedit this for me" - "Polish pass" - "Strip the AI tells from..." - "Anti-AI scrub on..." - User pastes a long doc and asks for systematic editing - User points at a file and asks to walk through it Do NOT trigger when there is no source document or no defined structure to work within. The skill needs a document, sections, or slots where the prose belongs. ## Step 1 — Intake (always ask, never skip) Even if context appears pre-loaded, ask. The user's own words shape the workflow. Ask in one batch: 1. **What's the source?** (file path, paste, or URL — load it before suggesting changes) 2. **What is it?** (ebook, report, whitepaper, blog post, deck, internal memo) — voice and stakes differ 3. **Audien