Find the best CLAUDE.md, AGENTS.md and Claude skills

curvedinfSkill

documentation-style

curvedinf/dev-skills/skills/passive/documentation-style/SKILL.md

Documentation, prose, wording, terminology, examples. Apply concise evidence-driven writing conventions when enabled; use polish-docs for an onboarding redesign.

jordanhubbardSkill

releasing-documentation

jordanhubbard/nanolang/skills/releasing/documentation/SKILL.md

Bring README, CONTRIBUTING, the user guide and the roadmap current before a NanoLang release is tagged. Use when make release-docs-check names one of them, or when preparing a release by hand.

aiproxerSkill

golang-documentation

aiproxer/aiproxer/.agents/skills/golang-documentation/SKILL.md

Write and review Go documentation against code: API contracts, doc comments, executable examples, command/config instructions, and release artifacts.

Often used withgolang-pkg-go-dev·golang-how-to·golang-refactoring

jim60105Skill

documentation-writer

jim60105/copilot-prompt/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.

PracticalSwanSkill

documentation-automation

PracticalSwan/agent-skills/documentation-automation/SKILL.md

Automate doc generation with JSDoc/TSDoc, linters, and pre-commit hooks. Use when setting up markdownlint, configuring doc linting pipelines, integrating JSDoc/TSDoc, or building automated documentation workflows.

ghuntleySkill

antithesis-documentation

ghuntley/loom/.agents/skills/antithesis-documentation/SKILL.md

Use Antithesis documentation efficiently for product, workflow, and integration questions. Prefer the snouty docs CLI when available, and otherwise request markdown versions of documentation pages directly.

thalysjuvenalSkill

documentation-patterns

thalysjuvenal/advpl-specialist/skills/documentation-patterns/SKILL.md

Use when the user wants to generate technical documentation for ADVPL/TLPP code on TOTVS Protheus -- Protheus.doc header blocks (@type, @param, @return, @author, @since, @history), complete routine documentation (tables read/written, MV_* parameters, entry points, execution flow, dependencies), or REST API endpoint documentation (path/query parameters, request/response JSON, status codes). Also triggers on Portuguese phrasing like "documentar rotina", "gerar cabecalho Protheus.doc", "documentar endpoint", "documentar API REST", or requests to add documentation to legacy/undocumented code.

Sapere-IASkill

documentation-update

Sapere-IA/sdd-onboarding-kit/skills/optional/documentation-update/SKILL.md

Update documentation affected by a completed task, after technical review and before the task is marked done. Use when review identifies documentation targets.

NewFutureSkill

documentation-maintenance

NewFuture/DDNS/.agents/skills/documentation-maintenance/SKILL.md

Maintain DDNS VitePress documentation with bilingual parity, correct navigation and links, safe executable-doc changes, and build verification.

klawisha012Skill

golang-documentation

klawisha012/agentsync/.agents/skills/golang-documentation/SKILL.md

Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.

Often used withgolang-pkg-go-dev·golang-how-to·golang-refactoring

bnemaSkill

documentation-pass

bnema/pi-public/skills/documentation-pass/SKILL.md

Use when a documentation pass is needed or docs, README, guides, examples, changelogs, or public explanations may be stale before PR.

BurakDSkill

documentation-sync

BurakD/ai-engineering-harness/skills/documentation-sync/SKILL.md

Keeps durable project documentation aligned with implementation and operating reality. Use when a change affects product behavior, architecture, data, APIs, configuration, environments, release procedures, commands, or other facts future maintainers need.

CallicrateSkill

make-documentation

Callicrate/skills/make-documentation/SKILL.md

Use when writing READMEs, architecture, changelogs, release notes, runbooks, notebook docs, install docs, or security articles; produces docs. Do not trigger for API docs, AGENTS.md, or diagrams.

dss-timeSkill

documentation-sync

dss-time/repo-doctor-skills/skills/documentation-sync/SKILL.md

Synchronize documentation with a confirmed code, configuration, API, or behavior change by updating only evidence-backed README, API, configuration, example, migration, and changelog content while preserving style and language. Use for documentation-only edits; do not modify production behavior, invent undocumented facts, or use as a general code fix. 根据已确认的代码、配置、API 或行为变更，只更新有证据支持的 README、API、配置、示例、迁移和 CHANGELOG 内容，并保留原有风格与语言。用于仅文档修改；不得改变生产行为、编造未证实内容，也不作为通用代码修复。

FlashlockSkill

documentation-agent

Flashlock/kahn-queue/.cursor/skills/documentation-agent/SKILL.md

Writes or upgrades API docs (Javadoc, etc.) with minimal, usage-focused text. Use when the user asks to document code, add Javadoc, upgrade docs, or apply documentation standards.

Frictionless-LabsSkill

obra-documentation

Frictionless-Labs/claude-skills/skills/obra-documentation/SKILL.md

Generates comprehensive documentation including READMEs, API docs, and inline comments

GiammeSkill

exec-documentation

Giamme/linear-spanks/skills/extras/exec-documentation/SKILL.md

Execution skill loaded when a task requires updating docs, READMEs, or inline comments.

KMaruthi2002Reads credentialsSkill

code-documentation

KMaruthi2002/universal-llm-skills/skills/code-documentation/SKILL.md

Write and maintain documentation that lives with code: comments that earn their place, docstrings and doc comments, READMEs, API reference, architecture and decision records, runbook-style operational notes, and changelogs — and keep them true as the code changes, in the project's existing voice and tooling. Use when adding or reviewing comments or docstrings, writing or fixing a README, documenting a module, public API, or design decision, updating a changelog, or when docs have drifted from the code. For a standalone docs website use documentation-site; for long-form prose guides use technical-writing.

KMaruthi2002Reads credentialsSkill

documentation-site

KMaruthi2002/universal-llm-skills/skills/documentation-site/SKILL.md

Plan, build and maintain a documentation website for a product, API, library, platform or internal system: information architecture (tutorials, how-to guides, reference, explanation), choosing a static site generator or hosted docs platform, navigation and search, versioning for multiple releases, generated API reference, code samples that are tested and actually run, docs-as-code workflow with review, previews, link checking and CI, plus accessibility, internationalisation and analytics. Use when someone asks to create a docs site, developer portal, knowledge base, handbook site, migrate docs to a new generator, add versioning or search to docs, or fix docs that users cannot navigate or that have drifted from the product.

mashharukiReads credentialsSkill

repo-documentation

mashharuki/claude-code-sample/.claude/skills/repo-documentation/SKILL.md

リポジトリの構造・技術スタック・機能一覧・セットアップ手順を動的に解析し、 包括的なドキュメントを自動生成するスキル。言語・フレームワーク問わず汎用的に動作する。 Use this skill whenever the user asks to: - Explain a repository / リポジトリの説明 / リポジトリの概要 - Generate a README / README生成 / README作成 - Understand project structure / プロジェクト構成を教えて / 構造を説明して - Learn how to run a project / 使い方を教えて / 動かし方 / セットアップ方法 - Get a repo overview / repo overview / explain this repo / what does this repo do - List features / 機能一覧 / このプロジェクトは何ができる？ - Onboard to a new codebase / コードベースのキャッチアップ / 新しいリポジトリに入った - "このリポジトリ何？" "プロジェクトの全体像" "how to run this project" - "コードの全体を把握したい" "ドキュメントを整備して" "技術スタックを知りたい" This skill is especially useful when joining a new project, onboarding team members, or when a repository lacks proper documentation. It works with ANY repository regardless of programming language, framework, or project type.