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.
mturacSkillmturac/everything-openai-codex/.cursor/skills/documentation-lookup/SKILL.md
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).
Often used witheverything-claude-code-conventionsagent-sortbrand-voice
poradaSkillporada/domfiles/skills/.domfiles-agent-documentation/SKILL.md
Use for creating, editing, reviewing, auditing, or maintaining project-authored agent documentation, including `AGENTS.md`, `.agents/PROJECT.md`, skill documentation, reusable handoff and decision capture prompts, templates, canonical public-surface assets, and public skill READMEs. Also use for project agent documentation setup, repository independence, cross-repository alignment, documentation authority, ownership, composition, routing, redundancy, and token efficiency.
wondelaiReads credentialsSkillwondelai/skills/technical-documentation/SKILL.md
Audit, write, and improve developer documentation using Google''s Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or tutorial", "API reference", "docstrings", "CLI help text", "changelog or release notes", "migration guide", or "our docs are confusing". Also use it when writing docs from code, rewriting a doc for clarity, fixing headings, procedures, or code samples, or enforcing consistent voice and terminology across a docs set — prefer it over editing documentation unaided. Covers reader and doc-type fit, second person and active voice, procedures, headings, lists and tables, code samples and placeholders, link text, notices, the word list, timeless docs, and accessibility. For code comments and naming, see clean-code. For marketing or landing-page copy, see storybrand-messaging.
Steady3 mentions in 2 weeks
33 projects use a version of this
helpin-aiSkillhelpin-ai/helpin/.agents/skills/helpin-documentation/SKILL.md
Write, explain, review, name, or reorganize Helpin repository documentation and update its navigation. Use for documentation work in this repository, including architecture and contributor/operator guides.
ipspaceSkillipspace/netlab/.github/skills/developer-documentation/SKILL.md
Write configuration template developer documentation
shinprSkillshinpr/claude-code-workflows/skills/documentation-criteria/SKILL.md
Determines which of PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires, and where each is stored. Use when deciding documentation scope, or when creating or reviewing a technical document.
ErikaAX08SkillErikaAX08/erikas-skills/code-documentation/SKILL.md
Document code clearly, concisely, and professionally. Use when the user asks to document functions, classes, structs, or code files; add comments to existing code; improve existing documentation; or mentions "document", "comments", "docstrings", "JSDoc", "godoc", or "code documentation". Generates documentation that other engineers can quickly understand without being verbose, with strict prose line-count caps and no comment-width limit, while allowing one line per structured parameter, return, or error entry and forbidding per-property and per-interface-member documentation except for extreme type ambiguity.
HK-hubSkillHK-hub/AgentSkills/tech-documentation/SKILL.md
Technical documentation writing skill covering API docs, architecture documentation, deployment guides, and various technical writing best practices. Use this skill when creating technical documentation, writing API documentation, creating architecture design documents, or need templates for deployment and operations manuals.
openclawSkillopenclaw/openclaw-windows-node/.agents/skills/technical-documentation/SKILL.md
Write, review, or restructure Windows node documentation and agent instructions using current source, task-focused explanations, and explicit fact preservation.
31 projects use a version of this
SuperkikimSkillSuperkikim/nexus-ai-chat-importer/.agents/skills/rebuild-documentation/SKILL.md
Design, audit, or rebuild this repository's user documentation and README using the current code as evidence, with UX, DRY, navigation, and uncertainty tracking as acceptance criteria.
SuperkikimSkillSuperkikim/nexus-ai-chat-importer/.claude/skills/rebuild-documentation/SKILL.md
Design, audit, or rebuild this repository's user documentation and README using the shared cross-agent workflow.
fdiblenSkillfdiblen/rseng-agent-skills/skills/rseng-documentation/SKILL.md
Covers how to document research software at every level: writing a README, code-level docs (comments, docstrings, API and CLI help), project docs (INSTALL, CONTRIBUTING, LICENSE, CITATION, changelog), publishing hosted documentation with Read the Docs, and capturing a Research Software Story. Use when the user asks how to write or improve a README, decide what documentation their project needs, add docstrings or inline comments, document an API or CLI, set up Sphinx/MkDocs/Doxygen, host docs on Read the Docs, structure a docs site, or write the narrative context and history behind a project. For outward-facing papers, talks and announcements see rseng-science-communication; for public and citizen-science narrative see rseng-storytelling.
AndersonAndradSkillAndersonAndrad/skills/api-documentation/SKILL.md
Author and review API and application documentation for modified contracts using the project's existing documentation tooling, such as Swagger/OpenAPI. Use when endpoints, DTOs, integrations, configuration, or public behavior change. Notify the developer when no documentation tooling exists.
AxlZero21SkillAxlZero21/Skills/api-documentation/SKILL.md
OpenAPI/Swagger specification standards and API documentation best practices
baturReads credentialsSkillbatur/ts-baseline-docs/.agents/skills/documentation-adr/SKILL.md
Use this skill when creating, updating, or reviewing repository documentation, ADRs, engineering standards, architecture docs, Mermaid diagrams, README onboarding, Copilot instructions, or documentation changes required by architecture/API/security/database/auth/deployment decisions in TypeScript software projects.
jgeorgeai11Skilljgeorgeai11/claude_code_resources/.claude/skills/sas-documentation/SKILL.md
Document or review SAS files against project conventions. First step of the SAS conversion workflow — the documentation is what sas-conversion-planning plans from. Use when documenting one or more SAS files or reviewing existing SAS documentation; each file is handled in its own parallel pass and gets its own documentation file.
OpenBunReads credentialsSkillOpenBun/Skills/api-documentation/SKILL.md
Automatically generate comprehensive API documentation from a codebase or spec — covering REST, GraphQL, and WebSocket APIs. Use this skill whenever the user wants to document an API, analyze routes/resolvers/handlers to extract endpoints, create Swagger/OpenAPI specs or Postman collections, add JSDoc comments, set up Swagger UI, write authentication guides, document error codes, pagination, filtering, or rate limiting. Trigger for requests like document this API, write API docs, set up swagger, add JSDoc, generate OpenAPI, create a Postman collection, document my GraphQL schema, document my WebSocket events, or when a user shares any API code and asks how to document it.
PMDevSolutionsSkillPMDevSolutions/Nerva/.claude/skills/api-documentation/SKILL.md
Generates OpenAPI 3.1 specification from the Hono app and Zod schemas, sets up interactive API documentation using Scalar UI, generates Postman collections, and creates API quickstart documentation. Uses @hono/zod-openapi for spec generation. Keywords: openapi, swagger, documentation, docs, scalar, postman, collection, spec, api-reference, interactive, ui, endpoint, schema, quickstart, hono-zod-openapi
yiweiwanSkillyiweiwan/skills/.claude/skills/api-documentation/SKILL.md
Use only when writing or improving API documentation, endpoint references, REST docs, GraphQL docs, SDK docs, authentication docs, request and response examples, error codes, rate limits, pagination, and integration guides.
zekhoiSkillzekhoi/claude/.agents/skills/kit-documentation/SKILL.md
Write or update project documentation such as READMEs, setup and usage guides, and API references so it matches what the code actually does, with every command and example verified. Use when the user asks to write, update, or fix documentation, a README, or usage instructions. Do not use for code comments during feature work, changelogs for releases, or explaining code to the user in chat.
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.
