agentmods.dev

doc-coauthoring

doc-coauthoring is a skill for Claude Code from This-HW/claude-code-kit. It costs 26 tokens per session (1,415 once invoked), scanned A, original, MIT.

A guide for writing, reviewing, and updating technical documents such as API references, architecture notes, user guides, and README files. It uses the project files and existing specifications to build consistent documentation.

In plain words
What is it for?
Creating API documentation, architecture descriptions, user instructions, troubleshooting sections, FAQs, and standard project README files.
Why use it?
It reduces the effort of turning code and project structure into documentation that people can follow and maintain.

Skill for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Part of the claude-code-kit plugin — 20 skills, 4 hooks shipped together

not rated 4repo 1mo ago A scan 26 tokens original MIT

Good fit Creating API documentation, architecture descriptions, user instructions, troubleshooting sections, FAQs, and standard project README files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/this-hw/claude-code-kit/doc-coauthoring
View source ↗ This-HW/claude-code-kit this-hw.github.io
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 This-HW/claude-code-kit --skill doc-coauthoring
Clone the repo
git clone --depth 1 https://github.com/This-HW/claude-code-kit

Made for: Claude Code.

Or install claude-code-kit, the plugin that ships this one along with the rest of its 20 skills, 4 hooks.

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/this-hw/claude-code-kit/doc-coauthoring/github.svg)](https://agentmods.dev/skills/this-hw/claude-code-kit/doc-coauthoring)
Your own site
<a href="https://agentmods.dev/skills/this-hw/claude-code-kit/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/this-hw/claude-code-kit/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/this-hw/claude-code-kit/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/this-hw/claude-code-kit/doc-coauthoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,415 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.
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.00026 $0.01415
Opus 5.5 $0.00010 $0.00566
Sonnet 5.5 $0.00005 $0.00283
Haiku 4.5 $0.00003 $0.00142

Measured 1mo ago against content hash fd4a248a7c8a, 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.

plugins/common/skills/doc-coauthoring/SKILL.md · 265 lines

How it starts

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

Document Co-authoring

AI 기반 문서 작성 및 협업

문서의 작성, 리뷰, 업데이트를 자동화하여 일관성 있는 고품질 문서를 유지합니다.

사용법

신규 문서 작성

/doc-coauthoring "API 문서 작성" docs/api/README.md
/doc-coauthoring "사용자 가이드" docs/user-guide.md

기존 문서 업데이트

/doc-coauthoring "업데이트" docs/architecture/design.md
/doc-coauthoring "리뷰 및 개선" README.md

문서 유형별 워크플로우

1. API 문서

구조:

  • 개요 (Overview)
  • 인증 (Authentication)
  • 엔드포인트 (Endpoints)
    • 요청/응답 예시
    • 에러 코드
  • 사용 예시 (Examples)

생성 프로세스:

  1. 코드에서 API 정의 추출 (Glob + Read)
  2. OpenAPI/Swagger 스펙 읽기 (있으면)
  3. 표준 템플릿 적용
  4. 예시 코드 생성

2. 아키텍처 문서

구조:

  • 시스템 개요
  • 구성 요소 (Components)
  • 데이터 플로우
  • 기술 스택
  • 의사결정 기록 (ADR)

생성 프로세스:

  1. 프로젝트 구조 분석 (Glob)
  2. 주요 파일 읽기 (Read)
  3. 다이어그램 생성 (Mermaid)
  4. 의사결정 맥락 추가

3. 사용자 가이드

구조:

  • 시작하기 (Getting Started)
  • 주요 기능 (Features)
  • 튜토리얼 (Tutorials)
  • FAQ
  • 트러블슈팅 (Troubleshooting)

생성 프로세스:

  1. 사용자 여정 파악
  2. 스크린샷 위치 표시
  3. 단계별 가이드 작성
  4. 일반적인 문제 정리

4. README

구조:

  • 프로젝트 설명
  • 기능 (Features)
  • 설치 (Installation)
  • 사용법 (Usage)
  • 기여 가이드 (Contributing)
  • 라이센스 (License)

생성 프로세스:

  1. 프로젝트 메타데이터 추출
  2. 주요 기능 식별
  3. 설치 단계 자동 감지
  4. 배지 (Badges) 추가

문서 품질 체크

자동 검증

  • 구조: 표준 헤딩 구조 (H1 → H2 → H3)
  • 링크: 깨진 링크 없음
  • 코드 블록: 언어 지정 (python, bash)
  • 일관성: 용어 통일 (API vs api, Node.js vs nodejs)
  • 완전성: 필수 섹션 포함

스타일 가이드

# 제목은 문장형 (Sentence case)

## 부제목도 문장형

- 리스트는 일관된 형식
  - 들여쓰기 유지
  - 마침표 규칙 통일

**굵게**: 중요 용어
`코드`: 명령어, 파일명, 함수명

> 인용구: 주의사항, 팁

문서 리뷰 프로세스

1. 구조 리뷰

  • 논리적 흐름 확인
  • 섹션 순서 검증
  • 중복 제거

2. 내용 리뷰

  • 기술적 정확성
  • 예시 코드 동작 확인
  • 스크린샷 최신화

3. 언어 리뷰

  • 문법 및 맞춤법
  • 일관된 톤 & 보이스
  • 전문 용어 정확성

4. 형식 리뷰

  • Markdown 문법 확인
  • 링크 검증
  • 코드 블록 형식

자동 업데이트 트리거

다음 변경 시 관련 문서 자동 업데이트:

변경 영향받는 문서
API 엔드포인트 추가/변경 API 문서, README
새 기능 추가 사용자 가이드, README
의존성 변경 README (Installation)
아키텍처 변경 아키텍처 문서, ADR

Read the full file on GitHub · 265 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 · 265 lines · 26 tokens per session scan A fd4a248a7c8a

Subscribe to this mod's changes

doc-coauthoring is a skill published in the GitHub repository This-HW/claude-code-kit (4 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,415 once invoked, about $0.0001 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-31.

Claude CodeWriting and docsai-agentsanthropicclaude-code-pluginclaude-pluginsdeveloper-tools
Related

Other skills, from other repositories

code-standards

Prabhdeep (Sonu) Singh's personal coding standards — the house rules and quality bar for how code gets written. INVOKE before writing, generating, refactoring, or reviewing ANY code in ANY language — schemas, endpoints, queries, logging, validation, error handling — even when nobody says "standards" or "style".…

PrabhdeepSingh/claude-plugins · 81 tokens

design-tree

Make design decisions as an explicit branching tree — genuine alternatives, decisive rationale, rejected branches preserved. INVOKE PROACTIVELY when planning or designing any implementation approach, or choosing between architectures, libraries, or data models — especially in plan mode. Skip trivial or forced changes…

PrabhdeepSingh/claude-plugins · 62 tokens

self-review

Surface the riskiest parts of the current diff so a reviewer knows where to look hardest — one inline pass on small diffs, one cold read on a cheaper model tier with in-session synthesis on substantial ones. INVOKE PROACTIVELY whenever a change is finished and about to be handed off, reviewed, or shipped. It points…

PrabhdeepSingh/claude-plugins · 79 tokens

ticket-lifecycle

The ticket-as-control-plane rulebook — the single home for the tracker-operations contract, tracker resolution, the type/priority taxonomy, human-only trigger authorization, derived status, and trust boundaries. INVOKE when reading or writing tickets in a queue-driven flow, resolving a repo's tracker, or deciding…

PrabhdeepSingh/claude-plugins · 105 tokens

tdd

Test-driven development — the red-green-refactor discipline for code that's correct by design, not by accident. INVOKE PROACTIVELY whenever writing or changing code, fixing a bug, adding or structuring tests, or choosing what to mock — even when nobody says "TDD" or "tests". (Tests are code held to…

PrabhdeepSingh/claude-plugins · 80 tokens

pr-conventions

Author PR descriptions from the right per-change-type template (the repo's own PULLREQUESTTEMPLATE wins), embed issue-tracker links, keep the description current as fixes land, and reply to human and bot review threads. INVOKE when opening or updating a PR or responding to reviewer comments — inside /sonu:ship or…

PrabhdeepSingh/claude-plugins · 80 tokens