Agent Skills

n8n:spec-driven-development

★ 195,330

by n8n-io

Keeps implementation and specs in sync. Use when working on a feature that has a spec in .agents/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes.

🧰 Not standalone — use together with n8n-io/n8n

antigravity-support

✓★ 105,779

by google-gemini

Use when the user asks questions, seeks help, or requests instructions related to installing, setting up, or migrating to Antigravity CLI. This skill provides the latest up to date details, requirements, and commands sourced from the official Antigravity CLI documentation.

🧰 Not standalone — use together with google-gemini/gemini-cli

open-source

★ 102,956

by browser-use

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 handlin

🧰 Not standalone — use together with browser-use/browser-use

cloud

★ 102,956

by browser-use

Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2 or v3), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP WebSocket connections, stealth browsers, residential proxies, CAPTCHA handling, webhooks, workspaces, skills marketplace, liveUrl streaming, pricing, or integration patterns (chat UI, subag

🧰 Not standalone — use together with browser-use/browser-use

context7-docs

✓★ 58,632

by upstash

Fetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves librar

🧰 Not standalone — use together with upstash/context7

context7-cli

✓★ 58,632

by upstash

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.

🧰 Not standalone — use together with upstash/context7

find-docs

✓★ 58,632

by upstash

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

🧰 Not standalone — use together with upstash/context7

expo-api-docs

✓★ 50,451

by expo

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.

🧰 Not standalone — use together with expo/expo

review-docs

★ 48,561

by tldraw

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

🧰 Not standalone — use together with tldraw/tldraw

addressing-pr-review-comments

★ 45,149

by streamlit

Address all valid review comments on a PR for the current branch in the streamlit/streamlit repo. Covers both inline review comments and general PR (issue) comments. Use when a PR has reviewer feedback to address, including code changes, style fixes, and documentation updates.

🧰 Not standalone — use together with streamlit/streamlit

documenting-warehouse-sources

★ 35,336

by posthog

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.

🧰 Not standalone — use together with posthog/posthog

signals

★ 35,336

by posthog

How to query the document_embeddings table for raw signal data using HogQL. Use when you need to perform semantic search over signals, fetch every signal that contributed to a specific report, or list signal types. For browsing the curated report layer (the Inbox) — listing reports, filtering by status/source, drilling into a single report by ID — use the `inbox-exploration` skill first; drop into this skill afterwards if the user wants the underlying observations.

🧰 Not standalone — use together with posthog/posthog

recipe-share-doc-and-notify

✓★ 29,425

by Google

Share a Google Docs document with edit access and email collaborators the link.

🧰 Not standalone — use together with googleworkspace/cli

gws-docs-write

✓★ 29,425

by Google

Google Docs: Append text to a document.

🧰 Not standalone — use together with googleworkspace/cli

research-agent

★ 25,837

by mastra-ai

Authoring playbook for building agents that search, read, and synthesize information into a report. Use this when the user wants an agent to research a topic, summarize sources, compare options, do competitive analysis, monitor news, generate briefs, or pull together a citation-backed report from the web or internal documents.

🧰 Not standalone — use together with mastra-ai/mastra

docs-audit

★ 25,837

by mastra-ai

Interactive documentation quality review for Mastra docs. Use when auditing, reviewing, or critiquing Mastra documentation; checking docs against source code; validating code examples, API accuracy, or property completeness; checking whether docs follow the styleguide and deterministic linters; or evaluating whether a beginner or agent can follow a doc to complete a job. This skill keeps humans in the loop with ask_user and submit_plan, then always runs an agent-build eval after approved fixes.

🧰 Not standalone — use together with mastra-ai/mastra

react-pdf

★ 15,622

by vercel

React PDF renderer for json-render. Use when generating PDF documents from JSON specs, working with @json-render/react-pdf, or rendering specs to PDF buffers/streams/files.

🧰 Not standalone — use together with vercel-labs/json-render

investigation-notes

✓★ 8,372

by cloudflare

Structured scratch tracking document for investigation state during bug hunts - prevents re-reading code, losing context, and rabbit holes; maintains external memory so you don't re-derive conclusions

🧰 Not standalone — use together with cloudflare/workerd

xcodebuildmcp-docs-release-review

✓★ 6,033

by getsentry

Use when reviewing XcodeBuildMCP documentation, CLI command references, website manifest generation, changelog, release notes, and release script changes.

🧰 Not standalone — use together with getsentry/xcodebuildmcp

contributing

✓★ 4,910

by cloudflare

Use when contributing to the Cloudflare Docs repository — writing or editing documentation pages, choosing content types or components, adding changelog entries, reviewing docs, or learning how to contribute.

🧰 Not standalone — use together with cloudflare/cloudflare-docs

docs-impact-architect

✓★ 3,123

by microsoft

Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume / produce / govern) and the persona ramps as hard constraints.

🧰 Not standalone — use together with microsoft/apm

docs-corpus-audit

✓★ 3,123

by microsoft

Use this skill to run a holistic regrounding pass on the entire microsoft/apm documentation corpus against current source code, page-by-page, and emit surgical fixes for stale claims. Activate when the maintainer wants a WHOLE-CORPUS audit (not per-PR review) -- typical triggers include "audit the docs", "reground the corpus", "check every page against code", "pre-release docs sweep", "the docs have drifted everywhere", or "we just reshaped the TOC, find dead links". Wave-batched and S7-verified

🧰 Not standalone — use together with microsoft/apm

docs-grounding-verifier

✓★ 3,123

by microsoft

Use this skill to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code. Activate when you have specific pages to check for factual accuracy -- not when sweeping a whole corpus (use docs-corpus-audit for that) and not when triaging a PR diff (use docs-sync for that). Trigger nouns: "is this doc accurate", "verify the page against the code", "fact-check this section", "any claims that drifted from source", "fact-checking", "grounding audit", "drift hunt",

🧰 Not standalone — use together with microsoft/apm

docs-sync

✓★ 3,123

by microsoft

Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent drift between code and docs. Classifies impact as no-change, in-place edit (one to a few paragraphs), or structural change (new page or TOC reshape), then orchestrates a CDO + doc-w

🧰 Not standalone — use together with microsoft/apm

docs-impact-classifier

✓★ 3,123

by microsoft

Use this skill to classify the documentation impact of a pull request diff, returning one of three verdicts -- no-change, in-place edit, or structural change -- with bounded LLM cost. Activate as a sibling skill of docs-sync; the orchestrator calls this first, before any panel spawn, to keep cost floor at 1 LLM call when no docs work is needed. Reads .apm/docs-index.yml as the corpus map; never reads the full corpus.

🧰 Not standalone — use together with microsoft/apm

index-knowledge

✓★ 2,769

by cloudflare

Generate hierarchical AGENTS.md knowledge base for a codebase. Creates root + complexity-scored subdirectory documentation.

🧰 Not standalone — use together with cloudflare/kumo

write-changelog

✓★ 2,599

by microsoft

Write a CHANGELOG.md entry for a new extension release. Use when: writing changelog, updating changelog, adding release notes, preparing a release, documenting milestone changes. Requires a milestone name and extension version number.

🧰 Not standalone — use together with microsoft/vscode-pull-request-github

grill-with-docs

★ 950

by sanity-io

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

🧰 Not standalone — use together with sanity-io/next-sanity

site-explorer

✓★ 926

by microsoft

Browse and discover SharePoint sites, lists, document libraries, and file contents — navigate your SharePoint world without leaving the CLI.

🧰 Not standalone — use together with microsoft/work-iq

building-components

✓★ 776

by vercel

Guide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm/registry, or writing component documentation.

🧰 Not standalone — use together with vercel/components.build