Agent Skill 目录与安装教程 — ClawHub、SkillsMP 与开源 Skill

io.github.upstash/context7/context7-docs

Fetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer. Do not rely on training data for API details, signatures, or configuration options — they are frequently out of date. Prefer this over web search for library documentation.

io.github.ruvnet/ruflo/api-docs

Generate API documentation from source code with JSDoc and OpenAPI support

skillsmp.droidrun-mobilerun-skill-md

Mobilerun documentation reference. Use when users ask about Mobilerun setup, configuration, SDK usage, CLI commands, device setup, agents, architecture, app cards, credentials, tracing, Docker, migration, structured output, or any Mobilerun "how do I..." questions.

io.github.remotion-dev/remotion/writing-docs

Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.

io.github.formbricks/formbricks/nextjs-docs

Local Next.js docs index for this repo (.next-docs/). Use for ANY Next.js-related work in apps/web - routing, layouts, pages, app router, server/client components, server actions, caching, revalidation, metadata, route handlers, proxy/middleware, next.config, images, fonts, error handling, loading states, parallel/intercepting routes, dynamic routes, useRouter/usePathname/useSearchParams, cookies/headers, redirects, deployment, upgrades. Read the relevant .mdx files before implementing or debugging Next.js behavior; do not rely on training data.

io.github.c15t/c15t/writing-docs

Author or edit c15t documentation in docs/**/*.mdx — the source for both the c15t.com site and the docs bundled into published packages. Use when writing guides, integration pages, reference docs, changing package-bundled docs (packages/*/docs, packages/*/AGENTS.md), or fixing docs lint failures.

io.github.mono/SkiaSharp/api-docs

Write AND review XML API documentation for SkiaSharp (ECMA/mdoc XML in the docs submodule). Two modes: (1) ADD docs for new APIs with "To be added." placeholders; (2) REVIEW existing docs by scope for accuracy, freshness, examples, and hygiene. Triggers: "document class", "add XML docs", "write XML documentation", "fill in missing docs", "remove To be added placeholders", "review documentation", "check docs for errors", "fix doc issues", "audit the docs", "review the font docs", "are the examples correct", "update out-of-date docs", any request to add, validate, correct, or expand SkiaSharp API documentation.

io.github.handsontable/handsontable/writing-docs-pages

Use when creating or editing documentation pages in docs/content/guides/ - covers YAML frontmatter, page structure, framework-specific example embedding, writing style, and sidebar registration

io.github.ruvnet/ruflo/agent-docs-api-openapi

Agent skill for docs-api-openapi - invoke with $agent-docs-api-openapi

io.github.omnigent-ai/omnigent/api-docs

Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.

io.github.actualbudget/actual/writing-actual-docs

Use whenever creating, updating, editing, drafting, restructuring, or fixing documentation in the Actual Budget repo — specifically anything under `packages/docs/` (the Docusaurus site published at actualbudget.org/docs) or any change to `.md` / `.mdx` files in that package. Trigger for asks like "add a doc page for X", "update the FAQ", "write a guide for the new feature", "document this setting", "fix the docs about Y", "add a contributing page", or any work on the docs site, even when the user does not explicitly mention style, structure, or conventions. Actual's docs follow strict Docusaurus conventions (front matter, heading levels, image placement and naming, admonition syntax, Title Case, tone of voice, spelling allowlist) and writing them without consulting the project's style guide reliably produces output that fails review and needs to be redone.

io.github.shader-slang/slang/design-docs-incremental-update

Incrementally refresh the LLM-generated design docs under docs/generated/design/. Use when the user asks to update, refresh, or regenerate the generated design documentation after source changes. Runs the three-stage operator loop defined in docs/generated/design/_meta/regenerate.md - (1) regenerate stale docs (Claude), (2) direct the user to run the non-Claude review, (3) apply remediation (Claude) - with explicit confirmation before stages 1 and 3.

io.github.vercel/next.js/update-docs

This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature", "document this feature", "review docs completeness", "add docs for this change", "what documentation is affected", "docs impact", or mentions "docs/", "docs/01-app", "docs/02-pages", "MDX", "documentation update", "API reference", ".mdx files". Provides guided workflow for updating Next.js documentation based on code changes.

io.github.expo/expo/expo-api-docs

Write TSDoc comments for Expo SDK APIs following official conventions. MUST USE when introducing new user-facing TypeScript APIs in expo-* packages - document APIs correctly from the start, not as an afterthought. Also use when improving existing documentation. Covers @platform, @example, @deprecated, @default annotations, third-person declarative style, blockquote notes, and type export patterns for docs generation.

io.github.medusajs/medusa/writing-docs

Writes and updates Medusa documentation MDX files for the book, resources, ui, user-guide, and cloud projects. Use when making documentation changes based on code diffs, adding new pages, updating existing content, or updating component examples. ALWAYS load this skill before modifying any MDX file in www/apps/.

io.github.Fody/Costura/api-docs

Write and review XML API documentation following .NET guidelines. Triggers: "document class", "add XML docs", "write XML documentation", "add triple-slash comments", "review documentation quality", "check docs for errors", "fix doc issues", "fill in missing docs", "remove To be added placeholders", API documentation requests.

io.github.tldraw/tldraw/review-docs

Review and improve documentation with parallel evaluation and iterative improvement loop.

io.github.google-gemini/gemini-cli/docs-writer

Always use this skill when the task involves writing, reviewing, or editing files in the `/docs` directory or any `.md` files in the repository.

io.github.storybookjs/storybook/docs-review

Review, improve, rewrite, author, or plan Storybook documentation in /docs. Use this when asked to review docs, improve a page, rewrite documentation, draft new docs, or advise on docs strategy.

io.github.cursor/plugins/docs-canvas

Render a documentation-style Cursor Canvas that organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references. Use when the user asks for a docs canvas, documentation overview, architecture walkthrough, API reference page, or wants to render structured documentation as an interactive canvas.

io.github.open-edge-platform/anomalib/python-docstrings

Enforces Google-style Python docstrings for Python code

io.github.nukeop/nuclear/writing-docs

Use when writing or editing documentation in packages/docs. Covers Gitbook markdown syntax, special blocks, page structure, and the SUMMARY.md table of contents. Trigger phrases include "write docs", "add documentation", "docs page", "gitbook", "user manual".