document
daledesilva/obsidian_ink/.agents/skills/document/SKILL.md
Document new or materially changed feature behavior implemented in the current chat thread.
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.
daledesilva/obsidian_ink/.agents/skills/document/SKILL.md
Document new or materially changed feature behavior implemented in the current chat thread.
OneWave-AI/claude-skills/api-documentation-writer/SKILL.md
Generate comprehensive API documentation including endpoint descriptions, request/response examples, authentication guides, error codes, and SDKs. Creates OpenAPI/Swagger specs, REST API docs, and developer-friendly reference materials. Use when users need to document APIs, create technical references, or write developer documentation.
xenitV1/Antigravity-Workflows/skills/documentation-templates/SKILL.md
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
Often used withintelligent-routingrust-proweb-design-guidelines
henrique-simoes/Istara/skills/deliver/handoff-documentation/SKILL.md
Generate developer handoff docs: specs, annotations, edge cases, accessibility requirements.
Dyfree/problem-navigator/skills/solution-documentation/SKILL.md
Project frozen solution semantics into an accepted formal report or one product/software document package.
michellepellon/superpowers/skills/documentation-audit/SKILL.md
Systematically verify documentation claims against codebase reality. Use when auditing docs, before releases, after refactors, or when documentation drift is suspected. Two-pass approach with pattern expansion ensures comprehensive detection of false claims, dead references, and gaps.
tusharpandey13/forge/skills/forge-documentation/SKILL.md
Create documentation after implementation and reviews are complete. Use when documenting features, adding docstrings, updating README, or creating context files.
microsoft-foundry/foundry-agent-webapp/.github/skills/reviewing-documentation/SKILL.md
Provides documentation audit checklists and quality standards. Use when reviewing README files, SKILL.md files, agent definitions, copilot-instructions.md, or ARCHITECTURE-FLOW.md for quality and consistency.
pr-pm/prpm/.claude/skills/documentation-standards/SKILL.md
Standards and guidelines for organizing, structuring, and maintaining documentation in the PRPM repository - ensures consistency across user docs, development docs, and internal references
JPeetz/agent-skills/skills/documentation-content/documentation-and-adrs/SKILL.md
Use this skill when you need to record an architecture decision (ADR) or document the reasoning behind a design choice — when changing public APIs, shipping features that change behavior, or recording context that future engineers (human or agent) will need to understand the codebase. Does NOT replace code comments or inline docstrings; targets strategic documentation and decision capture. Primary keywords: ADR architecture decision record, technical documentation, design rationale, decision log, API documentation, README writing, changelog, documentation-driven development, inline documentation best practices, specification writing. For all major agentic platforms.
Often used withconstraint-driven-developmentdeprecation-and-migrationdoubt-driven-development
NVIDIA/elements/.agents/skills/authoring-documentation/SKILL.md
Guidelines for writing documentation files including 11ty templates, Eleventy shortcodes, JSDoc annotations, and markdown content. Use this skill whenever the user works with documentation markdown files, Vale prose linting errors, Eleventy shortcodes (dodont, example), frontmatter, JSDoc annotations that must pass Vale, or the documentation site. Also trigger when the user mentions Vale errors, adding terms to the vocabulary, suppressing Vale rules, or writing and fixing prose in .md or .ts files.
adobe/S3Mock/.agents/skills/document/SKILL.md
Generate and update S3Mock project documentation. Use when asked to document code, update CHANGELOG.md, update README.md, update AGENTS.md files, or fix formatting, wording, or style in any existing documentation file. Also invoked at the end of the implement skill workflow.
launchapp-dev/animus-cli/.claude/skills/documentation-template/SKILL.md
Generate structured documentation templates for components, patterns, or guidelines within a design system.
shinpr/codex-workflows/.agents/skills/documentation-criteria/SKILL.md
Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each document lives. Use when deciding documentation scope or creating or reviewing one of these artifacts.
bagisto/agent-skills/skills/bagisto-documentation/SKILL.md
Use when writing or updating any Bagisto documentation site — the developer documentation, the merchant user guide, or any other Bagisto docs repository — covering page content, code samples, screenshots, the sidebar, image naming, and moving or deleting pages. Trigger phrases include "docs", "documentation", "user guide", "developer documentation", "dev docs", "merchant documentation", "marketplace docs", "document this", "update the docs", "add a doc page", "screenshot", "ImagePopup", "redirect a doc page".
barlevalon/skills/skills/documentation-system/SKILL.md
Apply the Diátaxis framework to write, audit, organize, and improve technical documentation. Use when creating or revising tutorials, how-to guides, reference, explanation, docs IA, README sections, or documentation that feels mixed, incomplete, or hard to use.
dawiddiwad/checkmate/.agents/skills/update-documentation/SKILL.md
Align Checkmate documentation and examples with changes to versioned contracts, drivers, configuration, evidence, or CLI/API workflows.
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.