doc-coauthoring

doc-coauthoring is a skill for Claude Code, Codex from ThinkInAIXYZ/deepchat. It costs 77 tokens per session (3,254 once invoked), scanned A, original, Apache-2.0.

A guided process for writing documentation, proposals, technical specifications, and decision records together. It gathers context, shapes the document, and checks whether it makes sense to a new reader.

In plain words
What is it for?
Use it to draft or improve structured documents such as PRDs, design documents, decision documents, and RFCs.
Why use it?
It reduces the risk of missing important context or producing a document that only its author understands. Reader testing helps find unclear sections before sharing the document.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions Claude Code.

Good fit Use it to draft or improve structured documents such as PRDs, design documents, decision documents, and RFCs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/thinkinaixyz/deepchat/doc-coauthoring
About the project

DeepChat is an open-source desktop client for AI agents that keeps user data local first and connects agents with services such as MCP, Skills, ACP, and messaging apps. It is for people who want to use and control AI assistants from a desktop application. The catalogue add-ons extend DeepChat’s agent workflows.

ThinkInAIXYZ/deepchat · 6,372 stars · on GitHub · deepchat.thinkinai.xyz

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ThinkInAIXYZ/deepchat --skill doc-coauthoring
Clone the repo
git clone --depth 1 https://github.com/ThinkInAIXYZ/deepchat

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for doc-coauthoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/thinkinaixyz/deepchat/doc-coauthoring/github.svg)](https://agentmods.dev/skills/thinkinaixyz/deepchat/doc-coauthoring)
Your own site
<a href="https://agentmods.dev/skills/thinkinaixyz/deepchat/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/thinkinaixyz/deepchat/doc-coauthoring/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for doc-coauthoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/thinkinaixyz/deepchat/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/thinkinaixyz/deepchat/doc-coauthoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,254 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.03254
Opus 5.5 $0.00031 $0.01302
Sonnet 5.5 $0.00015 $0.00651
Haiku 4.5 $0.00008 $0.00325

Measured 1mo ago against content hash 2e47d78846fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

doc-coauthoring scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

resources/skills/doc-coauthoring/SKILL.md · 376 lines

How it starts

The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Doc Co-Authoring Workflow

This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.

When to Offer This Workflow

Trigger conditions:

  • User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up"
  • User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC"
  • User seems to be starting a substantial writing task

Initial offer: Offer the user a structured workflow for co-authoring the document. Explain the three stages:

  1. Context Gathering: User provides all relevant context while Claude asks clarifying questions
  2. Refinement & Structure: Iteratively build each section through brainstorming and editing
  3. Reader Testing: Test the doc with a fresh Claude (no context) to catch blind spots before others read it

Explain that this approach helps ensure the doc works well when others read it (including when they paste it into Claude). Ask if they want to try this workflow or prefer to work freeform.

If user declines, work freeform. If user accepts, proceed to Stage 1.

Stage 1: Context Gathering

Goal: Close the gap between what the user knows and what Claude knows, enabling smart guidance later.

Initial Questions

Start by asking the user for meta-context about the document:

  1. What type of document is this? (e.g., technical spec, decision doc, proposal)
  2. Who's the primary audience?
  3. What's the desired impact when someone reads this?
  4. Is there a template or specific format to follow?
  5. Any other constraints or context to know?

Inform them they can answer in shorthand or dump information however works best for them.

If user provides a template or mentions a doc type:

  • Ask if they have a template document to share
  • If they provide a link to a shared document, use the appropriate integration to fetch it
  • If they provide a file, read it

Read the full file on GitHub · 376 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 376 lines · 77 tokens per session scan A 2e47d78846fa

Subscribe to this mod's changes

doc-coauthoring is a skill published in the GitHub repository ThinkInAIXYZ/deepchat (6,372 stars, last pushed today), licensed Apache-2.0. It adds 77 tokens to every session and 3,254 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

proactive-agent

Transform AI agents from task-followers into proactive partners that anticipate needs and continuously improve. Now with WAL Protocol, Working Buffer, Autonomous Crons, and battle-tested patterns. Part of the Hal Stack 🦞.

MerkyorLynn/Lynn · 46 tokens

novel-workshop

A workspace for writing novels with an AI assistant, covering outlines, characters, chapters, multiple viewpoints, editing, and book assembly. It treats the author’s files and instructions as the source of truth.

MerkyorLynn/Lynn · 90 tokens

agent-personality

3-layer personality system for AI agents: Yuan (base persona), Ishiki (private self-awareness), Public Ishiki (external behavior rules). Give your agent a consistent character, emotional depth, and safe guest interaction boundaries. Use when: (1) Want agent to have a consistent personality, (2) Agent needs different…

MerkyorLynn/Lynn · 114 tokens

image-lightbox

Click-to-zoom lightbox for chat images, screenshots, and generated visuals. Scroll-wheel zoom (0.5x–5x), drag-to-pan, pinch gesture on mobile, keyboard shortcuts. Zero dependencies — pure CSS + vanilla JS. Use when: (1) Chat contains images the user wants to inspect, (2) Browser screenshots need closer examination…

MerkyorLynn/Lynn · 108 tokens

memory-recall

Persistent cross-session memory system with fact extraction, semantic search, and compiled memory layers. Your agent remembers everything across sessions — user preferences, project context, past decisions, personal details. Use when: (1) User references something from a previous conversation, (2) Agent needs project…

MerkyorLynn/Lynn · 104 tokens

stock-analysis

Analyze stocks and cryptocurrencies using Yahoo Finance data. Supports portfolio management, watchlists with alerts, dividend analysis, 8-dimension stock scoring, viral trend detection (Hot Scanner), and rumor/early signal detection. Use for stock analysis, portfolio tracking, earnings reactions, crypto monitoring…

MerkyorLynn/Lynn · 70 tokens