Documents & Data · IN-DEPTH PROFILE

doc-coauthoring

Structured context gathering, section refinement, and reader testing for substantial documents.

View listed source ↗Installation guide ↓
Best for

Authors of technical specs, proposals, and decision documents

What you get

Gather context + Refine by section

Main limitation

The interview and section-by-section loop can be disproportionate for short or low-stakes documents.

First risk

Sensitive context collection. The workflow explicitly invites organizational context, incidents, linked documents, and team discussions. Minimize sensitive details and verify connector scope before sharing them.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-08-20

Pinned revision · 0a64e398

Open pinned commit ↗
SkillSignal profileEditorial metadata

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

What it does—and when it fits

Doc Co-Authoring is Anthropic's structured workflow for substantial documentation such as proposals, technical specifications, decision records, and RFCs. It moves through context gathering, section-by-section refinement, and reader testing so the final document can stand on its own outside the original conversation.

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project scope.claude/skills/doc-coauthoring/
Personal scope~/.claude/skills/doc-coauthoring/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)npx skills add anthropics/skills --skill doc-coauthoring --agent claude-code
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Gather context

Close knowledge gaps with targeted questions before drafting.

02

Refine by section

Brainstorm, select, draft, and surgically revise each section.

03

Test with a fresh reader

Use a context-free review to expose assumptions and unclear passages.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. Separates context gathering from drafting instead of mixing both activities.
  2. Treats reader comprehension as a testable outcome.

Limitations

  1. The interview and section-by-section loop can be disproportionate for short or low-stakes documents.
  2. Reader testing finds clarity gaps but does not prove domain facts are correct.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Claude Code

grill-with-docs

Grill With Docs combines deep design questioning with domain-model documentation.
Tradeoff to check
It assumes the repository has, or is willing to adopt, domain glossaries and decision records.
First risk
Documentation churn · Medium
Source state
Pinned · 885e2ca4
Open profile ↗
02

Same job family · native to Claude Code

lark-approval

Lark Approval routes approval instances and approval inbox work through lark-cli.
Tradeoff to check
Available actions depend on the approval definition, current state, identity, and tenant permissions.
First risk
Consequential approval action · High
Source state
Pinned · 755daa4d
Open profile ↗
03

Same job family · native to Claude Code

lark-attendance

Lark Attendance is a narrow, read-only lark-cli Skill for querying the current user's Feishu attendance check-in records.
Tradeoff to check
The Skill only documents the user's own check-in query; it is not a general attendance administration tool.
First risk
Employment data exposure · High
Source state
Pinned · 755daa4d
Open profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Authors of technical specs, proposals, and decision documents

→

Teams transferring complex context to new readers

BEFORE YOU USE IT

Risks to review before use

High

Sensitive context collection

The workflow explicitly invites organizational context, incidents, linked documents, and team discussions. Minimize sensitive details and verify connector scope before sharing them.

SECURITY

What the permission profile means

  • Treat linked documents and team channels as permission-controlled sources.
  • Remove secrets, personal data, and unnecessary organizational detail from drafts and test prompts.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream package contentSource-linked

TAGS

documentationco-authoringreader-testing

Original SkillSignal editorial profile grounded in the current SKILL.md and linked files at pinned Anthropic commit 0a64e398, checked 2026-08-20; not independently executed or security-certified.