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

castacksDeletes or force-pushesSkill

update-documentation

castacks/AirStack/.agents/skills/update-documentation/SKILL.md

Document new modules and update mkdocs navigation. Use after implementing any new feature or module. Covers README templates, mkdocs.yml updates, mermaid diagrams, and documentation standards for AirStack.

pavel-molyanovSkill

documentation-writing

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-molyanovSkill

documentation-writing

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-skillsSkill

rust-documentation

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.

bgauryySkill

octocode-documentation

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.

mturacSkill

documentation-lookup

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-conventions·agent-sort·brand-voice

mturacSkill

documentation-lookup

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-conventions·agent-sort·brand-voice

wondelaiReads credentialsSkill

technical-documentation

wondelai/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.

poradaSkill

agent-documentation

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-aiSkill

helpin-documentation

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.

ipspaceSkill

developer-documentation

ipspace/netlab/.github/skills/developer-documentation/SKILL.md

Write configuration template developer documentation

shinprSkill

documentation-criteria

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.

ErikaAX08Skill

code-documentation

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-hubSkill

tech-documentation

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.

openclawSkill

technical-documentation

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.

SuperkikimSkill

rebuild-documentation

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.

SuperkikimSkill

rebuild-documentation

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.

fdiblenSkill

rseng-documentation

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.

NVIDIASkill

edge-llm-documentation

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.

AndersonAndradSkill

api-documentation

AndersonAndrad/skills/api-documentation/SKILL.md

Author and review API and application documentation for modified contracts using the project's existing documentation tooling, such as Swagger/OpenAPI. Use when endpoints, DTOs, integrations, configuration, or public behavior change. Notify the developer when no documentation tooling exists.