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.
GitHubSkillgithub/awesome-copilot/skills/documentation-writer/SKILL.md
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
mckinseySkillmckinsey/agents-at-scale-ark/.claude/skills/documentation/SKILL.md
Guidance for structuring Ark documentation using the Diataxis framework. Use this skill when creating new docs, deciding where content belongs, reviewing documentation PRs, or restructuring existing documentation.
eduardo-slSkilleduardo-sl/go-agent-skills/skills/(code-quality)/go-documentation/SKILL.md
Go documentation conventions: godoc comments, package docs, testable Example functions, deprecation notices, doc links, and project docs (README, CHANGELOG, llms.txt). Use when: "add godoc", "document this package", "write doc comments", "add examples to docs", "deprecate a function", "write a README", "update the changelog", "improve the docs". Not for: commit messages (git-commit), code style (go-coding-standards).
addyosmaniReads credentialsSkilladdyosmani/agent-skills/skills/documentation-and-adrs/SKILL.md
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Often used withconstraint-driven-developmentdeprecation-and-migrationdoubt-driven-development
bmarshall511Skillbmarshall511/Trellis/.claude/skills/documentation/SKILL.md
Use when writing a README, documenting a module or component, recording a decision, or deciding whether something needs explaining at all. Also when documentation has drifted from the code.
charly-vibesSkillcharly-vibes/incitaciones/skills/documentation/SKILL.md
Documentation suites: audit or plan docs, write with Diátaxis/Info Mapping/EPPO, review for scannability and AI-readiness. Trigger for doc planning, writing, or review. Broken links are doc-link-verifier, not this.
dewitt4Skilldewitt4/claude-code-template/.claude/skills/documentation/SKILL.md
Create and maintain technical documentation including README files, API docs, inline comments, architecture diagrams, and user guides
eliabdevweb-svgSkilleliabdevweb-svg/opencode-skills-MCP/skills/documentation/SKILL.md
Redaction de documentation technique: README, docs API, guides, changelogs. Use when writing or improving technical documentation, README files, or developer guides.
eyssetteSkilleyssette/js-template/.agents/skills/documentation/SKILL.md
Rédiger de la documentation technique ou utilisateur. À utiliser pour commencer une fonction ou un script, pour expliquer comment un module fonctionne, pour créer un tutoriel, une notice d'utilisation, ou compléter le README.
FreddyPolySkillFreddyPoly/claude-skills/documentation/SKILL.md
After finishing a non-trivial code change (new feature, bug fix, refactor, architecture decision), update the project's root documentation files — CLAUDE.md, SPEC.md, README.md, or whatever equivalent already exists — so a future agent or teammate can open the project cold and understand what it does, what changed, and how to continue. Create these files if none exist. Use at the end of a change, not before or during. Do not use for trivial edits (typo fixes, one-line tweaks, formatting) or read-only/exploratory work with no code change. Works in any conversation language, English or French included — write the documentation in whatever language the existing docs use, or the user's language if there's no precedent.
Geoffe-GaSkillGeoffe-Ga/well-worn-tools/.claude/skills/documentation/SKILL.md
Write clear, comprehensive documentation with language-specific patterns. Use when writing docstrings, module docs, README files, API references, or architecture decision records. Covers Python, TypeScript, Go, and Rust documentation conventions. Do NOT use for code style (use vibe skill).
hallucinautSkillhallucinaut/skills/documentation/SKILL.md
Write and maintain documentation. Use when creating READMEs, API docs, user guides, architecture diagrams, or any technical documentation.
IcodeNetSkillIcodeNet/agent-skills/skills/documentation/SKILL.md
Writes and updates docs, READMEs, runbooks, specs, and ADRs. Use when documenting a feature, writing a runbook, updating README/setup docs, or recording decisions. Do not use for competitive research briefs or for code comments that only restate the next line.
InfiniteRoomLabsSkillInfiniteRoomLabs/agent-ops/skills/documentation/SKILL.md
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
kiko197Skillkiko197/skill/documentation/SKILL.md
生成和维护清晰、准确的技术文档。当需要编写 README、模块/API 说明、设计文档、ADR（架构决策记录）、变更日志，或统一写作结构与规范时使用。
MesteriisSkillMesteriis/Engineering-Bible-AI/skills/documentation/SKILL.md
Updates technical docs for verified behavior, public contracts, commands, configuration, and operations.
mj-devingSkillmj-deving/pai-skills/skills/Documentation/SKILL.md
Documentation practices — comment guidelines, ADR conventions, API documentation, inline docs philosophy, doc health scanning and maintenance. USE WHEN documentation, write docs, comment guidelines, ADR, architecture decision, API docs, JSDoc, OpenAPI, document code, when to comment, how to document, self-documenting code, README, doc health, doc drift, stale docs, fix docs, doc maintenance, check docs.
muxammadmamajonovSkillmuxammadmamajonov/dot-claude/.claude/skills/documentation/SKILL.md
Use when writing or updating specs, READMEs, API/reference docs, ADRs, or runbooks — record an ADR per decision, update docs when a feature ships, fix drifted docs.
prinxSkillprinx/agents/skills/documentation/SKILL.md
Use at a meaningful delivery milestone when durable user, API, or operational documentation must be updated.
psubramanianReads credentialsSkillpsubramanian/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.
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.
