--- title: "Anthropic Documentation Coauthoring: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/skills/anthropics-doc-coauthoring/ description: "Guides a human and agent through audience discovery, section-by-section drafting and a separate-reader review of a substantial document." --- # Anthropic Documentation Coauthoring: review, setup & limitations · Undominated.ai > Guides a human and agent through audience discovery, section-by-section drafting and a separate-reader review of a substantial document. [← Explore all skills](/skills/) RESEARCH AND DOCUMENTATION / Anthropic # Anthropic Documentation Coauthoring Guides a human and agent through audience discovery, section-by-section drafting and a separate-reader review of a substantial document. See setup guidance ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-21 Evidence 2 linked sources Publisher Anthropic Licence Not established Revision 34040c9c5685 Read what was—and wasn’t—checked ↓ “Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured” Anthropic · upstream description ↗ Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Starts with the audience, intended impact and missing context, then lets the author curate ideas before the agent drafts each section. - Adds a reader-question pass with a fresh conversation or subagent, giving unclear assumptions a concrete route back into revision. ### A good fit for - Coauthoring a proposal, RFC or technical specification - Checking whether a draft explains enough for a reader outside the authoring conversation ### Weigh up before choosing - Reader-model agreement is a spot check, not factual verification or a human usability study; the author still needs to verify facts and links. - The workflow assumes Claude-style artifact/edit tools and can be question-heavy. Connector access and fresh-reader sessions depend on the host. - No licence covering this particular folder was established: the repository only says many skills are Apache-licensed. This listing supplies no definition download. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - skills/doc-coauthoring/SKILL.md - README.md (installation, compatibility and licence sections) ### Our findings - The complete definition has opt-out/freeform and manual-reader fallbacks, and separates brainstorming from edits to the working document. - Reader testing receives the document and questions rather than the full authoring conversation; sharing a draft or chat appendix can still reveal sensitive context. - The create-file versus replace-text guidance needs adaptation to the host so section edits do not overwrite the whole document. ### Not established by this review - No document was coauthored or evaluated with readers. - Artifact editing, connectors and context isolation were not exercised. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Add a skill to your workflow. Upstream setup instructions ↗ - Install or load the upstream skill through the publisher guidance; this catalogue does not provide its source text. - Choose a local Markdown or host artifact workflow, and agree which documents or connectors the agent may use. ### Before you start - A Claude environment that can load the skill - A draft, audience description and any required source material; connected accounts only for sources you authorize ### Compatibility Claude Code · Claude.ai ### Documents; optional connected sources - Read supplied documents and authorized connected content - Create or edit the working document - Send the draft to a separate reader session if that review path is chosen ### Cost model The consuming Claude account or API and any connected services have their own terms; the skill folder does not establish a separate access price. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - Skill definition at reviewed revision ↗ Checked 2026-09-21 https://github.com/anthropics/skills/blob/34040c9c568585f6929bedeaad110ad08f079624/skills/doc-coauthoring/SKILL.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access - Publisher installation, compatibility and licensing guidance ↗ Checked 2026-09-21 https://github.com/anthropics/skills/blob/34040c9c568585f6929bedeaad110ad08f079624/README.md Supports: install, compatibility, access, license KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Microsoft Docs Research ↗ Finds current Microsoft documentation with task-specific queries and retrieves full pages when excerpts are insufficient.](/skills/microsoft-microsoft-docs/)[### Microsoft Wiki Researcher ↗ Traces architecture and data flow through source code to produce an explanation with file references, diagrams and stated uncertainties.](/skills/microsoft-wiki-researcher/)[### Superpowers Writing Plans ↗ Turns an agreed specification into file-specific implementation tasks with verification steps and a structured plan review.](/skills/obra-writing-plans/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)