api-documentation
ronrefael/sonde/.claude/skills/api-documentation/SKILL.md
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
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.
ronrefael/sonde/.claude/skills/api-documentation/SKILL.md
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
slantview/pi-agents/skills/adr-documentation/SKILL.md
Creates, updates, reviews, indexes, and supersedes local Architecture Decision Records and related architecture documentation. Use for ADR work, documenting design decisions, checking implementation against accepted decisions, maintaining docs/adr files, or reconciling architecture docs with code.
flutter/skills/skills/dart-write-documentation/SKILL.md
Rules and formatting guidelines for writing Dart /// API documentation and doc comments. Use when documenting Dart code, writing doc comments for any Dart declaration (libraries, classes, methods, variables, etc.), or when instructed to follow the Effective Dart documentation guidelines.
pavel-molyanov/molyanov-ai-dev/.agents/skills/documentation-writing/SKILL.md
Creates and maintains a project's Project Knowledge and its CLAUDE.md entrypoint: initial project interview, updates after a change, audits and consistency checks, and feature finalization. Use whenever project documentation is created, updated, audited, or finalized, including documenting what a change did and finishing a feature. Only reading existing docs uses the project's project-knowledge skill.
pavel-molyanov/molyanov-ai-dev/skills/documentation-writing/SKILL.md
Creates and maintains a project's Project Knowledge and its CLAUDE.md entrypoint: initial project interview, updates after a change, audits and consistency checks, and feature finalization. Use whenever project documentation is created, updated, audited, or finalized, including documenting what a change did and finishing a feature. Only reading existing docs uses the project's project-knowledge skill.
full-stack-skills/rust-skills/skills/rust-documentation/SKILL.md
Design, write, build, test, and publish Rust documentation with rustdoc, cargo doc, doctests, intra-doc links, crate-level guides, examples, README synchronization, mdBook, docs.rs metadata, link checking, documentation CI, and the Rust API Guidelines Documentation chapter (C-DOC, C-LINK, C-META, C-EXAMPLE). Use when users ask for Rust API docs, a project book, runnable examples, docs.rs readiness, missing-doc policy, API guideline compliance, documentation architecture, or stale documentation repair.
bgauryy/octocode-mcp/skills/octocode-documentation/SKILL.md
Use when docs are missing, wrong, stale, or badly written, or need a copyedit against the Google style guide: README, API reference, runbook, CONTRIBUTING, changelog, onboarding, AGENTS.md/CLAUDE.md, ADR, migration guide, Diátaxis or whole-codebase restructure, docstrings, alt text, prose linting. Not for code, commits, or marketing copy. Code investigation → octocode-research; SKILL.md folders → octocode-skills.
mturac/everything-openai-codex/.agents/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
mturac/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
porada/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.
helpin-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.
ipspace/netlab/.github/skills/developer-documentation/SKILL.md
Write configuration template developer documentation
shinpr/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.
ErikaAX08/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-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.
openclaw/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
Superkikim/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.
Superkikim/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.
fdiblen/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.
NVIDIA/TensorRT-Edge-LLM/skills/edge-llm-documentation/SKILL.md
Write, edit, or review TensorRT Edge-LLM documentation using the Google developer documentation style guide. Apply to READMEs, tutorials, how-to guides, conceptual and design documents, API and CLI references, and release notes; not ordinary code changes or chat replies.
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.