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.
hallucinautSkillhallucinaut/skills/documentation/SKILL.md
Write and maintain documentation. Use when creating READMEs, API docs, user guides, architecture diagrams, or any technical documentation.
Often used withcreate-media-packresponse-styleproject-preferences
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.
Often used withcreate-media-packresponse-styleproject-preferences
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.
Often used withcreate-media-packresponse-styleproject-preferences
its-ashSkillits-ash/skills/documentation/SKILL.md
Keeps long-lived project docs from rotting: gives existing docs constitution, map, status, and history roles and wires AGENTS.md or CLAUDE.md to them, plus onboarding guides, CodeTour walkthroughs, domain glossaries with ADR handoff, and growth-log entries. Use when docs drift from code, agents lose context, deleted files come back, you need a project map, status page, delete-zone, or decision log, onboard to a repo, write a starter CLAUDE.md, create a .tour file, define terms in CONTEXT.md, or record lessons. Sub-skills: codebase-onboarding, code-tour, context-and-decisions, growth-log.
Often used withcreate-media-packresponse-styleproject-preferences
kiko197Skillkiko197/skill/documentation/SKILL.md
生成和维护清晰、准确的技术文档。当需要编写 README、模块/API 说明、设计文档、ADR（架构决策记录）、变更日志，或统一写作结构与规范时使用。
Often used withcreate-media-packresponse-styleproject-preferences
MesteriisSkillMesteriis/Engineering-Bible-AI/skills/documentation/SKILL.md
Updates technical docs for verified behavior, public contracts, commands, configuration, and operations.
Often used withcreate-media-packresponse-styleproject-preferences
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.
Often used withcreate-media-packresponse-styleproject-preferences
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.
Often used withcreate-media-packresponse-styleproject-preferences
prinxSkillprinx/agents/skills/documentation/SKILL.md
Use at a meaningful delivery milestone when durable user, API, or operational documentation must be updated.
Often used withcreate-media-packresponse-styleproject-preferences
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.
Often used withcreate-media-packresponse-styleproject-preferences
syntropic137Skillsyntropic137/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
Often used withcreate-media-packresponse-styleproject-preferences
syntropic137Skillsyntropic137/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
Often used withcreate-media-packresponse-styleproject-preferences
thistleknotSkillthistleknot/skills/documentation/SKILL.md
Documentation strategy and artifact-selection protocol. Use when updating README/changelog/docs, choosing timestamped vs cumulative records, or producing validation and fixes-applied artifacts after substantive changes.
Often used withcreate-media-packproject-preferences
TJM-NZSkillTJM-NZ/claude-skills/documentation/SKILL.md
Documentation audit, writing and upkeep - starts from who needs which answers (new contributor, operator, API consumer, user, coding agent), maps the docs that exist, checks them against the code for accuracy, and finds what is missing, misplaced or stale. Writes README, guides, reference, decision records, runbooks and agent files on approval, marking anything the code cannot prove. Stack-agnostic.
Often used withcreate-media-packresponse-styleproject-preferences
tofusitoSkilltofusito/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.
Often used withcreate-media-packresponse-styleproject-preferences
zeeshanalimughalSkillzeeshanalimughal/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.
Often used withcreate-media-packresponse-styleproject-preferences
MoizIbnYousafReads credentialsSkillMoizIbnYousaf/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.
GoogleSkillgoogle/A2UI/.agents/skills/public-documentation/SKILL.md
Defines authoring, multi-version tabbing, multi-SDK code example, and diagram standards for the A2UI developer site (docs/site/). Use when creating, editing, or reviewing public documentation, conceptual guides, tutorials, or quickstarts.
Surging12 mentions in 2 weeks
1 project uses a version of this
documensoSkilldocumenso/documenso/.agents/skills/create-documentation/SKILL.md
Generate markdown documentation for a module or feature
Steady4 mentions in 2 weeks
2 projects use a version of this
irahardiantoSkillirahardianto/awesome-agv/.agents/skills/api-documentation/SKILL.md
OpenAPI 3.1 specification writing, request/response examples, error documentation, versioning, and interactive API portal patterns.
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.
