Technical Docs agent skills

Technical Docs agent skills indexed by RunLocalModel. 480 indexed; SkillsMP reports 72,891 in this category. This is the stored sample from SkillsMP, not a complete directory.

Back to the Agent Skills browser

• acestep by ace-step. Updated March 9, 2026. Use ACE-Step API to generate music, edit songs, and remix music. Supports text-to-music, lyrics generation, audio continuation, and audio repainting. Use this skill when users mention generating music, creating songs, music production, remix, or audio continuation.
• acquire-codebase-knowledge by github. Updated September 16, 2026. Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
• add-ir-instruction by facebook. Updated February 19, 2026. Guide for adding a new IR instruction to the Hermes compiler. Use when the user asks to add, create, or define a new IR instruction (Inst/Instruction) in the Hermes intermediate representation. Covers all required files and the patterns for each.
• add-reference by juice-shop. Updated April 23, 2026. Instructions for adding new blog posts, talks, or other references to REFERENCES.md
• add-solution by juice-shop. Updated April 23, 2026. Instructions for adding new hacking guides, videos, or tools to SOLUTIONS.md
• add-tools by simstudioai. Updated September 25, 2026. Create tool configurations for a Sim integration by reading API docs
• add-vulhub-env by vulhub. Updated June 13, 2026. Guide for adding new vulnerability reproduction environments to the Vulhub project. Use this skill whenever the user wants to add a new CVE environment, create a vulnerability Docker lab, contribute a new vulnerability to vulhub, write vulnerability documentation for vulhub, or create docker-compose.yml / Dockerfile / README for a vulnerability environment. Also trigger when the user mentions a specific CVE they want to add, asks about vulhub contribution workflow, or wants to set up a reproducible exploit environment.
• adev-writing-guide by angular. Updated September 22, 2026. Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. You MUST use this skill any time you plan to create, edit, or review documentation files in `adev/` or `adev/src/content`.
• adk-sample-creator by google. Updated August 31, 2026. Author or rework a runnable example under `examples/` in the ADK Go repository — the directory, `main.go`, the README with its Mermaid diagram and real transcript, and the index row. Use when adding a sample for a feature (workflow graph, tool, registry client, model backend, server), when asked to "add an example" for something, or when bringing an existing example up to the repo's standard.
• adk-unit-design by google. Updated August 13, 2026. Writes an as-built architecture document for one ADK code unit — purpose, execution flow, data flow, cross-class dependencies, extension points, and the parts that must not change — to `docs/design/{topic}/{unit}/index.md`. It describes the code as implemented, not a proposed design, and its reader is a developer about to change or extend that unit. Use when asked to "write a design doc for {file}", "document the architecture of {class}", "document the extension points of {unit}", or after adding a core class, node type, or plugin base. Don't use for documentation aimed at developers who only call the unit from their own application — that is a usage guide with runnable examples under `docs/guides/` (use `adk-unit-guide`). Don't use to answer a framework-wide architecture question (use `adk-architecture`).
• adk-unit-guide by google. Updated September 23, 2026. Writes a hands-on developer guide for one ADK code unit — a minimal runnable example, how it works, a configuration-option table, advanced uses, limitations, and links to related samples — to `docs/guides/{topic}/{unit}/index.md`, then lists it in the index at `docs/guides/README.md`. Its reader is a developer calling the unit from their own application, at more depth than the published adk.dev documentation carries. Use when asked to "write a unit guide for {class}", "document how to use {feature}", "add a guide for {file}", or after shipping a user-facing class, node, or plugin. Don't use for internals documentation aimed at someone changing or extending the unit — that is a design document under `docs/design/` (use `adk-unit-design`). Don't use to write a runnable sample under `contributing/samples/` (use `adk-sample-creator`).
• adopting-generated-api-types by PostHog. Updated April 23, 2026. Use when migrating frontend code from manual API client calls (`api.get`, `api.create`, `api.surveys.get`, `api.dashboards.list`, `new ApiRequest()`) and handwritten TypeScript interfaces to generated API functions and types. Triggers on files importing from `lib/api`, files with `api.get<`, `api.create<`, `api.<entity>.<method>`, manual interface definitions that duplicate backend serializers, or any frontend file that constructs API URLs by hand. Covers the full replacement workflow — finding the generated equivalent, swapping imports, adapting call sites, and removing dead manual types.
• agui-dotnet-sdk-docs by ag-ui-protocol. Updated June 21, 2026. Author, update, and validate the AG-UI .NET SDK documentation pages on the docs.ag-ui.com Mintlify site (under docs/). USE FOR: adding or editing a ".NET SDK" docs page (sdk/dotnet/**/*.mdx), wiring it into the docs.json ".NET" nav group and global anchor, running the docs site locally with mintlify dev, previewing/validating rendered .NET pages, checking the .NET sidebar anchor/icon. DO NOT USE FOR: in-repo dotnet markdown such as sdks/dotnet/AGENTS.md or docs/architecture.md (use agui-dotnet-agents-sync); TypeScript/Python docs pages; product code, tests, or wire types.
• ai-context by meteor. Updated February 6, 2026. Use when creating, updating, or maintaining AI documentation files (AGENTS.md, CLAUDE.md, skills). Covers file structure, conventions, and guidelines for evolving AI context.
• ai-docs by pingdotgg. Updated September 18, 2026. AI documentation. Use when editing ai-docs/src or regenerating LLMS.md.
• aip-user-stories by apache. Updated June 7, 2026. Generate verified recipe playbooks from AIPs with PR implementations (post mode), or speculative user stories from AIPs without implementations (pre mode). Use when the user provides an AIP URL or AIP content, optionally with PR URLs and file paths.
• airflow-java-sdk by apache. Updated June 22, 2026. Guide for contributing to the Airflow Java SDK (AIP-108). Use this skill whenever a contributor is working in the `java-sdk/` directory or on the Java coordinator in `task-sdk/src/airflow/sdk/coordinators/java/` — whether they want to add a feature, write tests, fix a bug, understand the architecture, or prepare a PR. Trigger on phrases like "Java SDK", "JavaCoordinator", "java-sdk", "annotation processor", "Builder.Task", "BundleBuilder", or anything about running JVM tasks in Airflow.
• airflow-new-sdk by apache. Updated June 22, 2026. Guide for implementing a brand-new language SDK for Airflow (AIP-108). Use this skill when a contributor wants to add support for a new programming language — designing the Python coordinator, implementing the wire protocol in the target language, writing the bundle format, and structuring the PR. Trigger on phrases like "new language SDK", "new SDK", "add support for [language]", "implement coordinator for", "SubprocessCoordinator", "BaseCoordinator", "new runtime", "AFBNDL01", "supervisor schema", or anything about bringing a new language into the Airflow executor ecosystem.
• antd-component-lookup by ant-design. Updated May 13, 2026. Look up Ant Design React component documentation, props, and usage examples. Use when working with Ant Design (antd) components and needing API details, default values, or usage patterns.
• api-docs by omnigent-ai. Updated June 23, 2026. 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.
• api-docs by ruvnet. Updated July 17, 2026. Generate API documentation from source code with JSDoc and OpenAPI support
• api-documentation-generator by davila7. Updated January 25, 2026. Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
• api-proposal by dotnet. Updated September 12, 2026. Create prototype-backed API proposals for dotnet/runtime. Use when asked to draft an API proposal, write an api-suggestion issue, refine a vague API idea into a complete proposal, or improve a proposal marked api-needs-work. Covers the full pipeline from research through prototyping, ref source generation, and publishing. DO NOT USE FOR bug fixes, code review, performance benchmarking, or internal API changes that don't affect public surface area.
• api-review by dotnet. Updated September 1, 2026. Author and file a separate ASP.NET Core API review issue from an originating issue and an implementation pull request or commits. USE FOR writing API review issues, preparing api-ready-for-review proposals, filling API proposal templates, creating API review descriptions from issues and code changes, "fill out the API review", "prepare API review", or opening a pull request that changes public API. DO NOT USE FOR reviewing API design decisions, approving APIs, implementing APIs, or general code review.
• architecture-decision by Donchitos. Updated September 29, 2026. Create an ADR documenting a technical decision: context, alternatives considered, consequences.
• architecture-decision-record-maintainer-skill by architecture-decision-record. Updated September 5, 2026. Use when working ON the joelparkerhenderson/architecture-decision-record repository itself (this repo) — adding or editing a decision-record template, example, tool/guardrail link, or translation; reviewing a contributor's PR against it; or keeping README.md and locales/en/ in sync. Not for writing an ADR for some other project — use architecture-decision-record-skill for that.
• architecture-decision-records by affaan-m. Updated September 27, 2026. Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README. Use when the user says 'record this decision' or 'ADR this', chooses between frameworks or databases, discusses trade-offs, or asks why the codebase is shaped this way.
• architecture-decision-records by wshobson. Updated March 7, 2026. Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
• ask-the-docs by supabase. Updated September 22, 2026. Answer questions about the Supabase docs app (apps/docs) using documented architecture, build pipeline, and review-pattern notes, and apply feature-design principles (codebase reuse, coding minimalism) when proposing or critiquing changes. Use when the user asks "how does X work in the docs app?", "where does Y live?", "is this approach OK for the docs app?", or before writing non-trivial changes under apps/docs/ — especially anything touching the MDX pipeline, markdown generation, content components, federated docs, or contributor-facing authoring patterns. Can answer architecture questions with Mermaid diagrams when helpful.
• astro-developer by withastro. Updated August 13, 2026. Comprehensive guide for developing in the Astro monorepo. Covers architecture, debugging, testing, and critical constraints. Use when working on features, fixes, tests, or understanding the codebase structure.
• authoring-docs by goreleaser. Updated June 18, 2026. Use when writing or editing GoReleaser documentation under www/content (Hugo site) — customization reference pages, YAML config examples, "Since vX.Y" / Pro badges, callouts, or documenting a feature that is merged but not yet released.
• backend by redis. Updated May 21, 2026. NestJS backend development patterns for the RedisInsight API: module structure, services, controllers, DTOs, dependency injection, and error handling. Use when editing any file under redisinsight/api/**, writing or modifying NestJS modules, controllers, services, DTOs, providers, or when the user mentions the backend, API, or NestJS.
• backend-to-frontend-handoff-docs by davila7. Updated January 25, 2026. Create API handoff documentation for frontend developers. Use when backend work is complete and needs to be documented for frontend integration, or user says 'create handoff', 'document API', 'frontend handoff', or 'API documentation'.
• backport-docs by ray-project. Updated September 1, 2026. Cherry-pick documentation changes from master onto a release branch so they appear on the docs.ray.io /latest build
• backstage-release-notes by backstage. Updated September 8, 2026. Generate release notes for a new Backstage version from changesets. Use when writing or drafting release notes, or when preparing a Backstage release.
• beads-docs by gastownhall. Updated July 18, 2026. Project conventions for writing, editing, restructuring, or reviewing the beads user documentation — the Mintlify site under docs/. Use this whenever you touch anything in docs/ (pages, concept docs, reference, integration guides, recovery runbooks, diagrams, docs.json navigation) or write/edit prose about beads, even when the request is just "fix the docs", "write a docs page", "the docs are wrong/confusing", "rename X across the docs", or an edit to a file under docs/. It defines the canonical concept model (bead → dependencies → ready work; formula → proto → molecule/wisp; gates; Dolt sync and federation), required terminology, the prose/emphasis/diagram conventions, the rule that generated docs are edited at their source, and the gates to run before docs work is done.
• blog-draft by luongnv89. Updated August 4, 2026. Draft a blog post from ideas and resources. Use when users want to write a blog post, create content from research, or draft articles. Guides through research, brainstorming, outlining, and iterative drafting with version control.
• blog-draft by luongnv89. Updated April 6, 2026. Soạn thảo bài đăng blog từ ý tưởng và tài nguyên. Sử dụng khi người dùng muốn viết bài blog, tạo nội dung từ nghiên cứu, hoặc soạn thảo bài viết. Hướng dẫn qua nghiên cứu, động não, lập dàn ý, và soạn thảo lặp lại với kiểm soát phiên bản.
• blog-draft by luongnv89. Updated April 6, 2026. 根据想法和资料撰写博客草稿。适用于用户想写博客、基于研究创建内容，或起草文章的场景。流程会引导你完成调研、头脑风暴、提纲编写和带版本控制的迭代撰写。
• bmad-architecture by bmad-code-org. Updated September 25, 2026. Work out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a spec, a raw idea, or an existing codebase. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design"
• bmad-build by bmad-code-org. Updated September 25, 2026. Turns implementation work into working code, reviewed and verified. Use when the user delegates a feature, story, bug fix, or meaningful change; a bare story or issue link counts. Skip obvious, low-risk mechanical maintenance such as small ignore-file, typo-only, formatting-only, or configuration-hygiene edits. Explicit BMAD requests always qualify. Do not volunteer for user-directed interactive edits or version-control operations that only record existing work.
• bmad-prd by bmad-code-org. Updated September 25, 2026. Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD
• brand-voice by affaan-m. Updated May 17, 2026. 実際のポスト、エッセイ、ローンチノート、ドキュメント、またはサイトコピーからソース派生の執筆スタイルプロファイルを構築し、コンテンツ、アウトリーチ、ソーシャルワークフロー全体でそのプロファイルを再利用します。ユーザーが一般的なAI執筆トロープなしで声の一貫性を望む場合に使用します。
• breakdown-epic-pm by github. Updated February 24, 2026. Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.
• breaking-change-doc by dotnet. Updated September 12, 2026. Generate breaking change documentation for merged dotnet/runtime PRs. USE FOR: creating breaking change docs, "document this breaking change", "write breaking change issue for PR #NNNNN", processing PRs labeled needs-breaking-change-doc-created. DO NOT USE FOR: general code review (use code-review skill), bug fixes, API proposals (use api-proposal skill).
• bright-data-best-practices by davila7. Updated March 13, 2026. Build production-ready Bright Data integrations with best practices baked in. Reference documentation for developers using coding assistants (Claude Code, Cursor, etc.) to implement web scraping, search, browser automation, and structured data extraction. Covers Web Unlocker API, SERP API, Web Scraper API, and Browser API (Scraping Browser).
• build-guide by anthropics. Updated May 11, 2026. Help a clinic supervisor author a practice-area guide that configures how student-facing skills behave — intake questions, pedagogy posture (assist / guide / teach), review gates, cross-plugin checks, and local rules. Use when a supervising attorney wants to build or revise a per-practice-area guide, tune how the clinic skills behave for their clinic type, or set their teaching philosophy as plugin configuration.
• build-tools-bump-gradle-api by JetBrains. Updated August 25, 2026. Bumps the Gradle API version that Kotlin Gradle plugins are compiled against in the Kotlin compiler repository. Use this skill whenever the user asks to upgrade, bump, or update the Gradle compile API version, Gradle plugin API version, or GRADLE_COMMON_COMPILE_API_VERSION. Also use it when the user says something like "update KGP to compile against Gradle X.Y.Z" or "bump Gradle API to X.Y" or "we need to support Gradle X.Y in the plugin".
• ce-skill-work by EveryInc. Updated September 10, 2026. Applies this repository's skill-authoring standard as a procedure. Use for any change to, or judgment about, a file under skills/** — a SKILL.md, a reference, a persona prompt, a bundled script's instructions: creating a skill, editing one, reviewing a skill change, or acting on review feedback (human or bot) about one. Not for src/, tests/, or scripts/ code.
• changesets by primer. Updated September 18, 2026. Use when a pull request changes a package's public API. Covers affected packages, semantic version impact, file format, and user-focused release notes.
• chatgpt-apps by openai. Updated March 24, 2026. Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.
• chromium-docs by chromium. Updated August 13, 2026. Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides. Use when the user asks to find, locate, browse, or learn from Chromium docs about architecture, APIs, testing, GPU, networking, or other Chromium topics.
• claude-automation-recommender by anthropics. Updated May 28, 2026. Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
• claude-automation-recommender by CherryHQ. Updated August 4, 2026. Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
• claude-code-guide by 2025Emma. Updated December 16, 2025. Claude Code 高级开发指南 - 全面的中文教程，涵盖工具使用、REPL 环境、开发工作流、MCP 集成、高级模式和最佳实践。适合学习 Claude Code 的高级功能和开发技巧。
• claude-cookbooks by 2025Emma. Updated December 16, 2025. Claude AI cookbooks - code examples, tutorials, and best practices for using Claude API. Use when learning Claude API integration, building Claude-powered applications, or exploring Claude capabilities.
• cli by lobehub. Updated September 26, 2026. LobeHub CLI (@lobehub/cli) development guide — commands, subcommands, architecture.
• cli-anything by HKUDS. Updated June 8, 2026. Use when the user wants Codex to build, refine, test, validate, or list CLI-Anything harnesses for GUI applications or source repositories. Adapts the full CLI-Anything methodology to Codex without changing the generated Python harness format.
• cli-anything-mermaid by HKUDS. Updated April 18, 2026. Command-line interface for Mermaid Live Editor - Create, edit, and render Mermaid diagrams via stateful project files and mermaid.ink renderer URLs. Designed for AI agents and power users who need to generate flowcharts, sequence diagrams, and other visualizations without a GUI.
• cli-creator by openai. Updated April 10, 2026. Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a companion skill.
• clinical-reports by davila7. Updated December 20, 2025. Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.
• clojure-write by metabase. Updated September 11, 2026. Guide Clojure and ClojureScript development using REPL-driven workflow, coding conventions, and best practices. Use when writing, developing, or refactoring Clojure/ClojureScript code.
• clonedeps by alvinunreal. Updated July 13, 2026. Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos locally readable. Do not use for ordinary API/docs questions where @librarian is enough.
• code-documentation by bytedance. Updated April 5, 2026. Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.
• code-documenter by Jeffallan. Updated April 29, 2026. Generates, formats, and validates technical documentation — including docstrings, OpenAPI/Swagger specs, JSDoc annotations, doc portals, and user guides. Use when adding docstrings to functions or classes, creating API documentation, building documentation sites, or writing tutorials and user guides. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, getting started guides.
• code-mate-opencode by CherryHQ. Updated August 27, 2026. Runs OpenCode non-interactively for repository analysis and coding tasks. Use when the user asks to delegate work to OpenCode or compare OpenCode with another coding agent.
• code-wiki by NousResearch. Updated August 30, 2026. Generate wiki docs + Mermaid diagrams for any codebase.
• codebase-onboarding by affaan-m. Updated March 22, 2026. 分析一个陌生的代码库，并生成一个结构化的入门指南，包括架构图、关键入口点、规范和一个起始的CLAUDE.md文件。适用于加入新项目或首次在代码仓库中设置Claude Code时。
• codebase-onboarding by affaan-m. Updated June 11, 2026. Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.
• codebase-onboarding by alirezarezvani. Updated May 14, 2026. Analyze a codebase and generate onboarding documentation for engineers, tech leads, and contractors. Fast fact-gathering and repeatable onboarding outputs. Use when onboarding a new engineer, writing architecture-overview docs for a new project, or producing tech-lead briefings for unfamiliar repos.
• codegen by vercel-labs. Updated March 7, 2026. Code generation utilities for json-render. Use when generating code from UI specs, building custom code exporters, traversing specs, or serializing props for @json-render/codegen.
• codex by NousResearch. Updated September 19, 2026. Delegate coding to OpenAI Codex CLI (features, PRs).
• codex-cli by kortix-ai. Updated September 25, 2026. Drive OpenAI's Codex CLI (`codex exec`) as a non-interactive coding sub-agent from inside Claude Code. Load WHENEVER you want to delegate a coding/analysis/refactor task to Codex, get a second opinion / adversarial review from another model, fan out parallel agents across files or worktrees, or run a long mechanical job while you stay the planner. Covers the exact `codex exec` flags, sandbox tiers, output capture, JSON/schema modes, session resume, parallel fan-out, and the mandatory "delegate → capture → independently verify, never trust the self-report" supervision loop.
• codex-result-handling by openai. Updated March 30, 2026. Internal guidance for presenting Codex helper output back to the user
• coding-agent by mastra-ai. Updated May 27, 2026. Authoring playbook for building agents that write, edit, review, or refactor code. Use this when the user asks for an agent that writes scripts, generates code, reviews pull requests, refactors a codebase, fixes bugs, implements features, writes tests, or works with programming languages such as Python, TypeScript, JavaScript, Go, Rust, SQL, or shell.
• coding-agent by openclaw. Updated July 29, 2026. Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
• coingecko by 2025Emma. Updated December 16, 2025. CoinGecko API documentation - cryptocurrency market data API, price feeds, market cap, volume, historical data. Use when integrating CoinGecko API, building crypto price trackers, or accessing cryptocurrency market data.
• command-development by anthropics. Updated November 17, 2025. This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
• command-development by anthropics. Updated March 17, 2026. This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
• commit-archaeologist by Shubhamsaboo. Updated July 22, 2026. Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite, refactor, or risky edit. Runs entirely locally.
• communication-style by openchamber. Updated August 27, 2026. Load when writing or editing any human-facing text — documentation, UI copy, PR/issue comments, release notes, READMEs — to strip AI-generated patterns and keep a human voice.
• component-context-generator by PrestaShop. Updated May 12, 2026. Generates a CONTEXT.md file for a PrestaShop shared component inside the `.ai/Component/` folder. Trigger this skill when the user asks to "generate a context for [Component]", "document the [X] component", "fill in the CONTEXT.md for [Component]", or when working inside `.ai/Component/` directories. Components live under `src/Core/{Name}/` and/or `src/Adapter/{Name}/` — they are shared infrastructure, not business domains. Examples: Grid, Form, Hook, CQRS, Translation, Router.
• concept-workflow by leonardomso. Updated January 6, 2026. End-to-end workflow for creating complete JavaScript concept documentation, orchestrating all skills from research to final review
• connector-standards by open-metadata. Updated March 9, 2026. Load all OpenMetadata connector development standards into context. Use before building or reviewing connectors to ensure consistent patterns.
• context-driven-development by wshobson. Updated September 28, 2026. Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a `conductor/` directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when setting up a project, creating or updating product docs, managing a tech stack file, defining development workflows, tracking work units, onboarding to an existing codebase, or running project scaffolding.
• context7-auto-research by davila7. Updated January 25, 2026. Automatically fetch latest library/framework documentation for Claude Code via Context7 API
• context7-cli by upstash. Updated August 31, 2026. Use the ctx7 CLI to fetch library documentation, manage AI coding skills, and configure Context7 MCP. Activate when the user mentions "ctx7" or "context7", needs current docs for any library, wants to install/search/generate skills, or needs to set up Context7 for their AI coding agent.
• context7-mcp by upstash. Updated August 9, 2026. Fetches current, version-specific library documentation and code examples through the Context7 MCP server. Use whenever the user asks about a library, framework, SDK, API, CLI tool, or cloud service, including API syntax, configuration, setup instructions, version migration, CLI usage, and library-specific debugging. Use when generating code that calls a third-party library, and when the user names a version such as Next.js 15 or React 19. Use even for well-known libraries like React, Vue, Next.js, Prisma, Supabase, Express, Tailwind, Django, and Spring Boot, because training data may not reflect recent changes. Prefer this over web search for library documentation. Do not use it for refactoring, writing scripts from scratch, debugging business logic, code review, or general programming concepts, or when the user has already supplied the relevant documentation.
• contextual-commit by yamadashy. Updated May 24, 2026. Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
• contribute by mindfold-ai. Updated April 23, 2026. Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs across both the Trellis main repo and docs repo. Use when someone wants to add a new spec template, add a new skill to the marketplace, add or update documentation pages, or submit a PR to this project.
• contribute by mindfold-ai. Updated March 20, 2026. Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs across both the Trellis main repo and docs repo. Use when someone wants to add a new spec template, add a new skill to the marketplace, add or update documentation pages, or submit a PR to this project.
• contributing by apache. Updated September 8, 2026. Guides the contribution workflow for Apache Beam, including creating PRs, issue management, code review process, release cycles, and rigorous evaluation rules for high-risk core component changes. Use when contributing code, creating PRs, or modifying core Beam components.
• conventions by meteor. Updated September 4, 2026. Use when writing new packages, adding CLI commands, creating build plugins, or following Meteor code patterns. Covers package.js structure, file naming, and common code patterns.
• convex-docs by openclaw. Updated August 5, 2026. Pull version-current Convex docs for the version this project uses — pin the installed version, fetch page-as-markdown or check node_modules types, freshness hierarchy — instead of writing a possibly-stale API from memory.
• copilot-instructions-blueprint-generator by github. Updated February 24, 2026. Technology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns and avoiding assumptions.
• craft-documentation by onyx-dot-app. Updated August 17, 2026. Answer questions about how Onyx and Onyx Craft work using the official documentation at docs.onyx.app. Use when the user asks what Craft can do, how a feature works, how to set up skills or apps, or how to deploy, configure, or administer Onyx.
• crafting-effective-readmes by davila7. Updated January 25, 2026. Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
• create-cowork-plugin by anthropics. Updated March 18, 2026. Guide users through creating a new plugin from scratch in a cowork session. Use when users want to create a plugin, build a plugin, make a new plugin, develop a plugin, scaffold a plugin, start a plugin from scratch, or design a plugin. This skill requires Cowork mode with access to the outputs directory for delivering the final .plugin file.
• create-design-md by ibelick. Updated July 21, 2026. Create or update a DESIGN.md from an existing product repository or public website. Use when asked to document an interface's design language, reconstruct its visual system, extract design tokens and guidance from current evidence, or give coding agents persistent UI context. Do not modify product source or promote accidental implementation patterns into design decisions.
• create-documentation by documenso. Updated March 9, 2026. Generate markdown documentation for a module or feature
• create-instructions by microsoft. Updated April 8, 2026. Create an instructions file (.instructions.md) for a project rule or convention.
• create-llms by github. Updated February 24, 2026. Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/
• create-plan by davila7. Updated December 29, 2025. Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
• create-planning-document by Nuitka. Updated August 9, 2026. Create a Nuitka planning document under `.planning/` from the standard template. Use when the user asks to create, draft, or start a planning document, and wait for explicit user authorization before implementation.
• create-plugin by different-ai. Updated June 2, 2026. Create an OpenCode plugin for OpenWork. Scaffolds the plugin file with the correct API shape, tool definitions, and hook registration. Use when the user asks to 'create a plugin', 'write a plugin', or 'make a plugin that does X'.
• create-pr by moeru-ai. Updated September 23, 2026. Prepare and create an AIRI pull request with verifiable change context, architecture evidence, and required visual evidence. Use when Codex must open, create, publish, or prepare a PR from the current branch.
• create-pr by ueberdosis. Updated September 17, 2026. Create a pull request with a clear, concise description that follows the repository's current PR template. Use when asked to open a PR or prepare its title and description.
• create-readme by github. Updated February 24, 2026. Create a README.md file for the project
• create-rfc by NVIDIA. Updated September 2, 2026. Create OpenShell RFC proposals in rfc/ from a design request. Use when the user asks to write, draft, start, create, or update an RFC, Request for Comments, architecture proposal, API proposal, process proposal, or cross-cutting design proposal that should follow the OpenShell RFC process and template.
• create-tldr-page by github. Updated February 24, 2026. Create a tldr page from documentation URLs and command examples, requiring both URL and command name.
• create-verification-skill by cursor. Updated July 30, 2026. Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
• create-video by calesthio. Updated March 29, 2026. Create videos from a text prompt using HeyGen's Video Agent. Use when: (1) Creating a video from a description or idea, (2) Generating explainer, demo, or marketing videos from a prompt, (3) Making a video without specifying exact avatars, voices, or scenes, (4) Quick video prototyping or drafts, (5) One-shot prompt-to-video generation, (6) User says "make me a video" or "create a video about X".
• creating-docs-examples by handsontable. Updated June 10, 2026. Use when creating code examples for documentation pages - JavaScript, TypeScript, React, Angular, and Vue variants with proper imports, registration, and license key
• credential-recipe-research by n8n-io. Updated September 28, 2026. Lookup procedure for Simplified Custom Auth recipe fields — sources the auth template, the key-issuing docsUrl and an auth-rejecting testUrl from the provider's real documentation instead of memory. Load before composing credentialHints for a service without a dedicated credential type (the post-build-flow setup step), or when asked to fix a recipe whose template, key page or test endpoint is wrong.
• csharp-docs by github. Updated February 24, 2026. Ensure that C# types are documented with XML comments and follow best practices for documentation.
• cursor-sdk by cursor. Updated April 28, 2026. Guide users building apps, scripts, CI pipelines, or automations on top of the Cursor TypeScript SDK (`@cursor/sdk`). Use this skill whenever the user mentions integrating, installing, or writing code against the Cursor SDK; whenever they say `Agent.create`, `Agent.prompt`, `Agent.resume`, `agent.send`, `run.stream`, `CursorAgentError`, or `@cursor/sdk`; whenever they ask to run Cursor agents programmatically from a script, CI/CD pipeline, GitHub Action, backend service, or any other code that isn't the Cursor IDE itself; and whenever they want to pick between local and cloud runtime, configure MCP servers for an SDK agent, or handle streaming, cancellation, or errors from an SDK agent. Also trigger when a user is wiring Cursor into an automation, writing a bot that runs Cursor, or porting REST `/v1/agents` calls to the SDK, even if they don't explicitly name the package. Use this eagerly rather than answering from memory; the SDK surface evolves and this skill plus its references are the source of truth for
• dagger-design-proposals by dagger. Updated September 18, 2026. Write design proposals for Dagger features. Use when asked to draft, review, or iterate on Dagger design documents, RFCs, or proposals.
• dagster-docs by dagster-io. Updated March 24, 2026. Expert guidance for writing documentation for the Dagster docs website. ALWAYS use before creating or updating documentation in the docs directory.
• dang-dagger-modules by dagger. Updated September 18, 2026. Authoring Dagger modules in Dang — dagger.json setup, the main type & constructor, what becomes module API, self-calls (supported; annotate returns as Dagger.<Type>!), dependencies, enums/interfaces/scalars, directives (@check, @cache, @defaultPath, @agent), Workspace args, and caching pitfalls. Use when writing or reviewing a Dagger module implemented in Dang.
• define-security-policy by openai. Updated September 8, 2026. Define, review, or update SECURITY.md guidance for a repository or component. Use when the user wants to clarify what Codex Security should review, what is out of scope, which security properties must hold, or whether existing guidance still matches the code.
• demo-page by handsontable. Updated May 13, 2026. Use when creating a demo or test page for manual testing of Handsontable. Trigger when the user asks to create a demo, test page, repro page, reproduction case, manual test, or wants to verify a bug fix or feature visually. Also trigger when the user mentions dev-generated.html, dev-pr.html, dev-latest.html, dev.html, or wants to compare behavior between a released version and a local build. Use this for any PR that needs a manual testing artifact.
• deprecate-api by remotion-dev. Updated July 29, 2026. Reference for how deprecation of public Remotion APIs is represented in TypeScript source and documentation. Use when adding, reviewing, or discussing a deprecation of a function, component, hook, type, prop, option, or other public API that remains available.
• design by asgeirtj. Updated September 27, 2026. Create a design canvas - a multi-artboard visual design published as an Artifact that runs Claude Design's canvas editor (an early preview of Claude Design inside Claude Code). You DRAFT the design as .dc.html artboards laid out on one pan/zoom canvas; where saving is enabled for the user's account they refine every element visually (click-to-select, a properties panel, inline text editing, undo/redo) and Save publishes a new version for everyone, otherwise they get a view-and-export (PNG/PDF) preview of your draft. Good for UI mockups and screen flows, landing pages, marketing and social graphics, and print pieces - posters, flyers, brochures as single-page artboards; memos and reports as one flowing artboard. Use when someone wants a design, mockup, wireframe, UI or screen design, landing page, poster, flyer, brochure, banner, card, one-pager, or any visual layout they would rather tweak by hand than in code. Only for CREATING or re-seeding a canvas; an existing one is edited in its published Artifact.
• design-handoff by anthropics. Updated March 13, 2026. Generate developer handoff specs from a design. Use when a design is ready for engineering and needs a spec sheet covering layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details.
• dev by microsoft. Updated September 18, 2026. Development workflows for the playwright-cli repository. Use when the user asks about rolling dependencies, releasing, or other repo maintenance tasks.
• dev-docs-generate by crmeb. Updated March 23, 2026. 开发文档生成规范，快速生成开发文档，自动放到docs目录下，方便技术快速了解项目，能快速入手开发
• dev-story by Donchitos. Updated September 29, 2026. Implement a story: ADR guidelines, right programmer agent, code plus test. Then /story-done (/story-readiness before, /code-review after, at standard/full).
• develop-extension by OpenBB-finance. Updated March 18, 2026. This is a complete guide for creating a new OpenBB Platform extension from scratch. Follow every phase in order. When the user says "build me an application that does X", use this guide to scaffold, implement, install, and verify the extension.
• developing-genkit-dart by google. Updated September 18, 2026. Generates code and provides documentation for the Genkit Dart SDK. Use when the user asks to build AI agents in Dart, use Genkit flows, or integrate LLMs into Dart/Flutter applications.
• development by ryoppippi. Updated June 8, 2026. Guides ccusage monorepo development. Use when editing packages, docs, shared configuration, bundled CLI packaging, dependencies, exports, or validation commands.
• doc-author by InsForge. Updated May 21, 2026. Write, edit, and maintain documentation. Use for collaborative drafting, autonomous writing, or improving existing docs. Defaults to collaborative mode where the human makes final decisions. Built by Mintlify.
• doc-check by coder. Updated September 26, 2026. Checks if code changes require documentation updates. Use when reviewing a PR or diff for missing, stale, or incorrect docs under docs/; to write or restructure docs, use write-docs.
• doc-coauthoring by anthropics. Updated December 4, 2025. Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
• doc-comments by microsoft. Updated September 18, 2026. Update doc comments
• doc-generator by luongnv89. Updated August 4, 2026. Generate comprehensive, accurate API documentation from source code. Use when creating or updating API documentation, generating OpenAPI specs, or when users mention API docs, endpoints, or documentation.
• doc-generator by luongnv89. Updated August 4, 2026. Генерація вичерпної, точної документації API з вихідного коду. Використовуйте при створенні або оновленні документації API, генерації специфікацій OpenAPI, або коли користувачі згадують документацію API, ендпоінти чи документацію.
• doc-generator by luongnv89. Updated August 4, 2026. 从源代码生成全面且准确的 API 文档。适用于创建或更新 API 文档、生成 OpenAPI 规范，或在用户提到 API 文档、端点或说明时使用。
• docs by InsForge. Updated July 15, 2026. Use this skill when contributing to InsForge's product documentation in this repository. This is for maintainers editing public docs in `docs/core-concepts`, agent docs in `.agents/docs`, SDK integration guides in `docs/sdks`, and OpenAPI specs in `openapi`.
• docs by remotion-dev. Updated July 9, 2026. Start the Remotion docs site and open it in the Codex browser. Use when the user invokes /docs or $docs, asks to launch the local documentation site, or wants to preview docs changes in Docusaurus.
• docs-audit by mastra-ai. Updated August 26, 2026. Autonomous, report-only documentation review for Mastra docs. Use when auditing changed docs against source, validating contextual code examples or API coverage, checking canonical mastra-docs guidance, or running narrow deterministic checks.
• docs-canvas by cursor. Updated April 15, 2026. 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.
• docs-components by reactjs. Updated January 30, 2026. Comprehensive MDX component patterns (Note, Pitfall, DeepDive, Recipes, etc.) for all documentation types. Authoritative source for component usage, examples, and heading conventions.
• docs-creator by udecode. Updated June 15, 2026. Create or update Plate docs with conversational voice, lane-aware structure, explicit ownership, and code-backed accuracy. This is the source of truth for Plate docs style and workflow. Use for plugin pages, guides, install docs, serialization docs, API docs, and specs — anywhere both humans and agents need a clear, readable source of truth.
• docs-decisions by ComposioHQ. Updated June 26, 2026. Work on Composio documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance. Use for files under docs/, documentation workflows, or requests to record or update a docs decision. Do not use for SDK runtime changes unless docs are the main deliverable.
• docs-generator by zhaoxuya520. Updated August 12, 2026. Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.
• docs-guide by dagger. Updated September 18, 2026. Author or review a platform guide in docs/current_docs/getting-started/platform-guides ("Daggerize a Go Project", Go + Compose, TypeScript + Playwright, and similar). Use when asked to write, extend, or review a guide that takes a whole project type from installing an official module to every Check passing in a runtime the project controls.
• docs-learn-pr-preview by netdata. Updated September 12, 2026. Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge. Do not trigger for ordinary docs edits unless the user asks for a local Learn preview.
• docs-page by nexu-io. Updated July 27, 2026. A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".
• docs-page by nexu-io. Updated August 18, 2026. A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".
• docs-review by metabase. Updated December 18, 2025. Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
• docs-review by storybookjs. Updated September 13, 2026. 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.
• docs-reviewer by strands-agents. Updated June 15, 2026. Review documentation drafts for voice consistency, structure, and terminology before PR submission. Use after completing a draft, when checking if docs are ready to ship, or automatically after docs-writer produces output. Also triggers on "review this draft", "check my docs", "is this ready to ship", "review before merging".
• docs-sandpack by reactjs. Updated January 30, 2026. Use when adding interactive code examples to React docs.
• docs-search by davila7. Updated February 23, 2026. Search auto-generated codebase documentation for function signatures, API docs, class definitions, and code comments. Use when the user asks to "search docs", "find documentation", "look up a function", "check the API", or before implementing changes to verify correct signatures and patterns.
• docs-style by continuedev. Updated February 13, 2026. Style guidelines for writing and updating documentation. Use when writing new docs, updating existing docs, or reviewing docs for quality.
• docs-style by Infisical. Updated September 23, 2026. Write, edit, and review Infisical documentation to the house style guide. Use whenever creating or changing any file under docs/ (.mdx pages, snippets, docs.json navigation), when asked to document a feature, write or update a guide, or review a docs diff or pull request. Covers running the Vale linter and the sentence-level review that Vale can't do.
• docs-sync by fossasia. Updated June 20, 2026. Keep API and behavior documentation aligned across README, contribution docs, and AI instructions
• docs-sync by redis. Updated July 1, 2026. Keep ioredis documentation synchronized with code behavior. Use when an agent changes public APIs, options, Redis command support, examples, generated typings, connection behavior, Cluster/Sentinel behavior, Pub/Sub, pipelines, transactions, scan streams, reconnect behavior, TypeScript usage, or release-facing behavior that may require README or docs updates.
• docs-sync-audit by github. Updated September 7, 2026. Run a read-only documentation drift audit for a feature, PR, branch, release, API, configuration change, workflow, CLI, package, or repository area. Use when the user asks whether docs are stale, missing, inconsistent with code, or need updates after code changes. Checks README files, setup guides, API docs, env docs, changelogs, examples, comments, generated docs, and user-facing instructions. This is not a general code review; it compares what the docs claim against what the code does.
• docs-update-from-diff by QwenLM. Updated June 9, 2026. Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
• docs-voice by reactjs. Updated January 30, 2026. Use when writing any React documentation. Provides voice, tone, and style rules for all doc types.
• docs-write by metabase. Updated February 10, 2026. Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
• docs-writer by maximhq. Updated August 23, 2026. Write, update, and review Mintlify MDX documentation for Bifrost features. Explores the full codebase (UI, Go backend, config schema), validates config.json examples, places screenshot placeholders, and presents outlines for approval before writing. Invoked with /docs-writer <feature-name>, /docs-writer update <doc-path>, or /docs-writer review <doc-path>.
• docs-writer by strands-agents. Updated June 15, 2026. Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X", "document this feature".
• docs-writer-blog by reactjs. Updated July 9, 2026. Use when writing or editing files in src/content/blog/. Provides blog post structure and conventions.
• docs-writer-reference by reactjs. Updated January 30, 2026. Reference page structure, templates, and writing patterns for src/content/reference/. For components, see /docs-components. For code examples, see /docs-sandpack.
• docs-writing-style by dagger. Updated September 18, 2026. Writing style for Dagger documentation prose in docs/current_docs. Use when writing, rewriting, or reviewing any docs page (guides, reference, config, getting started) to get the voice, scope, naming, and accuracy right. Complements docs/STYLE_GUIDE.md, which covers mechanics like titles, pronouns, lists, and snippets.
• docstring by pipecat-ai. Updated July 30, 2026. Document a Python module and its classes using Google style
• docstring by pytorch. Updated October 28, 2025. Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.
• document by Hmbown. Updated July 22, 2026. Write or update repository/product documentation: README, user guides, API docs, architecture, migration notes, and changelog material. This is not the Word-document artifact skill.
• document-changes by PrefectHQ. Updated March 25, 2026. Analyze source code changes on the current branch and identify documentation that is stale, inaccurate, or missing. Use before creating a PR to check if docs need updating, or in CI after merges to main to automatically fix docs. Trigger when the user mentions "doc changes", "docs update", "check docs", "document changes", or wants to know if code changes affect documentation.
• document-generate by garrytan. Updated September 24, 2026. Generate missing documentation from scratch for a feature, module, or entire project. (gstack)
• document-public-apis by pytorch. Updated April 13, 2026. Document undocumented public APIs in PyTorch by removing functions from coverage_ignore_functions and coverage_ignore_classes in docs/source/conf.py, running Sphinx coverage, and adding the appropriate autodoc directives to the correct .md or .rst doc files. Use when a user asks to remove functions from conf.py ignore lists.
• documentation by anthropics. Updated February 24, 2026. Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
• documentation by comet-ml. Updated September 3, 2026. Feature documentation and release notes patterns. Use when documenting changes, writing PR descriptions, or preparing releases.
• documentation by microsoft. Updated April 29, 2026. Add documentation for contributors and developers.
• documentation-and-adrs by addyosmani. Updated September 7, 2026. Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
• documentation-discovery by project-chip. Updated June 12, 2026. Essential guidelines instructing AI agents on how to incrementally discover, read, and consult top-level monorepo documentation and example-specific reference guides before altering code or executing test harnesses.
• documentation-standards by kubernetes-sigs. Updated April 17, 2026. Standards for Kubebuilder documentation in docs/book/src/. Use when writing or reviewing documentation, tutorials, guides, or plugin docs.
• documentation-templates by davila7. Updated January 25, 2026. Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
• documentation-writer by github. Updated February 24, 2026. 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.
• documenting-warehouse-sources by PostHog. Updated June 24, 2026. Write or update the user-facing posthog.com documentation for a PostHog Data warehouse import source. Use when adding a new source doc, fixing an inconsistent or stub source doc, or standardizing the docs at contents/docs/cdp/sources. Covers the canonical template, shared snippets, the auto-rendered <SourceParameters /> and <SourceTables /> components, frontmatter, and the docsUrl/slug rule that prevents 404s.
• draft-announcement by rommapp. Updated September 27, 2026. Draft the Discord release announcement for a RomM release, from the release notes plus an interview about community news. Use when asked to "write the Discord announcement for 5.3.0", "draft the announcement post", "announce the beta in Discord", or to refresh an announcement draft. Interviews the user for the things no diff contains (new team members, third-party apps to spotlight, milestones, events, Discord housekeeping), writes in the house voice, and never posts to Discord.
• draft-openspec-docs by Fission-AI. Updated August 21, 2026. Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.
• draft-release-notes by cobusgreyling. Updated June 9, 2026. Generate categorized release notes draft from scan data. Human must approve before publish.
• draft-release-notes by rommapp. Updated September 27, 2026. Draft the GitHub release notes for a RomM release, stable or alpha/beta prerelease, from the diff since the previous stable tag, in the house format the published RomM releases use. Use when asked to "draft the 5.3.0 notes", "write the release notes for the beta", "what goes in the 5.3.0-alpha.1 notes", or to refresh a draft after more PRs land. Produces callouts, Highlights, Minor changes, Fixes, Other changes, API changes and New Contributors, and never publishes.
• edit-figma-design by warpdotdev. Updated April 28, 2026. Create or update Figma designs directly from a written product or UI description using the Figma MCP authoring tools. Use when the user wants a mockup, wireframe, screen, component, flow, or concept designed in Figma from text, or wants to iterate on an existing Figma file from textual feedback. Despite the name, this skill can start from a new blank file or edit an existing one. Do not use for capture-based workflows that turn a running page into Figma; use `figma-generate-design` for those, and use `implement-design` for code implementation requests. Requires Figma MCP server connection.
• effect-development by pingdotgg. Updated September 18, 2026. Effect development guidance. Use when implementing or reviewing code that composes Effect APIs or patterns.
• embodiment-description by wanshuiyin. Updated July 13, 2026. Write detailed embodiment descriptions for patent specifications. Use when user says "撰写实施例", "write embodiment", "实施例描述", "detailed description", or wants to describe how to practice an invention.
• engine-whats-new by flutter. Updated July 22, 2026. Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44). When to use: - Only activate when explicitly asked by the user to generate what's new in the engine, diff Flutter engine releases, or produce an engine release summary. When not to use: - Do not use for general questions about commits, individual file history, or codebase searches unless explicitly requested to generate the engine release diff or summary.
• environment-setup-guide by davila7. Updated January 25, 2026. Guide developers through setting up development environments with proper tools, dependencies, and configurations
• everything-claude-code by affaan-m. Updated September 18, 2026. Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
• expo-api-docs by expo. Updated May 8, 2026. 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.
• faq by nexmoe. Updated September 13, 2026. Build a FAQ from the current video transcript without turning it into an essay.
• feedback by Hmbown. Updated September 18, 2026. Report a Codewhale bug or idea as a GitHub issue. Use when: codewhale bug, feature request, feedback on codewhale, report an issue, or this should work differently.
• figma-implement-design by davila7. Updated February 8, 2026. Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.
• figma-implement-design by openai. Updated March 25, 2026. Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.
• figma-implement-design by warpdotdev. Updated April 28, 2026. Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.
• find-docs by upstash. Updated July 25, 2026. Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your 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 as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.
• fix-package-docs by elastic. Updated August 3, 2026. Fix API documentation issues in a Kibana plugin or package. Use when asked to fix, improve, or add JSDoc/API documentation for a Kibana plugin or package, or when check_package_docs validation fails.
• fprime-cpp-design by nasa. Updated September 15, 2026. Authoritative C/C++ design rules and idioms for F Prime flight software. Use this skill in two directions — as a *developer-side* reference when writing or modifying F Prime C++ code (what idioms to follow, what features to avoid, which F Prime types to prefer), and as a *reviewer-side* reference for finding-class names and severity hints when flagging C/C++ design violations. Trigger on any work that touches F Prime C/C++ source: component implementations, drivers, services, framework types, OSAL code, or unit-test infrastructure. Keywords: F Prime, C++14, FW_ASSERT, Fw::Buffer, Fw::String, JPL coding standard, dynamic memory, RTTI, exceptions.
• framework-docs-researcher by udecode. Updated March 30, 2026. Gathers comprehensive documentation and best practices for frameworks, libraries, or dependencies. Use when you need official docs, version-specific constraints, or implementation patterns.
• frontend-to-backend-requirements by davila7. Updated January 25, 2026. Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI.
• gen-docs by MoonshotAI. Updated January 26, 2026. Update Kimi Code CLI user documentation.
• generate-docs by yagop. Updated June 25, 2026. How to (re)generate the API reference doc/api.md for node-telegram-bot-api. Use whenever a public Api method, class, function, or type is added/removed/changed, or when a PR check reports doc/api.md is out of date. Covers the two-stage pipeline (TypeDoc -> doc/api.json -> doc/api.md via scripts/generate-docs.ts), what it does and does not capture, and how to verify the result is committed.
• generate-manifest by google. Updated September 28, 2026. Scan an ADK recipe directory and generate a manifest.yaml for it based on the schema at .github/schemas/manifest-schema.json. Use when the user wants to create or generate a manifest.yaml for a recipe under core/, contrib/, or plugins/.
• generating-changelog by streamlit. Updated July 14, 2026. Generates polished website release notes between two git tags for docs.streamlit.io. Use when preparing a new Streamlit release or reviewing changes between versions.
• get-api-docs by andrewyng. Updated April 24, 2026. Use this skill to get documentation for third-party APIs, SDKs or libraries before writing code that uses them to ensure you have the latest, most accurate documentation. This is a better way to find documentation than doing web search. This includes when a user asks for tasks like "use the OpenAI API", "call the Stripe API", "use the Anthropic SDK", "query Pinecone", or any other time the user asks you to write code against an external service and you need current API reference. Fetch the docs with chub before answering, rather than relying on your pre-trained knowledge, which may be outdated because of recent changes to these APIs. Be sure to use this skill when the user asks for the latest docs, latest API behavior, or explicitly mentions chub or Context Hub. Ensure `chub` is available, run `chub --help`, then follow the instructions there.
• gmod-addon-maker by davila7. Updated February 23, 2026. A tool for creating and managing Garry's Mod addons, including Lua scripting, content creation, and addon packaging. Use when: developing new addons, writing Lua scripts for GMod, organizing addon files, or when user mentions Garry's Mod, GMod, Lua scripting, or addon development.
• go-naming by infiniflow. Updated June 17, 2026. Go naming conventions and best practices. Use this skill when working with Go code and need to name packages, files, directories, structs, interfaces, functions, variables, or constants. Provides comprehensive naming guidelines following Go community standards.
• golang by JanDeDobbeleer. Updated August 26, 2026. Go coding standards and conventions for this project. Apply when writing, reviewing, or refactoring any Go source file.
• good-docs-audit by ComposioHQ. Updated July 30, 2026. Audit a doc, guide, README, or block of prose against the good-docs-writing style guide and report violations. Use when the user asks to review, critique, lint, or check the voice and tone of documentation or text. Produces a structured findings report (file:line, rule violated, offending text, suggested rewrite) and does NOT edit files unless explicitly asked.
• good-docs-writing by ComposioHQ. Updated July 30, 2026. Writing style guide derived from Modal's documentation voice. Apply when writing or editing docs, guides, tutorials, or technical prose that should read direct, second-person, confident, low-jargon, and example-first. Use to draft new docs in this voice or to revise existing prose toward it.
• google-ads-api-mcp-setup by google. Updated September 22, 2026. Guides developers through downloading, configuring, and installing the official open-source Google Ads MCP Server. Use this skill when a user wants to connect their AI assistant (such as Gemini, Claude Code, or Cursor) to their Google Ads account to query campaigns or retrieve reporting metrics using natural language.
• google-ads-api-quickstart by google. Updated September 22, 2026. Guides developers through Google Ads API quickstart: credential setup, choosing from 6 client libraries/REST, configuring environments, and running a "retrieve campaigns" script. Troubleshoots common setup errors: USER_PERMISSION_DENIED, login_customer_id issues, and DEVELOPER_TOKEN_NOT_APPROVED. Use this skill when: - The user asks how to get started with the Google Ads API. - The user needs to set up Google Ads credentials or developer tokens. - The user wants to write a quickstart/example script for Google Ads. - The user encounters errors like USER_PERMISSION_DENIED or DEVELOPER_TOKEN_NOT_APPROVED.
• gpt-5-4-prompting by openai. Updated March 30, 2026. Internal guidance for composing Codex and GPT-5.4 prompts for coding, review, diagnosis, and research tasks inside the Codex Claude Code plugin
• gpui-component-dev by longbridge. Updated August 13, 2026. Contributing to the gpui-component library: creating new UI components, writing component stories, writing component documentation, and writing GitHub PR descriptions. Use when adding a new component to crates/ui, writing a story in crates/story/src/stories, creating docs in the docs/ folder, or writing a PR description for this project.
• gsd-docs-update by open-gsd. Updated June 22, 2026. Generate or update project documentation verified against the codebase
• gui-ui-guidelines by warpdotdev. Updated July 31, 2026. GUI desktop app only. Catalog of guidelines for writing UI code in the Warp client. Read whenever doing any UI work in this repo, up front before writing the change, so the relevant guidelines shape the implementation.
• guide by recharts. Updated July 5, 2026. Create new article guides for Recharts users
• help by Hmbown. Updated September 23, 2026. Route a "how do I use Codewhale" question to the installed help, config, and doctor surfaces instead of reciting a manual from memory. Explicit-only.
• hindsight-docs by vectorize-io. Updated September 25, 2026. Complete Hindsight documentation for AI agents. Use this to learn about Hindsight architecture, APIs, configuration, and best practices.
• home-assistant-docs-writing-style by home-assistant. Updated July 10, 2026. Use this when writing or editing Home Assistant documentation, website pages, integration pages, blog prose, UI instructions, or other user-facing prose.
• humanizer by zed-industries. Updated February 24, 2026. Remove signs of AI-generated writing from text. Use after drafting to make copy sound more natural and human-written. Based on Wikipedia's "Signs of AI writing" guide.
• hyperframes-studio by heygen-com. Updated September 27, 2026. Use when building or editing a HyperFrames project that people open in Studio: how the timeline should be laid out so it reads well (one caption track, one element kind per track, every scene a sub-composition) and where captions and key content may sit (safe zones). Don't use for how to perform an individual edit (split, trim, retime, volume, copy, swap): that is `creator-editing-recipes.md` in `/hyperframes-core`.
• improve-oas by elastic. Updated August 3, 2026. Add or improve OpenAPI descriptions, examples, and code samples for a Kibana API area. Use when a plugin or package needs better OAS documentation — missing descriptions on schema fields, missing route summaries, missing examples, or missing code samples.
• init by asgeirtj. Updated September 9, 2026. Initialize a new CLAUDE.md file with codebase documentation
• investment-memo-craft by xbtlin. Updated June 27, 2026. Codex-only writing and layout overlay for AI Berkshire investment research reports. Use whenever Codex creates, rewrites, revises, or critiques company/industry/fund research reports, especially long-form Markdown reports that need financial rigor, readable business mechanics, contrarian analysis, valuation-to-action guidance, investor-specific recommendations, restrained typography, and clear buy/hold/sell signals. Do not use this to modify Claude Code slash-command sources.
• isaaclab-following-coding-style by isaac-sim. Updated July 23, 2026. Applies Isaac Lab coding style, API design, docstring, type-hint, lazy export, and contribution conventions. Use when writing or reviewing Isaac Lab Python code, public APIs, config classes, module exports, or documentation strings.
• java-development by apache. Updated February 9, 2026. Guides Java SDK development in Apache Beam, including building, testing, running examples, and understanding the project structure. Use when working with Java code in sdks/java/, runners/, or examples/java/.
• java-docs by github. Updated February 24, 2026. Ensure that Java types are documented with Javadoc comments and follow best practices for documentation.
• javascript-mastery by davila7. Updated January 25, 2026. Comprehensive JavaScript reference covering 33+ essential concepts every developer should know. From fundamentals like primitives and closures to advanced patterns like async/await and functional programming. Use when explaining JS concepts, debugging JavaScript issues, or teaching JavaScript fundamentals.
• job-post-builder by anthropics. Updated September 15, 2026. Builds end-to-end hiring packets — job post, structured interview guide with scoring rubric, and offer letter template — from a hiring brief. Triggers on: "help me hire", "we're hiring for", "write a job post", "job description", "JD", "open role", "create a job ad", "interview questions", "scoring rubric", "draft an offer letter", "send an offer", "make a hiring packet", or any request to recruit for a position. When in doubt, trigger — covers the full hiring workflow from job post through DocuSign envelope creation via browser. Does NOT screen or rank applicants.
• jsdocs by Effect-TS. Updated September 23, 2026. Public API JSDoc. Use when authoring or reviewing Effect API documentation, refining a module's documentation, or fixing documentation related diagnostics.
• jsdocs by pingdotgg. Updated September 18, 2026. Public API JSDoc. Use when authoring or reviewing Effect API documentation, refining a module's documentation, or fixing documentation related diagnostics.
• jupyter-notebook by microsoft. Updated February 20, 2026. Bruges når brugeren beder om at oprette, opsætte eller redigere Jupyter-notebooks (`.ipynb`) til eksperimenter, udforskninger eller vejledninger; foretræk de medfølgende skabeloner og kør hjælpeskriptet `new_notebook.py` for at generere en ren start-notebook.
• jupyter-notebook by microsoft. Updated February 19, 2026. Naudokite, kai vartotojas prašo sukurti, paruošti arba redaguoti Jupyter užrašų knygeles (`.ipynb`) eksperimentams, tyrimams arba pamokoms; teikite pirmenybę pridedamiems šablonams ir paleiskite pagalbinį scenarijų `new_notebook.py`, kad sugeneruotumėte švarų pradinį užrašų knygelę.
• jupyter-notebook by microsoft. Updated February 20, 2026. प्रयोगकर्ताले प्रयोग, अन्वेषण, वा ट्युटोरियलका लागि Jupyter नोटबुकहरू (`.ipynb`) बनाउन, ढाँचा तयार गर्न, वा सम्पादन गर्न अनुरोध गरेमा प्रयोग गर्नुहोस्; समावेश गरिएको टेम्प्लेटलाई प्राथमिकता दिनुहोस् र सफा सुरुवाती नोटबुक उत्पन्न गर्न सहायक स्क्रिप्ट `new_notebook.py` चलाउनुहोस्।
• jupyter-notebook by microsoft. Updated February 19, 2026. Użyj, gdy użytkownik prosi o utworzenie, przygotowanie szkieletu lub edycję notatników Jupyter (`.ipynb`) do eksperymentów, eksploracji lub samouczków; preferuj dołączone szablony i uruchom skrypt pomocniczy `new_notebook.py`, aby wygenerować czysty notebook początkowy.
• jupyter-notebook by microsoft. Updated February 20, 2026. Använd när användaren ber om att skapa, strukturera eller redigera Jupyter-notebooks (`.ipynb`) för experiment, utforskningar eller handledningar; använd helst de medföljande mallarna och kör hjälpskriptet `new_notebook.py` för att generera en ren startanteckningsbok.
• jupyter-notebook by microsoft. Updated February 20, 2026. ใช้เมื่อผู้ใช้ร้องขอให้สร้าง จัดโครงร่าง หรือแก้ไข Jupyter notebooks (`.ipynb`) สำหรับการทดลอง การสำรวจ หรือบทแนะนำ; ควรใช้เทมเพลตที่มาพร้อมและรันสคริปต์ช่วยเหลือ `new_notebook.py` เพื่อสร้างโน้ตบุ๊กเริ่มต้นที่สะอาด
• kedro-docs-draft-writer by kedro-org. Updated August 14, 2026. Draft or polish Kedro documentation. Writes a first draft from source code or a branch, or polishes an existing draft the user provides. Follows the Kedro style guide, places new files in the correct docs/ path, and runs Vale before handing back. Use when the user says "draft docs for X", "write a how-to for X", "document this feature", "polish my draft", or wants to beat blank-page paralysis on any Kedro docs page.
• keploy-docs by keploy. Updated April 27, 2026. Guide for contributing to the Keploy documentation site at github.com/keploy/docs. Invoke when a change in keploy/keploy introduces, removes, or alters user-visible behavior (new CLI flag, changed default, new command, new configuration field, new on-disk format) and the docs need to catch up — or when the user asks to document a feature, write a quickstart, or fix a docs bug. Covers where to put the edit, every CI check that must pass, and how to reproduce each check locally before the PR.
• lat-md by fathah. Updated June 20, 2026. Writing and maintaining lat.md documentation files — structured markdown that describes a project's architecture, design decisions, and test specs. Use when creating, editing, or reviewing files in the lat.md/ directory.
• learn by nanocoai. Updated June 24, 2026. Distill a reusable skill from anything — a directory, a URL, pasted notes, or what you just did together — or refine an existing skill with new learnings. Use when the user says '/learn', 'learn this', 'turn this into a skill', 'capture this workflow', 'make a skill from <source>', or 'improve/update the <name> skill'. Produces or updates a .claude/skills/<name>/SKILL.md authored to NanoClaw's skill guidelines. (This CREATES or REFINES a skill from a source; it does not install existing skills from a registry.)
• legal-writer by kortix-ai. Updated August 3, 2026. Legal document drafting -- contracts, memos, briefs, complaints, demand letters, opinions, discovery, settlements, ToS, privacy policies. Full pipeline: document structure, per-section writing, Bluebook citation, case law lookup (CourtListener API), regulation lookup (eCFR API), DOCX output, and TDD-style verification (defined terms, cross-references, placeholders, boilerplate, citation format). Triggers on: 'draft a contract', 'write a legal memo', 'create an NDA', 'write a brief', 'legal document about', 'draft a complaint', 'terms of service', 'privacy policy', 'demand letter', 'settlement agreement', 'legal opinion', 'discovery requests', any request to produce a legal or law-related document.
• live-tutorial by leon-ai. Updated September 14, 2026. Create an annotated MP4 tutorial from a workflow demonstrated in the owner's actual application. Use when asked for a tutorial video, not merely to watch an action live.
• llamafactory-v1-docs by hiyouga. Updated September 14, 2026. Write, review, update, build, or preview LlamaFactory v1 documentation. Use for docs work grounded in src/llamafactory/v1; not for running model training.
• logseq-answer-machine by logseq. Updated May 14, 2026. Answer user questions about the Logseq repository by researching source code, docs, tests, runtime behavior, and local tools. Use when Codex needs to explain how Logseq works, why behavior happens, where logic lives, how CLI/Desktop/Web flows interact, or what evidence supports an answer, without implementing features or fixing bugs.
• magisk-app by topjohnwu. Updated August 31, 2026. Guidelines, architecture, development conventions, and build workflows for the Magisk Android application (app/ subproject). Use when working on, modifying, building, or testing code in app/ or any of its submodules (:core, :apk, :shared, :stub, :stub-res, :test, :build-logic, :apk-legacy).
• make-instructions by dotnet. Updated September 18, 2026. Create and evaluate VS Code file-based instructions (.instructions.md files). Use when asked to create, scaffold, or add file-based instructions for Copilot. Generates scoped instructions and a paired Vally harness eval.
• make-plan by thedotmack. Updated February 16, 2026. Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do-plan.
• make-plan by thedotmack. Updated May 21, 2026. Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.
• make-repo-contribution by github. Updated February 17, 2026. All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.
• markdown-mermaid-writing by K-Dense-AI. Updated July 26, 2026. Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.
• mastra-docs by mastra-ai. Updated August 18, 2026. Documentation guidelines for Mastra. Use this skill when creating, editing, moving, deleting, or reviewing Mastra documentation, sidebars, redirects, or docs components.
• mastra-frontend by mastra-ai. Updated September 29, 2026. How to build Mastra frontend interfaces with the @mastra/playground-ui design system. This skill should be used when creating or modifying any application UI — pages, components, styling, or tokens — in this repo or in an external consumer of the design system. The docs site has its own styling and is out of scope.
• mermaid-diagrams by davila7. Updated January 25, 2026. Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
• microsoft-code-reference by github. Updated March 16, 2026. Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get working examples, or troubleshoot errors. Catches hallucinated methods, wrong signatures, and deprecated patterns by querying official docs.
• microsoft-docs by github. Updated March 16, 2026. Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 16, 2026. Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 19, 2026. Запитвайте официалната документация на Microsoft, за да намерите концепции, уроци и примери за код за Azure, .NET, Agent Framework, Aspire, VS Code, GitHub и други. Използва Microsoft Learn MCP като по подразбиране, като за съдържание, което се намира извън learn.microsoft.com, използва Context7 и Aspire MCP.
• microsoft-docs by microsoft. Updated February 19, 2026. Prohledávejte oficiální dokumentaci Microsoftu, abyste našli koncepty, návody a ukázky kódu napříč Azure, .NET, Agent Framework, Aspire, VS Code, GitHub a dalšími. Jako výchozí používá Microsoft Learn MCP; pro obsah, který se nachází mimo learn.microsoft.com, používá Context7 a Aspire MCP.
• microsoft-docs by microsoft. Updated February 20, 2026. Søg i den officielle Microsoft-dokumentation for at finde koncepter, vejledninger og kodeeksempler på tværs af Azure, .NET, Agent Framework, Aspire, VS Code, GitHub og mere. Bruger Microsoft Learn MCP som standard, samt Context7 og Aspire MCP til indhold, der findes uden for learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 20, 2026. Αναζητήστε επίσημη τεκμηρίωση της Microsoft για να βρείτε έννοιες, σεμινάρια και παραδείγματα κώδικα σε Azure, .NET, Agent Framework, Aspire, VS Code, GitHub και άλλα. Χρησιμοποιεί το Microsoft Learn MCP ως προεπιλογή, με το Context7 και το Aspire MCP για περιεχόμενο που βρίσκεται εκτός learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 18, 2026. Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 18, 2026. Consulta la documentación oficial de Microsoft para encontrar conceptos, tutoriales y ejemplos de código en Azure, .NET, Agent Framework, Aspire, VS Code, GitHub y más. Utiliza Microsoft Learn MCP como predeterminado, con Context7 y Aspire MCP para contenido que se encuentra fuera de learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 20, 2026. Küsib ametlikku Microsofti dokumentatsiooni, et leida mõisteid, juhendeid ja koodinäiteid Azure'i, .NET-i, Agent Frameworki, Aspire'i, VS Code'i, GitHubi ja muu kohta. Vaikimisi kasutatakse Microsoft Learn MCP-i; Context7 ja Aspire MCP-i kasutatakse sisu jaoks, mis asub väljaspool learn.microsoft.com-i.
• microsoft-docs by microsoft. Updated February 20, 2026. Kysy virallista Microsoftin dokumentaatiota löytääksesi käsitteitä, opetusohjelmia ja koodiesimerkkejä Azureen, .NET:iin, Agent Frameworkiin, Aspireen, VS Codeen, GitHubiin ja muihin liittyen. Käyttää oletuksena Microsoft Learn MCP:tä, sekä Context7:ää ja Aspire MCP:tä sisällölle, joka sijaitsee learn.microsoft.comin ulkopuolella.
• microsoft-docs by microsoft. Updated February 18, 2026. Interroger la documentation officielle de Microsoft pour trouver des concepts, des tutoriels et des exemples de code couvrant Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, et plus encore. Utilise Microsoft Learn MCP par défaut, avec Context7 et Aspire MCP pour le contenu qui se trouve en dehors de learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 19, 2026. Interroga la documentazione ufficiale Microsoft per trovare concetti, tutorial ed esempi di codice relativi ad Azure, .NET, Agent Framework, Aspire, VS Code, GitHub e altro. Usa Microsoft Learn MCP come predefinito, con Context7 e Aspire MCP per i contenuti che si trovano al di fuori di learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 20, 2026. 公式の Microsoft ドキュメントを検索して、Azure、.NET、Agent Framework、Aspire、VS Code、GitHub などの概念、チュートリアル、コード例を見つけます。既定では Microsoft Learn MCP を使用し、learn.microsoft.com の外にあるコンテンツには Context7 と Aspire MCP を使用します。
• microsoft-docs by microsoft. Updated March 7, 2026. ಅಧಿಕೃತ Microsoft ಡಾಕ್ಯುಮೆಂಟೇಶನ್ ಅನ್ನು ಪ್ರಶ್ನೆ ಮಾಡಿ Azure, .NET, Agent Framework, Aspire, VS Code, GitHub ಮತ್ತು ಇತರೆ ಸಂಬಂಧಿತ ವಿಷಯಗಳ ಮೇಲೆ ತತ್ವಗಳು, ಟ್ಯುಟೋರಿಯಲ್ಗಳು ಮತ್ತು ಕೋಡ್ ಉದಾಹರಣೆಗಳನ್ನು ಕಂಡುಹಿಡಿಯಿರಿ. ಡೀಫಾಲ್ಟ್‌ವಾಗಿ Microsoft Learn MCP ಅನ್ನು ಬಳಸುತ್ತದೆ; learn.microsoft.com ಹೊರಗಿನ ವಿಷಯಗಳಿಗೆ Context7 ಮತ್ತು Aspire MCP ಅನ್ನು ಬಳಸಲಾಗುತ್ತದೆ.
• microsoft-docs by microsoft. Updated February 19, 2026. Ieškokite oficialioje Microsoft dokumentacijoje sąvokų, pamokų ir kodo pavyzdžių apie Azure, .NET, Agent Framework, Aspire, VS Code, GitHub ir dar daugiau. Naudoja Microsoft Learn MCP kaip numatytąjį, o Context7 ir Aspire MCP — turiniui, esantį už learn.microsoft.com ribų.
• microsoft-docs by microsoft. Updated February 19, 2026. Kueri dokumentasi rasmi Microsoft untuk mencari konsep, tutorial, dan contoh kod merentas Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, dan banyak lagi. Menggunakan Microsoft Learn MCP sebagai lalai, dengan Context7 dan Aspire MCP untuk kandungan yang berada di luar learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 20, 2026. Doorzoek de officiële Microsoft-documentatie om concepten, tutorials en codevoorbeelden te vinden voor Azure, .NET, Agent Framework, Aspire, VS Code, GitHub en meer. Gebruikt Microsoft Learn MCP als standaard, met Context7 en Aspire MCP voor inhoud die buiten learn.microsoft.com staat.
• microsoft-docs by microsoft. Updated February 20, 2026. Søk i offisiell Microsoft-dokumentasjon for å finne konsepter, veiledninger og kodeeksempler på tvers av Azure, .NET, Agent Framework, Aspire, VS Code, GitHub og mer. Bruker Microsoft Learn MCP som standard, med Context7 og Aspire MCP for innhold som ligger utenfor learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 20, 2026. Na to search official Microsoft documentation make you fit find concepts, tutorials, and code examples for Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and plenty more. E dey use Microsoft Learn MCP as the default, together with Context7 and Aspire MCP for content wey dey outside learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 19, 2026. Przeszukaj oficjalną dokumentację Microsoft, aby znaleźć koncepcje, samouczki i przykłady kodu dotyczące Azure, .NET, Agent Framework, Aspire, VS Code, GitHub i innych. Domyślnie używa Microsoft Learn MCP, a dla treści znajdujących się poza learn.microsoft.com korzysta z Context7 i Aspire MCP.
• microsoft-docs by microsoft. Updated February 19, 2026. Consultar a documentação oficial da Microsoft para encontrar conceitos, tutoriais e exemplos de código sobre Azure, .NET, Agent Framework, Aspire, VS Code, GitHub e muito mais. Usa o Microsoft Learn MCP como padrão, com Context7 e Aspire MCP para conteúdo que esteja fora do learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 19, 2026. Consultar a documentação oficial da Microsoft para encontrar conceitos, tutoriais e exemplos de código sobre Azure, .NET, Agent Framework, Aspire, VS Code, GitHub e mais. Utiliza o Microsoft Learn MCP como predefinição, com o Context7 e o Aspire MCP para conteúdo que se encontra fora do learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 19, 2026. Interoghează documentația oficială Microsoft pentru a găsi concepte, tutoriale și exemple de cod pentru Azure, .NET, Agent Framework, Aspire, VS Code, GitHub și altele. Folosește Microsoft Learn MCP ca implicit, iar pentru conținutul care se află în afara learn.microsoft.com utilizează Context7 și Aspire MCP.
• microsoft-docs by microsoft. Updated February 19, 2026. Запрашивайте официальную документацию Microsoft, чтобы находить концепции, учебники и примеры кода по Azure, .NET, Agent Framework, Aspire, VS Code, GitHub и другим. Используется Microsoft Learn MCP по умолчанию, а для контента, размещённого вне learn.microsoft.com, — Context7 и Aspire MCP.
• microsoft-docs by microsoft. Updated February 19, 2026. Prehľadávajte oficiálnu dokumentáciu Microsoftu, aby ste našli koncepty, návody a ukážky kódu naprieč Azure, .NET, Agent Framework, Aspire, VS Code, GitHub a ďalšími. Používa Microsoft Learn MCP ako predvolený zdroj, spolu s Context7 a Aspire MCP pre obsah, ktorý sa nachádza mimo learn.microsoft.com.
• microsoft-docs by microsoft. Updated February 19, 2026. Poizvedujte v uradni Microsoftovi dokumentaciji, da poiščete koncepte, vodiče in primere kode za Azure, .NET, Agent Framework, Aspire, VS Code, GitHub in še več. Privzeto uporablja Microsoft Learn MCP, za vsebino, ki se nahaja zunaj learn.microsoft.com, pa Context7 in Aspire MCP.
• microsoft-docs by microsoft. Updated February 19, 2026. Претражите званичну Microsoft документацију да бисте пронашли концепте, туторијале и примере кода за Azure, .NET, Agent Framework, Aspire, VS Code, GitHub и још. Користи Microsoft Learn MCP као подразумевани, а за садржај који се налази ван learn.microsoft.com користи Context7 и Aspire MCP.
• microsoft-docs by microsoft. Updated February 20, 2026. Fråga den officiella Microsoft-dokumentationen för att hitta koncept, handledningar och kodexempel inom Azure, .NET, Agent Framework, Aspire, VS Code, GitHub och mer. Använder Microsoft Learn MCP som standard, med Context7 och Aspire MCP för innehåll som finns utanför learn.microsoft.com.
• microsoft-docs by microsoft. Updated March 7, 2026. Microsoft యొక్క అధికారిక డాక్యుమెంటేషన్‌ను పరిశీలించి Azure, .NET, Agent Framework, Aspire, VS Code, GitHub మరియు మరెన్నో అంశాలకు సంబంధించిన కాన్సెప్ట్స్, ట్యుటోరియల్స్ మరియు కోడ్ ఉదాహరణలను కనుగొనండి. డిఫాల్ట్‌గా Microsoft Learn MCP ను ఉపయోగిస్తుంది, learn.microsoft.com వెలుపల ఉన్న కంటెంట్ కోసం Context7 మరియు Aspire MCP ను ఉపయోగిస్తుంది.
• microsoft-docs by microsoft. Updated February 19, 2026. Запитуйте офіційну документацію Microsoft, щоб знаходити концепції, навчальні посібники та приклади коду щодо Azure, .NET, Agent Framework, Aspire, VS Code, GitHub та іншого. Використовує Microsoft Learn MCP за замовчуванням, а для вмісту, що знаходиться поза learn.microsoft.com, — Context7 та Aspire MCP.
• microsoft-docs by microsoft. Updated February 20, 2026. Truy vấn tài liệu chính thức của Microsoft để tìm các khái niệm, hướng dẫn và ví dụ mã trên Azure, .NET, Agent Framework, Aspire, VS Code, GitHub và nhiều hơn nữa. Sử dụng Microsoft Learn MCP làm mặc định, với Context7 và Aspire MCP cho nội dung nằm ngoài learn.microsoft.com.
• minimal-fix by cobusgreyling. Updated June 9, 2026. Produce the smallest possible code change that fixes a specific, well-scoped issue (CI failure, reviewer comment, typo). Use only when the fix target is explicit. Never refactor unrelated code.
• mintlify by activepieces. Updated June 26, 2026. Build and maintain documentation sites with Mintlify. Use when creating docs pages, configuring navigation, adding components, or setting up API references.
• mintlify by Arize-ai. Updated September 21, 2026. Build and maintain documentation sites with Mintlify. Use when creating docs pages, configuring navigation, adding components, or setting up API references.
• mintlify-docs by nearai. Updated August 21, 2026. Use when creating docs pages, configuring navigation, adding components, or setting up API references with Mintlify.
• mkdocs-docs by kata-containers. Updated June 23, 2026. Write or edit documentation in this repository under docs/. The site is built with mkdocs-materialx (a fork of mkdocs-material) and navigation is controlled via docs/.nav.yml. Use this skill whenever the user asks you to add, write, edit, restructure, or review any file under docs/ — including new pages, how-to guides, use-cases, design docs, README-style entries inside docs/, and updates to docs/.nav.yml. Trigger even when the user does not explicitly say "mkdocs" or "materialx" — any work that produces or modifies a Markdown file under docs/ should use this skill so the output uses admonitions (not `>` blockquotes for notes), omits manual tables of contents, and takes advantage of mkdocs-material features (tabs, code annotations, mermaid, collapsible blocks, etc.).
• ml-paper-writing by Orchestra-Research. Updated April 10, 2026. Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. For systems venues (OSDI, NSDI, ASPLOS, SOSP), use systems-paper-writing instead.
• mobilerun-docs by droidrun. Updated September 16, 2026. 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.
• n8n-code-javascript by czlonkowski. Updated July 3, 2026. Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with this.helpers / the $helpers global, working with dates using DateTime, troubleshooting Code node errors, choosing between Code node modes, or doing any custom data transformation in n8n. Always use this skill when a workflow needs a Code node — whether for data aggregation, filtering, API calls, format conversion, batch processing logic, or any custom JavaScript. Covers SplitInBatches loop patterns, cross-iteration data, pairedItem, and real-world production patterns. Also use when asked why a Code node or workflow is slow, which execution mode is faster, or how to cut per-item overhead on large datasets. EXCEPTION — for the AI-agent-callable Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode, a tool attached to an AI Agent), use the n8n-code-tool skill instead; it has a different runtime contract.
• n8n-code-javascript by davila7. Updated January 8, 2026. Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, or choosing between Code node modes.
• n8n-code-python by czlonkowski. Updated July 3, 2026. Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes. Use this skill when the user specifically requests Python for an n8n Code node. Note — JavaScript is recommended for 95% of use cases — only use Python when the user explicitly prefers it or the task requires Python-specific standard library capabilities (regex, hashlib, statistics). EXCEPTION — for Python in the AI-agent-callable Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode), use the n8n-code-tool skill instead (input is _query, return must be a string).
• n8n-code-python by davila7. Updated January 8, 2026. Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes.
• n8n-create-skill by n8n-io. Updated June 16, 2026. Guides users through creating effective Agent Skills. Use when you want to create, write, or author a new skill, or asks about skill structure, best practices, or SKILL.md format.
• n8n-experiments by n8n-io. Updated September 28, 2026. Guides work on `packages/frontend/editor-ui` experiments. Use when creating, extending, wiring, testing, reviewing, or retiring editor-ui experiments, PostHog feature flags, experiment key indexes, variants, stores/composables, persisted experiment state, or experiment telemetry.
• n8n-ui-design by n8n-io. Updated September 28, 2026. Guidelines on designing and building UI. Use when working in editor-ui or design-system packages. Triggers for tasks that include refactoring components, styling changes, or feature work.
• natural-writing by flutter. Updated June 8, 2026. Contains well-defined rules for creating natural, accurate, and readable writing. Use whenever authoring longer text, like analysis documents, PR or CL descriptions, or documentation.
• nemoclaw-user-guide by NVIDIA. Updated September 17, 2026. Find official NemoClaw documentation for installation, configuration, operation, or troubleshooting. Also handles requested docs MCP setup.
• network-traffic-annotations by chromium. Updated April 3, 2026. Guide for writing and managing Network Traffic Annotations in Chromium. Use this skill when adding or updating code that makes network requests.
• no-bare-casts by prisma. Updated August 3, 2026. Writing `as` in TypeScript or TSX production code, modifying a file that contains a bare `as` cast, silencing a type error with a cast, encountering `as unknown as`, or reviewing a cast site.
• nx-generate by nrwl. Updated June 18, 2026. Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a new app, create a new lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.
• nx-generate by tsparticles. Updated February 10, 2026. Generate code using nx generators. INVOKE IMMEDIATELY when user mentions scaffolding, setup, structure, creating apps/libs, or setting up project structure. Trigger words - scaffold, setup, create a ... app, create a ... lib, project structure, generate, add a new project. ALWAYS use this BEFORE calling nx_docs or exploring - this skill handles discovery internally.
• obsidian-clipper-template-creator by davila7. Updated January 25, 2026. Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
• odoo-guidelines by odoo. Updated September 25, 2026. House rules for Odoo addon code: module structure, manifest, Python/ORM, fields, controllers, XML views and data, QWeb reports, access rights and record rules, performance, tests. Use when writing or reviewing any file in an Odoo addon outside static/ (for the JavaScript, Owl templates and SCSS under static/, see odoo-web-guidelines).
• odysseus by odysseus-dev. Updated June 9, 2026. Use when the user asks Codex to read or write Odysseus data (todos, email, calendar, memory, documents) or to launch/monitor/stop a Cookbook model-serve task through the scoped Codex Agent API. Requires ODYSSEUS_URL and ODYSSEUS_API_TOKEN.
• oo-component-documentation by github. Updated March 15, 2026. Create or update standardized object-oriented component documentation using a shared template plus mode-specific guidance for new and existing docs.
• opc-mvp-designer by easychen. Updated April 23, 2026. Define the smallest viable experiment and MVP for a selected one-person company opportunity. Use when Codex needs to explain what MVP means when needed, verify prerequisites, ask one question at a time, present multiple MVP options, and write user-confirmed outputs into `opc-doc/`.
• open-source by browser-use. Updated September 15, 2026. Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browser_use, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle hooks, MCP server setup, or monitoring/observability with Laminar or OpenLIT. Also trigger for questions about browser-use installation, prompting strategies, or sensitive data handling. Do NOT use this for Cloud API/SDK usage or pricing — use the cloud skill instead. Do NOT use this for directly automating a browser via CLI commands — use the browser-use skill instead.
• openai-docs by davila7. Updated February 8, 2026. Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to official OpenAI domains.
• openai-docs by openai. Updated June 17, 2026. Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.
• openai-docs by openai. Updated June 17, 2026. Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.
• openapi-glossary by scalar. Updated March 15, 2026. Use consistent OpenAPI terminology and definitions when writing documentation, educational material, and tooling guidance.
• openapi-spec-generation by wshobson. Updated September 28, 2026. Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns. Use when creating API documentation, generating SDKs, or ensuring API contract compliance.
• opensandbox-release-notes by opensandbox-group. Updated September 28, 2026. Generate umbrella release notes for the whole OpenSandbox repository (docs/releases/X.Y.Z.md) by analyzing all merged PRs since the previous release baseline. Triggered when users ask to write or generate OpenSandbox release notes, changelogs, or release summaries for a specific version.
• opensourcefaq by digoal. Updated April 23, 2026. Answer open-source product questions by combining local source-code and documentation research, project framework notes generated by init, DeepWiki repository knowledge, and current web evidence, then save a sourced, diagram-rich Markdown answer to the current project's markdown directory. Use when the user asks about behavior, architecture, internals, configuration, APIs, troubleshooting, performance, operations, extension points, practical reproduction, or version-specific details of one or more open-source projects and provides the question, all relevant local source directories, and DeepWiki repoName values.
• openspec-onboard by Fission-AI. Updated September 23, 2026. Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work. Also use when the user says "openspec onboard" or "opsx onboard".
• orchestrator by agent0ai. Updated September 8, 2026. Delegate to external coding CLIs: A0 headless, Codex, Claude Code and others.
• paper-plan by wanshuiyin. Updated September 28, 2026. Generate a structured paper outline from review conclusions and experiment results. Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing.
• paper-plan by wanshuiyin. Updated August 21, 2026. Generate a structured paper outline from review conclusions and experiment results. Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing.
• paper-plan by wanshuiyin. Updated July 10, 2026. Generate a structured paper outline from review conclusions and experiment results. Use when user says "写大纲", "paper outline", "plan the paper", "论文规划", or wants to create a paper plan before writing.
• paper-plan by wanshuiyin. Updated September 6, 2026. Generate a structured paper outline from review conclusions and experiment results. Use when user says \"写大纲\", \"paper outline\", \"plan the paper\", \"论文规划\", or wants to create a paper plan before writing.
• patent-pipeline by wanshuiyin. Updated September 6, 2026. Full patent drafting pipeline from invention description to jurisdiction-formatted filing documents. Supports CN (CNIPA), US (USPTO), EP (EPO). Supports invention patents and utility models. Use when user says "写专利", "patent pipeline", "专利申请", "draft patent", "写权利要求书", or wants to draft a complete patent application.
• patent-pipeline by wanshuiyin. Updated September 6, 2026. Full patent drafting pipeline from invention description to jurisdiction-formatted filing documents. Supports CN (CNIPA), US (USPTO), EP (EPO). Supports invention patents and utility models. Use when user says "写专利", "patent pipeline", "专利申请", "draft patent", "写权利要求书", or wants to draft a complete patent application.
• perl-patterns by affaan-m. Updated August 12, 2026. Modern Perl 5.36+ idioms, best practices, and conventions for building robust, maintainable Perl applications. Use when writing or reviewing modern Perl 5.36+ code.
• phoenix-release-notes by Arize-ai. Updated September 11, 2026. Create Phoenix release documentation grounded in actual code changes. Use this skill whenever the user asks to write release notes, document a release, update release documentation, or mentions undocumented releases. Also trigger when the user wants to update GitHub release descriptions, add entries to the release notes page, or asks what changed in a recent Phoenix version.
• phoenix-typescript by Arize-ai. Updated August 14, 2026. TypeScript conventions and patterns for any TypeScript code in the Phoenix monorepo — including js/packages/, js/app/, and any other TS directories. Use this skill whenever writing, reviewing, or modifying TypeScript code — new functions, types, exports, tests, or refactors. Also trigger when the user asks about TS patterns, naming conventions, or best practices for this project.
• pinchtab-dev by pinchtab. Updated September 13, 2026. Develop and contribute to the PinchTab project. Use when working on PinchTab source code, adding features, fixing bugs, running tests, or preparing PRs. Triggers on "work on pinchtab", "pinchtab development", "contribute to pinchtab", "fix pinchtab bug", "add pinchtab feature".
• playwright-dev by microsoft. Updated August 28, 2026. Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.
• policy-redraft by anthropics. Updated May 12, 2026. Produce a proposed marked-up policy redraft that closes a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says "redraft the policy", "draft the policy fix", "mark up the policy", or when gap-surfacer hands off a gap for drafting.
• pr-checklist by open-metadata. Updated September 28, 2026. Use when opening or finalizing a GitHub PR for OpenMetadata. Walks through the repo PR template — linked issue, high-level design (for big PRs), unit/integration/Playwright tests + coverage, UI screen recording, and manual test steps — then drafts a fully-filled PR body and (optionally) creates the PR.
• pr-description by pipecat-ai. Updated September 15, 2026. Draft or update a GitHub PR description that explains the problem, changed behavior, and review concerns in plain language.
• pr-description by zulip. Updated September 3, 2026. Write a pull request description following Zulip's guidelines. Use when opening a pull request or drafting/revising its title or description.
• pr-design-doc by OpenHands. Updated September 10, 2026. For a non-trivial pull request, write a self-contained HTML design doc under the temporary `.pr/` directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the proposal at a glance - code/API design, and the before/after of the change, grounded to real code. Use when opening or updating a non-trivial PR, or when the user says "add a design doc", "document this PR for reviewers", "show the before/after", "make the design reviewable", or "write the .pr/ page".
• pr-draft-summary by redis. Updated July 1, 2026. Create the required PR-ready summary block, branch suggestion, title, and draft description for ioredis. Must be used before the final response whenever the actual task diff includes runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size. Skip only when no eligible files changed, every change is repo-meta or docs-only without behavior impact, the task is conversation-only, or the user explicitly opts out.
• pr-draft-summary by redis. Updated July 1, 2026. Create the required PR-ready summary block, branch suggestion, title, and draft description for node-redis. Must be used before the final response whenever the actual task diff includes runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size. Skip only when no eligible files changed, every change is repo-meta or docs-only without behavior impact, the task is conversation-only, or the user explicitly opts out.
• pr-to-video by heygen-com. Updated September 27, 2026. Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
• pr-walkthrough by tldraw. Updated September 24, 2026. Create a narrated video walkthrough of a pull request with code slides and audio narration. Use when asked to create a PR walkthrough, PR video, or walkthrough video.
• product-feature-tech-design by digoal. Updated June 18, 2026. 输入 PRD 文档（Markdown 或 PDF），以开发架构师的角色编写字段/接口级精度的功能设计文档（Functional/Technical Design Doc），以 Markdown 格式保存到当前项目 markdown/ 目录。这份文档是开发者、reviewer、测试者三方协作的唯一契约——三者互相隔离、不能看对方的产出物（测试者看不到代码，reviewer 不参与开发），所以必须把每个功能点写到可直接落地、可直接测试的精度：接口请求/响应字段、错误码、状态机、数据模型、异常边界场景都要明确。触发条件：用户提到"功能设计文档"、"技术设计文档"、"tech design"、"functional design"、"从 PRD 生成设计文档"、"帮我把这份 PRD 转成开发文档"、"写一份给开发和测试用的设计文档"、"接口设计 + 验收标准"，或者用户上传了一份 PRD 并希望进入开发落地阶段。即使用户只说"基于这个 PRD 帮我写设计文档"或"把这个需求文档详细化成开发能直接看懂的文档"，也应立即使用本 skill。不要将本 skill 与 write-prd/write-brd 混淆——那两个 skill 输出的是面向业务评审的需求文档（WHY/WHAT 层），本 skill 输出的是面向研发落地的技术设计文档（HOW 层，包含具体字段和契约），通常以 PRD 作为输入而非从零开始的 idea。
• prose by cloudflare. Updated July 30, 2026. Style guidance for the written word. Use when asked to write code comments, commit messages, pull requests, READMEs, or documentation. Triggers might be phrases like "write a commit", "document this", or "add a README".
• prowler-docs by prowler-cloud. Updated May 27, 2026. Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.
• pull-requests by coder. Updated September 26, 2026. Guide for creating, updating, and following up on pull requests in the Coder repository. Use when asked to open a PR, update a PR, rewrite a PR description, or follow up on CI/check failures.
• python-development by microsoft. Updated July 8, 2026. Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
• python-testing by microsoft. Updated July 23, 2026. Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
• qwik-docs-development by QwikDev. Updated June 26, 2026. Use when writing, modifying, or reviewing Qwik docs content or docs-site code under packages/docs, including docs routes, MDX content, generated LLM outputs, docs build behavior, or docs-specific e2e tests.
• react-component-documentation by getsentry. Updated March 5, 2026. Create or update component documentation in Sentry's MDX stories format. Use when asked to "document a component", "add stories", "write component docs", "create an mdx file", "add a stories.mdx", or document a design system component. Generates structured MDX with live demos, accessibility guidance, and auto-generated API docs from TypeScript types.
• react-expert by reactjs. Updated July 9, 2026. Use when researching React APIs or concepts for documentation. Use when you need authoritative usage examples, caveats, warnings, or errors for a React feature.
• readme-blueprint-generator by github. Updated February 24, 2026. Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans .github/copilot directory files and copilot-instructions.md to extract project information, technology stack, architecture, development workflow, coding standards, and testing approaches while generating well-structured markdown documentation with proper formatting, cross-references, and developer-focused content.
• receipts by anthropics. Updated July 17, 2026. Generate a personal Claude Code usage & impact report ("receipts") from this machine's local session transcripts — for justifying Claude Code usage/spend to a manager, self-review, or "what have I been using this for" check-ins. Mines ~/.claude/projects locally (no extra API calls beyond one final write-up), cross-references local git history, and writes a markdown report plus a self-contained HTML receipt to your home directory. Use when the user asks for "receipts", an "impact report", "usage report", wants to "show my Claude Code activity", "prove the value of Claude Code", or runs `/receipts`.
• refactor by code-yeongyu. Updated September 29, 2026. Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code.
• release by coleam00. Updated September 25, 2026. Create a release from dev branch. Generates changelog entries from commits, bumps version, and creates a PR to main. TRIGGERS - Use this skill when user says: - "/release" - create a patch release (default) - "/release minor" - create a minor release - "/release major" - create a major release - "make a release", "cut a release", "ship it", "release to main"
• release by getsentry. Updated February 26, 2026. Publish a new Sentry JavaScript SDK release. Use when preparing a release, updating the changelog, or creating a release branch.
• release by Yeachan-Heo. Updated April 11, 2026. Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release
• release-changelog-discord-message by paperclipai. Updated August 18, 2026. Write the Discord announcement for a stable Paperclip release from the release changelog. Use when a release issue needs a copy-pasteable dotta-voice Discord post or refreshed discord_announcement document.
• release-devbox by jetify-com. Updated September 15, 2026. Cut a Devbox CLI release — recommend the version bump, write the release notes, and drive the draft or publish flow. Use when asked to release devbox, cut a version, ship 0.x.y, publish a release, or when a release is stuck partway through and needs diagnosing or resuming.
• release-easydict by tisfeng. Updated September 23, 2026. 编排 Easydict macOS 的 draft、publish、release 和 resume，整理英文 GitHub Release 内容，并处理发布后的 Issue 跟进及本地清理。不用于一般的发布流程设计讨论。
• release-generate-release-notes by mountain-loop. Updated July 1, 2026. Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links. Use when asked to run or replace the old Claude generate-release-notes command.
• release-note-writer by moeru-ai. Updated August 12, 2026. Write grouped, user-friendly release notes from git history, changelogithub output, GitHub releases, PR lists, or raw commit logs. Use when Codex needs to turn technical changelogs into English-only release notes for AIRI or similar products, including end-user highlights, developer/API notes, contributor-facing internal tooling notes, upgrade notes, or follow-up style-rule updates after wording feedback.
• release-notes by dotnet. Updated September 27, 2026. Generate and maintain .NET release notes from `features.json`. Uses `generate-changes` for authoritative shipped-change data, `generate-features` for scoring/triage, `update-existing-branch` for incremental reruns on populated branches, `editorial-scoring` for the shared rubric, `api-diff` to generate API diff reports, `api-diff-validation` for API verification, `validate-code-samples` to build and run the documented claims against the milestone build, and a multi-model `review-release-notes` pass for final editorial QA.
• release-notes by tabler. Updated September 24, 2026. Write or update the intro of a Tabler GitHub release — `.github/release-notes/<version>.md`, the part above the generated Core, Demo and Docs lists. Use whenever the user asks for release notes, a release description, a release intro or "what's new in X.Y", and proactively before a minor release when the version PR is open and the intro file is missing. Covers where the facts come from, the fixed layout (cover, headline features with a picture each, then the other changes), the image rules, the tone and how to check the result.
• release-notes by tw93. Updated September 20, 2026. Publish curated release notes for an existing Mole `V<version>` tag, including bilingual format, `gh release edit`, contributor thanks, and reactions. Use only when explicitly asked to edit or publish Mole release notes. Not for release readiness, tagging, or code review.
• release-notes by zauberzeug. Updated June 30, 2026. Write NiceGUI release notes for a milestone to release.md and a Reddit post to reddit.md. Use when asked to draft release notes or a release announcement for a given milestone/version (e.g. "write release notes for 3.14").
• release-notes-one-pager by nexu-io. Updated May 9, 2026. Release notes one-page HTML with highlights, Added, Fixed, Breaking changes, Known issues, and Upgrade note. Writes explicit "None" style sections whenever the user does not provide details.
• release-openclaw-announcement by openclaw. Updated July 23, 2026. Draft or post OpenClaw beta, stable, or extended-stable Discord release announcements from changelog, tag, registry, and validation evidence. Use when announcing a release, release candidate, or asking what users should test after an OpenClaw release.
• release-plannotator by backnotprop. Updated August 13, 2026. Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging a release, or publishing. Also trigger when the user says things like "let's ship", "prep a release", "what's changed since last release", or "time to cut a new version".
• rendercv-development-context by rendercv. Updated March 20, 2026. RenderCV codebase architecture, source code standards, and project references. Use when writing or reviewing RenderCV code.
• repo-source-code-document by open-circle. Updated March 7, 2026. Write JSDoc comments and inline documentation for Valibot library source code in /library/src/. Use when documenting schemas, actions, methods, or utilities. Covers interface documentation, function overloads, purity annotations, inline comment patterns, and terminology consistency.
• repo-website-api-create by open-circle. Updated March 17, 2026. Create new API reference pages for the Valibot website at website/src/routes/api/. Use when adding documentation for new schemas, actions, methods, or types. Covers reading source code, creating properties.ts and index.mdx files, updating menu.md, and cross-referencing related APIs.
• repo-website-api-update by open-circle. Updated March 17, 2026. Update existing API documentation pages after source code changes. Use when syncing docs with library changes like new parameters, type constraint changes, interface updates, or function renames. Covers common change patterns and verification steps.
• repo-website-guide-create by open-circle. Updated March 7, 2026. Create conceptual documentation and tutorial pages for the Valibot website at website/src/routes/guides/. Use when adding guides about schemas, pipelines, async validation, migration, or other topics. Covers directory structure, MDX templates, frontmatter, and content guidelines.
• research-paper-writing by NousResearch. Updated September 11, 2026. Write ML papers for NeurIPS/ICML/ICLR: design→submit.
• retrieving-developer-knowledge by google. Updated September 21, 2026. Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI/Gemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.
• reverse-document by Donchitos. Updated September 29, 2026. Generate missing design or architecture docs from existing implementation — works backwards from code and prototypes.
• review-and-refactor by github. Updated February 24, 2026. Review and refactor code in your project according to defined instructions
• review-docs by tldraw. Updated September 24, 2026. Review and improve tldraw SDK documentation against the voice and docs guides, scoring each article and iterating until it passes. Use when asked to review docs, audit an article in apps/docs/content, check whether documentation follows the style guide, or improve existing documentation.
• reviewing-readability by streamlit. Updated July 17, 2026. Evaluates comments, docstrings, and naming in code for readability by a developer new to the codebase — is the documentation clear and concise, and is non-obvious logic documented? Produces findings with concrete proposed rewrites (or additions where documentation is missing); the caller decides whether to apply them or present them as feedback. Use when reviewing a PR, branch, or set of changes for comment quality, naming clarity, or documentation readability. For a PR's title and description, use reviewing-pr-description instead.
• rstack-docs-writer by web-infra-dev. Updated September 12, 2026. Write or revise Markdown and MDX documentation, including READMEs, guides, and Rspress-based docs.
• screen-recording by github. Updated May 25, 2026. Create annotated animated GIF demos and screen recordings for pull requests and documentation. Covers frame capture, timing, imageio-based GIF creation, and per-frame annotation workflows.
• search-first by affaan-m. Updated March 22, 2026. 研究优先于编码的工作流程。在编写自定义代码之前，搜索现有的工具、库和模式。调用研究员代理。
• seatunnel-pr-submit by apache. Updated April 15, 2026. Draft or submit Apache SeaTunnel pull requests in English using the repository's required title and body conventions. Use when Codex needs to prepare a PR from the current branch or diff, infer a compliant `[Type][Module][SubModule] Description` title, fill the required PR template, describe what changed from git history or file diffs, or open the PR after the user provides or omits the change summary.
• segment-docs by JanDeDobbeleer. Updated August 30, 2026. Reference mapping between Oh My Posh Go segment source code and MDX documentation. Use when creating, updating, or auditing segment documentation, or when reading segment Go code and needing to understand how code constructs map to user-facing options, template properties, and type representations in docs.
• semaphore-cli-docs by semaphoreui. Updated September 14, 2026. Generate or update the CLI documentation under `docs/docs/reference/cli/` from the Cobra command code in `cli/`. Use this skill whenever the user asks to "update the CLI docs", "actualize/sync the CLI documentation", "document the CLI", "the CLI docs are out of date", "regenerate the runner/user/vault/project/migrate docs", or after adding or changing a Cobra command, subcommand, flag, alias, or required-argument check anywhere under `cli/cmd/`. Covers every command group (`users`, `projects`, `vaults`, `runner`, `migrate`) plus the operational commands (`server`, `setup`, `version`) and the global flags on the root command. Trigger when the user adds a new `*Cmd` Cobra command, a new `PersistentFlags()` call, or renames/removes a CLI flag.
• semaphore-third-party-licenses by semaphoreui. Updated May 27, 2026. Generate or update the THIRD-PARTY-LICENSES.md file for the Semaphore UI repository. Use this skill whenever the user asks to create, update, regenerate, audit, or refresh third-party license attributions, OSS notices, SBOM-style license inventories, or NOTICE files for Semaphore UI. Trigger on phrases like "third-party licenses", "OSS notices", "license attribution file", "SBOM for licenses", "NOTICE file", "audit dependencies", "licenses for go.mod / package.json", or any request that mentions compliance with customer agreements requiring an OSS components list. Also trigger when the user says "we added a new dependency, regenerate licenses". This skill knows the Semaphore UI layout (Go backend + Vue.js frontend), the project's license policy (allowlist/denylist), and the canonical output format.
• setup-darc-branch-publishing by dotnet. Updated July 20, 2026. Configure a dotnet repository branch to publish build artifacts through a Maestro channel. Use when: publishing branch artifacts to General Testing or another NuGet feed, adding a Darc default channel, enabling official builds for a branch, or setting up branch publishing flow.
• shipping-artifacts by phuryn. Updated July 3, 2026. The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
• simple-issue-description by every-app. Updated August 19, 2026. Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior. Use when a contributor asks to simplify an issue, explain what a PR is for, create the corresponding issue for a PR, remove implementation detail from a report, or invokes /simple-issue-description.
• skill-builder by yusufkaraaslan. Updated July 29, 2026. Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
• skill-builder by yusufkaraaslan. Updated May 30, 2026. Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
• skill-creator by ccusage. Updated August 1, 2026. Guides repo-local skill creation and updates. Use when adding or editing .agents/skills, root AGENTS.md routing, SKILL.md frontmatter, description trigger quality, references layout, skill scripts, or skill file line budgets.
• skill-creator by CoreBunch. Updated April 30, 2026. Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
• skill-creator by langfuse. Updated September 11, 2026. Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
• skill-creator by openai. Updated September 1, 2026. Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
• skill-creator by openai. Updated February 9, 2026. Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
• skill-creator by ryoppippi. Updated June 8, 2026. Guides repo-local skill creation and updates. Use when adding or editing .agents/skills, SKILL.md frontmatter, references, scripts, or skill routing.
• skill-creator by XiaomiMiMo. Updated August 4, 2026. Interactive guide for creating, reviewing, and improving agent skills (SKILL.md folders). Use when the user wants to build a new skill ('create a skill', 'make a skill for X', 'write a SKILL.md', 'turn this workflow into a skill'), review or improve an existing skill, fix a skill that never triggers or triggers too often, or validate a skill folder before sharing it. Do NOT use for general prompt writing, MCP server development, or editing arbitrary markdown files.
• skill-development by anthropics. Updated November 17, 2025. This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
• skill-development by anthropics. Updated February 5, 2026. This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
• skill-writer by pytorch. Updated October 28, 2025. Guide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure.
• sora by davila7. Updated February 8, 2026. Use when the user asks to generate, remix, poll, list, download, or delete Sora videos via OpenAI’s video API using the bundled CLI (`scripts/sora.py`), including requests like “generate AI video,” “Sora,” “video remix,” “download video/thumbnail/spritesheet,” and batch video generation; requires `OPENAI_API_KEY` and Sora API access.
• source-driven-development by addyosmani. Updated September 7, 2026. Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
• spec-driven-development by addyosmani. Updated September 12, 2026. Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
• spec-miner by Jeffallan. Updated April 29, 2026. Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.
• specification-writing by wanshuiyin. Updated September 6, 2026. Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
• specification-writing by wanshuiyin. Updated September 6, 2026. Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.
• submit-draft-pr by openvinotoolkit. Updated May 27, 2026. Optionally create a draft PR to the upstream repo from a local source directory. Used by coding agents when a local source path is available in the context file.
• syft-pr-review by OpenMined. Updated September 7, 2026. Write a review document for a syft pull request. Takes a PR number or URL, reads the diff, and produces a checkbox-structured summary of the flows that changed, what was added, each individual change, the tests, and any code-standards problems in the new code. Use when the user says "review PR 1234", "write me a review doc for <PR link>", or "what changed in this PR".
• technical-documentation by openclaw. Updated May 25, 2026. Build and review high-quality technical docs as well as agent instruction files in your repository.
• technical-writer by RightNow-AI. Updated February 25, 2026. Technical writing expert for API docs, READMEs, ADRs, and developer documentation
• technical-writing by cursor. Updated September 23, 2026. Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
• test-the-docs by supabase. Updated September 22, 2026. Execute runnable docs snippets and examples inside a disposable Docker Compose sandbox (runner container + local Supabase stack via `supabase start`). Use after Draft or during Self-review when asked to test the docs, fact-check CLI/SQL/code samples, or produce a verification report for a docs PR. Complements review-the-docs build and review checks; does not replace them.
• tldr-prompt by github. Updated February 24, 2026. Create tldr summaries for GitHub Copilot files (prompts, agents, instructions, collections), MCP servers, or documentation from URLs and queries.
• typescript by microsoft. Updated June 26, 2026. Use this guide when working on TypeScript changes in the FAST monorepo — authoring Web Components, writing templates and styles, working with the observable/reactive system, and testing.
• typescript by scalar. Updated March 15, 2026. Write clear, predictable TypeScript and Vue TypeScript code with strong typing, maintainability, and consistent documentation conventions.
• typescript-write by metabase. Updated September 10, 2026. Write TypeScript and JavaScript code following Metabase coding standards and best practices. Use when developing or refactoring TypeScript/JavaScript code.
• ui-component by tabler. Updated September 17, 2026. Build or extend a shared Astro component in `shared/ui/*.astro` (or `shared/components/**`) — the library that both the preview and the docs render. Use whenever the user asks for a new component, for a new prop, variant or size on an existing one, or for a refactor of a shared component. Covers the Props interface, the prop-name dictionary, class composition, slots, the `as` pitfall, and the follow-ups (demo page, docs, changeset) a new component needs.
• ui-demo by affaan-m. Updated June 11, 2026. Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
• understand-onboard by Egonex-AI. Updated August 11, 2026. Use when you need to generate an onboarding guide for new team members joining a project
• update-docs by pipecat-ai. Updated August 27, 2026. Update documentation pages to match source code changes on the current branch
• using-lynx-api-docs by lynx-family. Updated September 21, 2026. Provides authoritative guidance for Lynx development involving pages, templates, components, CSS, layouts, elements, web migration, rendering or styling bugs, and code review. Applies to *.ttml, Lynx *.tsx, and all Lynx-specific files, and requires searching the installed API docs before acting.
• verify-v8-v9-migration-docs by microsoft. Updated September 3, 2026. Generate, audit, and verify Fluent UI v8-to-v9 component migration guides. Use when asked to inventory v8 components, inspect their v8 and v9 source, produce missing per-component documentation, prove the guides are accurate or exhaustive with sealed migrations, classify documentation gaps versus agent mistakes, or publish a verification matrix.
• video-generator by holaboss-ai. Updated August 2, 2026. Create short videos and motion clips from a text description using AI video generation.
• video-transcripts by udecode. Updated June 1, 2026. Generate structured video transcripts from local files or video URLs using Gemini Files API. Use when a GitHub or Linear tracker item, comment, or attachment includes a screen recording, .mov, .mp4, or tracker-hosted video and you need a <video-transcripts> block instead of hand-written notes.
• video-transcripts by udecode. Updated June 29, 2026. Generate structured video transcripts from local files or video URLs using Gemini Files API. Use when a GitHub or Linear tracker item, comment, or attachment includes a screen recording, .mov, .mp4, or tracker-hosted video and you need a <video-transcripts> block instead of hand-written notes.
• vscode-ext-commands by github. Updated January 11, 2026. Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices
• weather-fetcher by shanraisshan. Updated April 26, 2026. Instructions for fetching current weather temperature data for Dubai, UAE from Open-Meteo API
• web-design-guidelines by calcom. Updated February 3, 2026. Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
• web-design-guidelines by davila7. Updated January 25, 2026. Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
• web-design-guidelines by moeru-ai. Updated August 4, 2026. Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
• web-design-guidelines by vercel-labs. Updated January 16, 2026. Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
• winui3-migration-guide by github. Updated March 3, 2026. UWP-to-WinUI 3 migration reference. Maps legacy UWP APIs to correct Windows App SDK equivalents with before/after code snippets. Covers namespace changes, threading (CoreDispatcher to DispatcherQueue), windowing (CoreWindow to AppWindow), dialogs, pickers, sharing, printing, background tasks, and the most common Copilot code generation mistakes.
• woocommerce-markdown by woocommerce. Updated April 16, 2026. Guidelines for creating and modifying markdown files in WooCommerce. Use when writing documentation, README files, or any markdown content.
• workflow-authoring by asgeirtj. Updated September 27, 2026. Reference for writing a Workflow tool script (script API and gotchas, resume, quality patterns, worked examples). Load before authoring a script for a workflow the user already opted into; it does not itself authorize running one.
• workflow-authoring by QwenLM. Updated September 27, 2026. Reference for writing a Workflow tool script (script API and gotchas, agent() options, pipeline() vs parallel(), verification and convergence patterns, resume, worked example). Load before authoring a script for a workflow the user already opted into; it does not itself authorize running one.
• workflow-builder by alirezarezvani. Updated May 27, 2026. Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.
• workflow-creator by QwenLM. Updated September 27, 2026. Create or update reusable Dynamic Workflow JavaScript files under .qwen/workflows. Use when the user asks to create, save, edit, or reuse a Dynamic Workflow, including requests started from the Web Shell Workflows page.
• write-api-docs by remix-run. Updated May 22, 2026. Write or audit public API docs for Remix packages. Use when adding or tightening JSDoc on exported functions, classes, interfaces, type aliases, or option objects.
• write-api-reference by vercel. Updated May 26, 2026. Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options. **Auto-activation:** User asks to write, create, or draft an API reference page. Also triggers on paths like `docs/01-app/03-api-reference/`, or keywords like "API reference", "props", "parameters", "returns", "signature". **Input sources:** Next.js source code, existing API reference pages, or user-provided specifications. **Output type:** A markdown (.mdx) API reference page with YAML frontmatter, usage example, reference section, behavior notes, and examples.
• write-architecture-docs by prisma. Updated August 31, 2026. Write or rewrite architecture subsystem docs, ADRs, and reference material for the engineering team. Use when creating, updating, or reviewing docs under docs/architecture docs/, or when the user asks you to write documentation that describes the system's design.
• write-changelog-entry by flet-dev. Updated May 1, 2026. Use when asked to add, revise, or review a changelog or release-notes entry in this repo. Inspect the existing changelog section style and the relevant PR, issue, and commit context first, then write a focused entry in the correct release section without overstating docs, tests, or chores unless they are the primary user-facing change.
• write-coding-standards-from-file by github. Updated February 24, 2026. Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt.
• write-concept by leonardomso. Updated January 6, 2026. Write or review JavaScript concept documentation pages for the 33 JavaScript Concepts project, following strict structure and quality guidelines
• write-docs by browseros-ai. Updated July 20, 2026. Write BrowserOS feature documentation. Use when the user wants to create or update documentation for a BrowserOS feature. This skill explores the codebase to understand features and writes concise Mintlify MDX docs.
• write-docs by coder. Updated September 22, 2026. Authoring workflow and guardrails for writing, moving, or restructuring Coder documentation under docs/. Points at the canonical content guidelines and prose style guide, then walks research, routing, Diátaxis mode, structure, pedagogy, and validation. Counterpart to the doc-check skill, which reviews changes for documentation needs.
• write-docs by comet-ml. Updated September 3, 2026. Authoring Fern MDX documentation pages for the Opik docs site, plus release-note and changelog routing. Use when writing or updating pages under apps/opik-documentation/documentation/fern/, drafting PR descriptions, or picking the right changelog surface.
• write-docs by PrefectHQ. Updated March 27, 2026. Comprehensive guide for writing and updating Prefect documentation. Use when creating new doc pages, updating existing docs, or working with Mintlify components and code example testing.
• write-docs by tabler. Updated September 14, 2026. Write, update, or suggest Tabler documentation pages in simple English using the current docs schema. Use whenever the user asks to create docs, edit docs, add new feature docs to an existing page, or standardize docs structure across any docs category. Also consult this skill proactively — without being asked — whenever a new visual UI component (shared/ui/*.astro), plugin, or other user-facing feature has just been added or changed and has no matching, up-to-date page under docs/content/**, since undocumented components are easy to forget about.
• write-docs by tldraw. Updated April 27, 2026. Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.
• write-guide by vercel. Updated May 26, 2026. Generates technical guides that teach real-world use cases through progressive examples. **Auto-activation:** User asks to write, create, or draft a guide or tutorial. Also use when converting feature documentation, API references, or skill knowledge into step-by-step learning content. **Input sources:** Feature skills, API documentation, existing code examples, or user-provided specifications. **Output type:** A markdown guide with YAML frontmatter, introduction, 2-4 progressive steps, and next steps section.
• write-guides by remix-run. Updated August 3, 2026. Write, rewrite, or audit Remix guide chapters in the voice of docs/guides/app/actions/docs/chapters/01-start-here.md. Use when drafting app guides, revising generated-sounding prose, tightening guide examples, preserving doc anchors, or reviewing Markdown chapters under docs/guides/app/actions/docs/chapters/.
• write-internal-docs by browseros-ai. Updated July 21, 2026. Write a doc into the private internal-docs repo as Markdown plus a rendered HTML sibling, tidy the repo's structure and index, and open a PR to browseros-ai/internal-docs.
• write-landing-docs by lobehub. Updated September 18, 2026. Use for public LobeHub website documentation under docs/**, including self-hosting, deployment, migration, and configuration guides. Excludes product changelogs and source-code API docs.
• write-leetcuda-book by xlite-dev. Updated September 24, 2026. 把 LeetCUDA kernels/interview 教学源码（base/sgemv/sgemm/hgemm/flash_attn/ffpa_attn/fp8_gemm.cuh）+ ffpa-attn CuTe sm_120 源码（csrc/cuffpa/cute fp8/fp4，commit 861d75e）写成中文 CUDA 技术书（6 Part 38 章 + CuTe 白皮书导读 + 5 附录，XeLaTeX→PDF，终态 530 页零 error）。RFC-0..N 已全部完成（2026-09-24，Part V=FP8/FP4 HGEMM 篇 ch34-35 新增，原 FP8/FP4 Attention 篇顺延为第六部分），当前任务形态 = 增补章（RFC-L/M/N 模式）/复审/勘误/图重绘。当任务涉及：撰写或修改书稿章节（chapters/chNN*.tex）、每章最小测试（book/tests/chNN_*.cu）、ffpa_attn.bench 验证、知乎资料收集与提炼、TikZ inline 图新建（主路径）与存量 drawio 图维护、源码注释核查、勾选 RFC 进度、构建/审校 book.pdf 时使用。规范源=BOOK_PLAN.md（章节结构/每章 DoD 八条/源码冻结/容差表/图片管线），执行跟踪=RFC.md（RFC-0..N 里程碑 + 各章卡片 + 图清单 + 知乎参考种子表）。
• write-memo by virattt. Updated May 24, 2026. Drafts a professional investment memo (HTML output) for a long or short equity idea, structured the way a hedge fund analyst would present a thesis to a PM. Triggers when the user asks to "write a memo", "draft an investment memo", "write up a thesis", "pitch this stock", "memo on [ticker]", "long writeup", "short writeup", or similar. Produces a 1-page HTML file at .dexter/memos/.
• write-plan by foambubble. Updated September 24, 2026. Work out how to build what a spec describes, and write it to plan.md. Use when asked to plan a spec, or when an @claude comment on a spec PR asks for the plan.
• write-prd by digoal. Updated June 9, 2026. Write a practical Product Requirements Document (PRD) from a product idea, feature concept, customer request, business problem, or rough product opportunity. Use when the user asks to write, draft, create, generate, or save a PRD, product requirements document, product spec, feature requirements, 产品需求文档, 产品方案, 需求说明, or PRD from an idea. Output a diagram-rich Markdown PRD under the current project's markdown/ directory.
• write-release-notes by tldraw. Updated May 6, 2026. Writing release notes articles for tldraw SDK releases. Use when creating new release documentation, drafting release notes from scratch, or reviewing release note quality. Provides guidance on structure, voice, and content for release files in `apps/docs/content/releases/`.
• write-ui-module-readme by remix-run. Updated April 27, 2026. Write concise module README files for `packages/ui/src/lib/*` primitives. Use when drafting or revising README docs for UI package modules like popover, press, or other first-party UI helpers, especially when the main goal is agent-friendly usage guidance and a short explanation of each exported value.
• writing-actual-docs by actualbudget. Updated June 17, 2026. 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.
• writing-comments by withastro. Updated August 13, 2026. How to write JSDoc (/** */) and inline (//) comments in the Astro codebase, for contributors reading the source — not end users. Use whenever writing or editing comments in .ts/.js source, including comments added incidentally while fixing bugs or building features. Does not cover the @docs-generated config/error reference.
• writing-docs by medusajs. Updated August 20, 2026. 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/.
• writing-docs by ngrx. Updated March 6, 2026. Doc conventions (impersonal style, formatting, Vitest in examples, structure, linking). Use when writing, editing, or reviewing guides, tutorials, or READMEs.
• writing-docs by nukeop. Updated April 4, 2026. 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".
• writing-docs by remotion-dev. Updated August 19, 2026. Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
• writing-docs-pages by handsontable. Updated June 30, 2026. 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
• writing-emdash-docs by emdash-cms. Updated September 19, 2026. Write, revise, and review EmDash documentation for technical accuracy, useful structure, house style, and natural prose. Use when working on user documentation, guides, API reference pages, migration or upgrade guides, READMEs, contributor documentation, technical specifications, or release notes in the EmDash repository, and when asked to improve, audit, de-slop, or humanize existing documentation.
• writing-kea-logics by PostHog. Updated September 5, 2026. Guide for writing or reviewing PostHog kea logic files (`*Logic.ts` / `*Logic.tsx`). Use when creating a new logic, adding actions/reducers/selectors/listeners/loaders/forms/router bindings, choosing between reducer vs selector vs cache, deciding between listeners and `kea-subscriptions`, wiring React with `useValues`/`useActions`/`BindLogic`, or onboarding to kea conventions. Read keajs.org for upstream API; this skill captures PostHog-specific conventions and idioms.
• writing-plans by jnMetaCode. Updated September 26, 2026. 当你有规格说明或需求用于多步骤任务时使用，在动手写代码之前
• writing-release-notes by stanfordnlp. Updated September 16, 2026. Drafts DSPy release notes from maintainer-selected highlights and a verified, complete Git release range. Use when preparing or updating stable, beta, or release-candidate notes.
• writing-releases by medusajs. Updated April 23, 2026. Writes GitHub release notes for Medusa releases in the established style. Use when generating a draft release description from a list of commits and PR metadata. Covers minimal patch releases, single-highlight releases, multi-feature releases, and releases with breaking changes.
• writing-spec by streamlit. Updated March 20, 2026. Writes product and tech specs for new Streamlit features. Use when designing new API commands, widgets, or significant changes that need team review before implementation.
• writing-style by pydantic. Updated September 4, 2026. How to write prose that reads like human technical documentation rather than LLM output. Use whenever writing or editing docstrings, comments, limitations/ docs, READMEs, commit messages or PR descriptions, and when prose reads as smooth, salesy or generic.
• writing-tsdocs by medusajs. Updated March 31, 2026. Adds and updates TypeDoc (TSDoc) comments to TypeScript source files in the Medusa codebase. Covers HTTP types, API routes, UI components, data models, service interfaces, JS SDK methods, abstract providers, workflow SDK functions, core-flows workflows and steps, and events. Use when adding TSDoc comments to files in packages/core/types/src/http, packages/medusa/src/api, packages/design-system/ui/src/components, packages/modules/*/src/models, packages/core/types/src, packages/core/js-sdk/src, packages/core/utils/src, packages/core/workflows-sdk/src/utils/composer, packages/core/core-flows/src, or packages/core/utils/src/core-flows/events.ts.
• writing-tutorials by medusajs. Updated April 10, 2026. Creates Medusa documentation tutorials in two phases: first builds the tutorial feature in an example project (with planning, coding, and tests), then writes the MDX documentation. Use when creating a new how-to tutorial or integration guide for the Medusa docs. Handles both feature implementation and documentation writing, but only one phase at a time.