Agent Skills

architecture-review

✓★ 347

by sentry

Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.

🧰 Not standalone — use together with getsentry/warden

test-skill-a

✓★ 347

by getsentry

Test skill A for integration tests

🧰 Not standalone — use together with getsentry/warden

zapier-explore

✓★ 343

by zapier

Explore what Zapier MCP can do for the user — interview them about their role and the apps they live in, suggest specific use cases as on-demand prompts, then walk them through enabling the actions to make those use cases real. The natural next step after `zapier-demo`. Use when the user asks "what else can Zapier do for me", "set up more tools", "add a starter pack for my role", "what should I enable next", "suggest workflows", "help me figure out what to do with Zapier", "I don't know where to

🧰 Not standalone — use together with zapier/zapier-mcp

zapier-onboard

✓★ 343

by zapier

Onboard a new user to Zapier MCP — introduce what it can do, walk through authentication, and route into the right flow based on the state of their setup. Use when getting started, troubleshooting connection issues, or when the user asks "what is Zapier MCP", "how do I get started with Zapier", "set me up", "what can I do with Zapier", or "tell me about Zapier".

🧰 Not standalone — use together with zapier/zapier-mcp

zapier-demo

✓★ 343

by zapier

Walk a new user through setting up their first Zapier action and running it live — the smallest possible win. Asks what app they use, recommends one read action to enable, guides them to mcp.zapier.com to add it, then demonstrates it working in the same chat. Use when the user asks "show me how Zapier works", "set up my first action", "give me a quick demo", "I want to try it", "what's the fastest way to see this work", "minimal setup", "hello world", or "smallest example".

🧰 Not standalone — use together with zapier/zapier-mcp

zapier-status

✓★ 343

by zapier

Check the health of your Zapier MCP setup. Three modes — health check (dashboard view), audit (find waste and duplicates), diagnose (systematic troubleshooting). Use when asking "is my MCP working?", "check my tools", "audit my setup", "what's broken?", or "zapier status".

🧰 Not standalone — use together with zapier/zapier-mcp

procedure-coding

✓★ 332

by anthropics

Assign CPT and HCPCS Level II procedure codes from clinical documentation the way a professional coder builds the claim. Use when users say "code this encounter for procedures", "what CPT codes apply", "assign HCPCS codes", "code this op note", or when turning visit notes or operative reports into claim-ready procedure codes.

🧰 Not standalone — use together with anthropics/healthcare

contracts

✓★ 332

by anthropics

Answer a question across a corpus of contract documents with verified citations. Use when the user asks what a contract says, which contracts have a clause, what changed between amendments, or any question that needs reading and citing across a set of contract files. The corpus must be on the local filesystem (see README).

🧰 Not standalone — use together with anthropics/healthcare

fraud-detection

✓★ 332

by anthropics

Screen a Medicare/Medicaid claims corpus for fraud, waste, and abuse and produce ranked, fully-cited investigation referrals for an SIU / program-integrity team. Use when asked to run a fraud sweep, screen claims for FWA, find billing anomalies, or generate investigation referrals over a claims dataset.

🧰 Not standalone — use together with anthropics/healthcare

fhir-developer-skill

✓★ 332

by anthropic

FHIR API development guide for building healthcare endpoints. Use when: (1) Creating FHIR REST endpoints (Patient, Observation, Encounter, Condition, MedicationRequest), (2) Validating FHIR resources and returning proper HTTP status codes and error responses, (3) Implementing SMART on FHIR authorization and OAuth scopes, (4) Working with Bundles, transactions, batch operations, or search pagination. Covers FHIR R4 resource structures, required fields, value sets (status codes, gender, intent), c

🧰 Not standalone — use together with anthropics/healthcare

prior-auth-review-skill

✓★ 332

by anthropic

Automate payer review of prior authorization (PA) requests. This skill should be used when users say "Review this PA request", "Process prior authorization for [procedure]", "Assess medical necessity", "Generate PA decision", or when processing clinical documentation for coverage policy validation and authorization decisions.

🧰 Not standalone — use together with anthropics/healthcare

doc-extract

✓★ 332

by anthropics

Extract plain text from a document file - PDF, DOCX, XLSX, PPTX, RTF, or plain text/markdown/HTML. Use when a binary document needs to be turned into text, for example a contract PDF or an EHR DocumentReference attachment. Other skills (contracts, fhir) invoke scripts/extract.ts directly.

🧰 Not standalone — use together with anthropics/healthcare

fhir

✓★ 332

by anthropics

Connect to a hospital's FHIR R4 server (Epic, Oracle Health/Cerner, MEDITECH, athenahealth, or any SMART-on-FHIR endpoint), pull a patient's clinical data and notes, and extract structured findings. Use when users say "connect to the EHR", "connect to Epic/Cerner", "pull notes for patient X", "what do the last 6 months of notes say about Y", or any task that starts from a live EHR rather than pasted text.

🧰 Not standalone — use together with anthropics/healthcare

clinical-note-extract-skill

✓★ 332

by anthropics

Extract structured data from clinical notes with span-level provenance and null-safety. Use when users say "extract [variables] from this note", "abstract this chart", "pull structured data from these notes", "what does this note say about [field]", or when building a chart-abstraction, registry, or cohort dataset from unstructured clinical text.

🧰 Not standalone — use together with anthropics/healthcare

icd10-cm-skill

✓★ 332

by anthropics

Extract billable ICD-10-CM diagnosis codes from a clinical note the way a professional coder builds the claim. Use when users say "code this encounter", "assign ICD-10 codes", "what diagnosis codes apply", "code this chart", or when turning clinical documentation into claim-ready diagnosis codes.

🧰 Not standalone — use together with anthropics/healthcare

clinical-trial-protocol-skill

✓★ 332

by anthropic

Generate clinical trial protocols for medical devices or drugs. This skill should be used when users say "Create a clinical trial protocol", "Generate protocol for [device/drug]", "Help me design a clinical study", "Research similar trials for [intervention]", or when developing FDA submission documentation for investigational products.

🧰 Not standalone — use together with anthropics/healthcare

clickhouse-js-node-coding

✓★ 321

by clickhouse

Write idiomatic application code with the ClickHouse Node.js client (`@clickhouse/client`). Use this skill whenever a user is *building* against the Node.js client — configuring the client, pinging, inserting rows in JSON or raw formats, selecting and parsing results, binding query parameters, managing sessions and temporary tables, working with data types or customizing JSON parsing. Do NOT use for browser/Web client code.

🧰 Not standalone — use together with clickhouse/clickhouse-js

release

✓★ 321

by clickhouse

Drive a package release of `ClickHouse/clickhouse-js` end to end: bump the version, sync the protected `release` branch from `main`, watch the npm publish (which is gated by a manual approval on the `npm-publish` environment), and create the GitHub Release from the CHANGELOG. Use this skill whenever the task is to "release", "cut a release", "publish a new version", or "ship" one of the packages: `@clickhouse/client` (Node.js), `@clickhouse/client-web` (Web), `@clickhouse/client-common` (depreca

🧰 Not standalone — use together with clickhouse/clickhouse-js

clickhouse-js-node-troubleshooting

✓★ 321

by clickhouse

Troubleshoot and resolve common issues with the ClickHouse Node.js client (@clickhouse/client). Use this skill whenever a user reports errors, unexpected behavior, or configuration questions involving the Node.js client specifically — including socket hang-up errors, Keep-Alive problems, stream handling issues, data type mismatches, read-only user restrictions, proxy/TLS setup problems, or long-running query timeouts. Trigger even when the user hasn't precisely named the issue; vague symptoms li

🧰 Not standalone — use together with clickhouse/clickhouse-js

typescript-lsp

✓★ 321

by clickhouse

Use the TypeScript language server (`typescript-language-server`) for precise code intelligence in the `clickhouse-js` repository: go-to-definition, find references, hover (type signatures and JSDoc, including `@deprecated` info), workspace-wide symbol search, completions, and per-file type diagnostics. Prefer this over grep when you need to resolve a symbol's actual definition, find all usages of an exported API, or inspect inferred types across the `packages/*` workspaces. The server is preins

🧰 Not standalone — use together with clickhouse/clickhouse-js

clickhouse-js-node-rowbinary

✓★ 321

by clickhouse

Generate TypeScript/JavaScript code that reads/decodes AND writes/encodes ClickHouse RowBinary streams for the ClickHouse HTTP server. Use this skill whenever a user wants to parse or produce `RowBinary`, `RowBinaryWithNames`, or `RowBinaryWithNamesAndTypes`. Node.js only, doesn't cover browsers.

🧰 Not standalone — use together with clickhouse/clickhouse-js

fix-release-pr

✓★ 321

by clickhouse

Fix CI failures and address code-review comments on a pull request that targets the protected `release` branch of `ClickHouse/clickhouse-js`. Release PRs are snapshots of `main` (their head branch is usually `main` itself) and cannot be edited directly — branch protection blocks pushing fixes onto them. Use this skill whenever the work is "fix the CI / address the review comments on PR #N" and that PR's base branch is `release`: it routes the fix through a separate PR to `main`, then closes the

🧰 Not standalone — use together with clickhouse/clickhouse-js

github-code

✓★ 276

by getsentry

Work with GitHub repositories, source code, branches, commits, pushes, pull requests, reviews, diffs, and CI runs. Use for repo implementation tasks, source-code investigation, cloning/fetching, branch and push workflows, PR creation, PR updates, PR review feedback, and GitHub Actions checks. Prefer this skill for repository and code tasks even when the repo concerns Sentry products.

🧰 Not standalone — use together with getsentry/junior

source-handbook

✓★ 276

by getsentry

Check bundled source handbook files for capability, policy, or implementation verification questions. Use when users ask to double-check or verify what the internal/source handbook says.

🧰 Not standalone — use together with getsentry/junior

agent-browser

✓★ 276

by getsentry

Automate websites with the agent-browser CLI for navigation, form flows, screenshots, extraction, and repeatable browser tasks. Use when users ask to interact with web apps, gather evidence from pages, or run browser-based QA steps.

🧰 Not standalone — use together with getsentry/junior

vercel-queues

✓★ 276

by sentry

Build and operate Vercel Queues with @vercel/queue across push and poll consumers. Use when users ask about "vercel queues", "@vercel/queue", "queue/v2beta", "handleCallback", "PollingQueueClient", "receive", queue retries, visibility timeouts, idempotency keys, or queue region routing.

🧰 Not standalone — use together with getsentry/junior

resilient-working-directory

✓★ 276

by getsentry

Use for /resilient-working-directory eval requests that verify command interruption recovery.

🧰 Not standalone — use together with getsentry/junior

eval-mcp

✓★ 276

by getsentry

Use for `/eval-mcp` requests that need the eval MCP handbook lookup.

🧰 Not standalone — use together with getsentry/junior

weather-lookup

✓★ 276

by getsentry

Look up current weather conditions for a city. Use when users ask about weather, temperature, or forecast for a location.

🧰 Not standalone — use together with getsentry/junior

vercel

✓★ 276

by getsentry

Query Vercel deployments, build logs, runtime logs, and deployment status through the Vercel CLI. Use when users ask to debug Vercel deployments, inspect failed builds, fetch production or preview runtime logs, find a deployment for a project or commit SHA, or investigate Vercel-hosted app errors. Do not use it for deploying, rolling back, changing project settings, domains, env vars, caches, storage, or any other Vercel mutation.

🧰 Not standalone — use together with getsentry/junior