documentation
prinx/agents/skills/documentation/SKILL.md
Use at a meaningful delivery milestone when durable user, API, or operational documentation must be updated.
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
prinx/agents/skills/documentation/SKILL.md
Use at a meaningful delivery milestone when durable user, API, or operational documentation must be updated.
psubramanian/Claude-Skills/documentation/SKILL.md
Write effective documentation for SaaS projects covering code comments, API docs, README files, and technical specifications. TRIGGER this skill automatically when the user mentions: writing docs, README, API documentation, JSDoc, TypeDoc, inline comments, "how do I document this", onboarding docs, CHANGELOG, technical spec, ADR (Architecture Decision Records), "the team doesn't understand this code", or any request to make code or systems easier to understand. Also trigger when public APIs or complex logic have no documentation.
syntropic137/harness-app-template/.claude/skills/documentation/SKILL.md
Use when reviewing documentation concerns: README presence and quality, public API documentation, ADR coverage for non-obvious decisions, inline rationale comments, TBD/placeholder hygiene in shipped docs
syntropic137/software-leverage-points/skills/documentation/SKILL.md
Use when reviewing documentation concerns: README presence and quality, public API documentation, ADR coverage for non-obvious decisions, inline rationale comments, TBD/placeholder hygiene in shipped docs
TJM-NZ/claude-skills/documentation/SKILL.md
Documentation quality audit and writing — README completeness, inline comment quality, API reference docs. Finds gaps in existing docs or writes missing documentation.
tofusito/multi-agents/skills/documentation/SKILL.md
Technical documentation workflow for capturing work done — decisions, commands, issues, and resolutions — into structured Markdown notes saved to an Obsidian vault.
zeeshanalimughal/claude-skills/skills/documentation/SKILL.md
Writing documentation people actually read — READMEs, API docs, ADRs, comments, changelogs, and technical writing style. Use when writing any docs, README, comments, or explaining a system in writing.
heymrun/heym/.cursor/skills/heym-documentation/SKILL.md
Create and update documentation articles for the Heym platform. Use when adding docs pages, writing reference articles from summaries, or when the user provides an outline for a new article.
MoizIbnYousaf/Ai-Agent-Skills/skills/code-documentation/SKILL.md
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
13 projects use a version of this
documenso/documenso/.agents/skills/create-documentation/SKILL.md
Generate markdown documentation for a module or feature
Steady14 mentions in 2 weeks
1 project uses a version of this
irahardianto/awesome-agv/.agents/skills/api-documentation/SKILL.md
OpenAPI 3.1 specification writing, request/response examples, error documentation, versioning, and interactive API portal patterns.
TriliumNext/Trilium/.claude/skills/writing-documentation/SKILL.md
Use whenever a change is user-facing — a new feature, a moved or removed button, a label, a shortcut, an option, a default, a note type, a collection view, an import format — or when asked to write, fix, restructure or audit Trilium's documentation ("document this", "update the User Guide", "add a page for X", "is X documented?", "which page describes X?", "the docs still say…", "rename/move this page", "add a screenshot", "which icon do I use?"). Covers the docs trees (`docs/User Guide`, `docs/Developer Guide`, `docs/Release Notes`) and the generated in-app help, `!!!meta.json` (noteId, shareAlias, iconClass, attachments), the User Guide house style (register, templates, reference pills, `<kbd>`, admonitions, figures, `bx`/`cke`/`tn-brand` icon spans), and `docs.mjs` (find/show/scaffold pages, register images, rename/move/delete, map a diff to affected pages, audit, regenerate the in-app help). A user-facing change is not finished until the User Guide describes it, in the same commit.
Steady4 mentions in 2 weeks
8 projects use a version of this
zhu1090093659/dsh-web-ui/.agents/skills/dsh-web-documentation/SKILL.md
Use when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
moltbot/moltbot/.agents/skills/technical-documentation/SKILL.md
Build and review high-quality technical docs as well as agent instruction files in your repository.
30 projects use a version of this
rajnandan1/kener/.claude/skills/documentation-writer/SKILL.md
Specialized skill for creating and editing high-quality Kener documentation. MUST be used whenever creating or editing documentation files in the src/routes/(docs)/docs/content/ directory or updating docs.json navigation.
Steady9 mentions in 2 weeks
36 projects use a version of this
canonical/snapcraft/.github/skills/documentation-build/SKILL.md
Validates documentation builds successfully. Use when checking Sphinx/RTD build integrity or diagnosing build failures. Reports errors, warnings, and build configuration issues.
canonical/snapcraft/.github/skills/documentation-style/SKILL.md
Enforces project documentation style guide compliance for tone, voice, terminology, punctuation, and formatting. Use when checking documentation style or validating MyST/reST syntax. Cites specific style guide violations.
JabRef/jabref/skills/developers/module-documentation/SKILL.md
How to write and maintain package-level (package-info.java) and module-level (module-info.java) Javadoc in JabRef, including deep links into devdocs.jabref.org. Use when adding a package or changing a package's or module's public surface.
Steady4 mentions in 2 weeks
No other project uses it yet
samber/cc-skills-golang/skills/golang-documentation/SKILL.md
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.
Steady11 mentions in 2 weeks
10 projects use a version of this
Often used withgolang-swaggergolang-pkg-go-devgolang-refactoring
jmfederico/pi-web/.agents/skills/documentation-guide/SKILL.md
Repository documentation placement and writing guidance. Use this skill whenever writing, modifying, reviewing, or planning README.md, anything under docs/, setup or installation instructions, troubleshooting or FAQ content, configuration references, operational guidance, or user-facing documentation in a feature or fix. Keep the README concise and put detailed material in its canonical documentation page.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.