Write, review, or restructure Windows node documentation and agent instructions using current source, task-focused explanations, and explicit fact preservation.
Surging1 mention in 2 weeks
30 projects use a version of this
2.2k16d agoReviewMountCreate a free account to mount
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.
2112mo agoReviewMountCreate a free account to mount
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.
203mo agoReviewMountCreate a free account to mount
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.
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.
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.
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.
Document a multi-component pattern (form validation, empty states, error handling): when to use, composition, states, a11y, anti-patterns. Triggers: document this pattern, write the pattern page. One named component: use usage-guidelines. Choosing a component: component-decision-tree.
19740d agoReviewMountCreate a free account to mount
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).
Write or update project documentation from code evidence: READMEs, tutorials, how-to guides, reference pages, explanations, and architecture decision records, running each documented command or marking it unverified. Use when asked to document a feature, API, CLI, configuration, or design decision, fix stale or broken docs, or write an ADR. Not for onboarding guides (use the onboard-to-codebase skill) or AGENTS.md and CLAUDE.md files (use the init-agent-context skill).
182mo agoReviewMountCreate a free account to mount
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Create and optionally run EPAC policy documentation configurations for assignment reports and policy set comparisons. Use when asked to generate, configure, scaffold, build, or update policyDocumentations JSON/JSONC files, document all or representative Azure Policy assignments, compare initiatives, or run Build-PolicyDocumentation.
Use when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. This should trigger for requests such as Improve the code with documentation; Apply documentation; Refactor the code with documentation; Generate README or developer documentation for a Java project; Document Java APIs architecture or project workflows. Part of Plinth Toolkit
4523mo agoReviewMountCreate a free account to mount
Validates documentation structural integrity including heading hierarchy, metadata, file naming, navigation, and cross-references. Use when checking documentation organization or validating toctree structure.
1.3k8mo agoReviewMountCreate a free account to mount
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.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
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.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
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.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.