One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.
ob-labsSkillob-labs/agentseek/.agents/skills/documentation-writer/SKILL.md
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework. Templates for tutorial / how-to / reference / explanation live under templates/.
MicrosoftSkillmicrosoft/devsquad-copilot/.github/plugins/devsquad/skills/documentation-style/SKILL.md
Formatting and style rules for markdown documentation. Use when generating or editing any project markdown document. Do not use for source code, code comments, or commit messages. For work item content (titles, descriptions, comments on GitHub Issues or Azure DevOps), use the Content Style section of the `work-item-creation` skill.
Microsoft AzureSkillAzure/terraform-azurerm-avm-ptn-alz/.github/skills/avm-tf-documentation/SKILL.md
Use for AVM Terraform generated README content, _header.md, _footer.md, examples documentation, terraform-docs inputs, and Avm.Authoring documentation checks.
canonicalSkillcanonical/workshop/.github/skills/documentation-review/SKILL.md
Performs comprehensive documentation review including build validation, Diataxis analysis, structure audit, accuracy verification, and style compliance. Use when reviewing documentation changes or auditing documentation quality.
canonicalSkillcanonical/workshop/.github/skills/documentation-verify/SKILL.md
Verifies documentation accuracy by cross-referencing claims, CLI commands, API signatures, and configuration against source code. Use when validating documentation correctness or checking code-docs consistency. Flags unsupported or outdated claims.
GitHubSkillgithub/awesome-copilot/skills/oo-component-documentation/SKILL.md
Create or update standardized object-oriented component documentation using a shared template plus mode-specific guidance for new and existing docs.
fmindSkillfmind/dot/skills/documentation-site/SKILL.md
Build and migrate Zensical documentation sites, navigation, search, and course pages.
mryeminaungSkillmryeminaung/documentation-assistant/.claude/skills/code-documentation/SKILL.md
How to explain source code, generate inline comments, write Markdown documentation, summarize a file, or improve variable/function names — for JavaScript, TypeScript, Python, Java, C++, and Dart. Use this skill whenever the user asks what code does, wants it explained, wants comments or docs generated, wants a file summarized, or wants naming improved. Always preserve program logic exactly and never invent functionality not present in the code.
ronrefaelSkillronrefael/sonde/.claude/skills/api-documentation/SKILL.md
API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation.
mturacSkillmturac/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).
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).
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.
poradaSkillporada/domfiles/skills/.domfiles-agent-documentation/SKILL.md
Use for editing, reviewing, auditing, or maintaining project-authored agent documentation, including `AGENTS.md`, `.agents/PROJECT.md`, skill documentation, relay assets, canonical public-surface assets, and public skill READMEs. Also use for documentation authority, ownership, composition, routing, redundancy, and token efficiency.
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.
wondelaiSkillwondelai/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.
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.
baturSkillbatur/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.
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
murphytruemanSkillmurphytrueman/design-system-ops/skills/pattern-documentation/SKILL.md
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.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.
