Agent Skills
Instruction packs that give your AI agent know-how — some work anywhere, some only with the tool they came with.
✦ Standalone skills3,373
Self-contained. Install one into any project and it works on its own — no other software needed.
🧰 Tool add-ons952
Come bundled with a specific tool and only work together with it — they teach your agent how to operate that tool.
✓ Official
48 companiesPublished by the companies themselves — pick one to see everything they ship.
openai5 skills
anthropics10 skills
google-gemini17 skills
microsoft92 skills
github8 skills
facebook4 skills
react1 skill
coinbase6 skills
stripe7 skills
shopify2 skills
cloudflare11 skills
vercel22 skills
vercel-labs63 skills
supabase4 skills
huggingface6 skills
pytorch2 skills
flutter3 skills
DataDog11 skills
getsentry89 skills
brave2 skills
googleworkspace95 skills
google-labs-code3 skills
genkit-ai9 skills
expo2 skills
n8n-io21 skills
sveltejs3 skills
nuxt1 skill
shadcn-ui2 skills
bitwarden2 skills
automattic14 skills
larksuite35 skills
browserbase1 skill
browser-use9 skills
apify2 skills
clickhouse8 skills
neondatabase11 skills
upstash10 skills
posthog165 skills
langfuse2 skills
resend3 skills
sanity-io24 skills
streamlit4 skills
remotion-dev3 skills
tldraw7 skills
apollographql1 skill
mastra-ai28 skills
triggerdotdev1 skill
mcp-use4 skillsOfficial
427 tool add-onsgithub-script
✓★ 4,723by github
Write robust JavaScript for GitHub Actions github-script steps.
🧰 Not standalone — use together with github/gh-aw
github-issue-query
✓★ 4,723by github
Query GitHub issues with jq filtering and reusable selectors.
🧰 Not standalone — use together with github/gh-aw
reporting
✓★ 4,723by github
Format reports with HTML details/summary blocks for readable output.
🧰 Not standalone — use together with github/gh-aw
jqschema
✓★ 4,723by github
Infer JSON structure and types with jq-based schema discovery.
🧰 Not standalone — use together with github/gh-aw
github-pr-query
✓★ 4,723by github
Query GitHub pull requests with jq filtering and reusable selectors.
🧰 Not standalone — use together with github/gh-aw
github-discussion-query
✓★ 4,723by github
Query GitHub discussions with jq filtering and reusable selectors.
🧰 Not standalone — use together with github/gh-aw
review
✓★ 3,392by brave
Review code for quality, root cause analysis, and fix confidence. Supports PR
🧰 Not standalone — use together with brave/brave-core
pr
✓★ 3,392by brave
Create a pull request for the current branch using `gh`.
🧰 Not standalone — use together with brave/brave-core
oss-growth
✓★ 3,123by microsoft
Activate for OSS adoption work -- README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles -- and any update to the maintained growth strategy at WIP/growth-strategy.md.
🧰 Not standalone — use together with microsoft/apm
apm-spec-guardian
✓★ 3,123by microsoft
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-*.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/*.schema.json), or the conformance fixture seed (tests/fixtures/spec-conformance/**). The panel fans out to four spec-ecosystem reviewers (swagger-openapi-editor, oci-distribution-editor, pkgmgr-registry-contract-editor, w3c-tag-architect), each running
🧰 Not standalone — use together with microsoft/apm
docs-corpus-audit
✓★ 3,123by 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,123by 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-impact-architect
✓★ 3,123by 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-sync
✓★ 3,123by 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
supply-chain-security
✓★ 3,123by microsoft
Activate when reviewing or modifying dependency resolution, lockfile schema, package downloaders, signature/integrity checks, file integration cleanup, or anything that could expose APM to dependency confusion, typosquatting, malicious packages, or token leakage.
🧰 Not standalone — use together with microsoft/apm
docs-impact-localizer
✓★ 3,123by microsoft
Use this skill to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel. Activate after docs-impact-classifier returns verdict in_place; reads the candidate page list, fetches the actual page contents, narrows scope to specific sections within each page, and emits the per-page task brief the panel fans out against.
🧰 Not standalone — use together with microsoft/apm
apm-strategy
✓★ 3,123by microsoft
Activate for changes to project positioning, release communication, community-facing artifacts, or breaking-change decisions in microsoft/apm. Triggers on README, MANIFESTO, PRD, CHANGELOG, release workflows, and issue templates.
🧰 Not standalone — use together with microsoft/apm
apm-usage
✓★ 3,123by microsoft
Activate when the user asks about APM (Agent Package Manager): installing, configuring, authoring, or troubleshooting AI-agent packages, dependencies, compilation, MCP servers, policy, or any `apm` CLI command.
🧰 Not standalone — use together with microsoft/apm
example-skill
✓★ 3,123by microsoft
An example skill from the mock plugin
🧰 Not standalone — use together with microsoft/apm
hello
✓★ 3,123by microsoft
🧰 Not standalone — use together with microsoft/apm
placeholder
✓★ 3,123by microsoft
🧰 Not standalone — use together with microsoft/apm
cut-release
✓★ 3,123by microsoft
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR (drop internal-only churn, consolidate duplicates), bump pyproject.toml + uv.lock, run the CI-mirror lint chain, and open the release PR. Activate on "ship a release", "cut v0.x", "rele
🧰 Not standalone — use together with microsoft/apm
cli-logging-ux
✓★ 3,123by microsoft
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (_rich_success, _rich_warning, _rich_error, _rich_info, _rich_echo), DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output — even if the user doesn't mention "logging" or "UX" explicitly.
🧰 Not standalone — use together with microsoft/apm
devx-ux
✓★ 3,123by microsoft
Activate when designing or modifying CLI command surfaces, command help text, install/init/run flows, error wording, or first-run experience in the APM CLI -- even when the user does not say "UX" explicitly.
🧰 Not standalone — use together with microsoft/apm
python-architecture
✓★ 3,123by microsoft
Activate when creating new modules, refactoring class hierarchies, introducing design patterns, or making changes spanning 3+ files in the APM CLI codebase.
🧰 Not standalone — use together with microsoft/apm
docs-impact-classifier
✓★ 3,123by 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
{{project_name}}
✓★ 3,123by microsoft
{{description}}
🧰 Not standalone — use together with microsoft/apm
Test Skill
✓★ 3,123by microsoft
A test skill from a marketplace plugin
🧰 Not standalone — use together with microsoft/apm
index-knowledge
✓★ 2,769by cloudflare
Generate hierarchical AGENTS.md knowledge base for a codebase. Creates root + complexity-scored subdirectory documentation.
🧰 Not standalone — use together with cloudflare/kumo
summarize-github-issue-pr-notification
✓★ 2,599by microsoft
Summarizes the content of a GitHub issue, pull request (PR), or notification, providing a concise overview of the main points and key details. ALWAYS use the skill when asked to summarize an issue, PR, or notification.
🧰 Not standalone — use together with microsoft/vscode-pull-request-github