DO

Writes and maintains project documentation by autonomously creating pull requests for review.

Install

mkdir -p .claude/skills/doc-author && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3656" && unzip -o skill.zip -d .claude/skills/doc-author && rm skill.zip

Installs to .claude/skills/doc-author

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Write, edit, and maintain documentation. Use for collaborative drafting, autonomous writing, or improving existing docs. Defaults to collaborative mode where the human makes final decisions. Built by Mintlify.
209 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • →Draft documentation collaboratively
  • →Write documentation autonomously via PRs
  • →Maintain existing documentation patterns
  • →Flag uncertainties with TODO comments
  • →Verify content against codebase

How it works

The agent operates in collaborative or autonomous modes, using codebase context to draft or update MDX files, always submitting changes through pull requests.

Inputs & outputs

You give it
Codebase or documentation brief
You get back
Pull request with documentation changes

When to use doc-author

  • →Generating API docs from code
  • →Updating project READMEs
  • →Drafting technical documentation improvements

About doc-author

This agent generates and maintains documentation based on the codebase. It operates either in collaborative mode with a human or autonomously, submitting all changes via pull requests to ensure verified accuracy.

Write and maintain documentation autonomously. Use when assigned to create, update, or improve documentation without direct human oversight. Always opens PRs for review. Built by Mintlify.

When not to use it

  • →When the feature or concept cannot be verified
  • →When the audience or goal is unclear

Prerequisites

Git accessAbility to create pull requests

Limitations

  • →Cannot document features that cannot be verified in the code
  • →Requires human review for autonomous PRs

How it compares

This agent integrates directly into the development workflow by autonomously managing PRs and adhering to specific documentation standards.

Compared to similar skills

doc-author side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
doc-author (this skill)19moNo flagsIntermediate
readme-generator31yReviewBeginner
ml-paper-writing489moReviewAdvanced
docs-review1011moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

readme-generator

aws-samples

This skill should be used when users want to create or improve README.md files for their projects. It generates professional documentation following the Deep Insight/Strands SDK style - comprehensive yet focused, with clear structure and practical examples.

339

ml-paper-writing

davila7

Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.

4897

docs-review

metabase

Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.

1085

claude-md-improver

anthropics

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".

2167

write-docs

tldraw

Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.

665

update-docs

vercel

This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.

2543

Search skills

Search the agent skills registry