Agent Skills

vitest

✓★ 105,783

by supabase

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

🧰 Not standalone — use together with supabase/supabase

vercel-composition-patterns

✓★ 105,783

by supabase

React composition patterns that scale. Use when refactoring components with

🧰 Not standalone — use together with supabase/supabase

context7-mcp

✓★ 58,632

by upstash

This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.

🧰 Not standalone — use together with upstash/context7

shepherd-pr

★ 48,561

by tldraw

Keep an eye on this PR. Review and resolve pull request comments and fix build failures autonomously. Use when asked to review PR feedback, address reviewer comments, fix CI failures, resolve PR threads, or handle PR maintenance tasks like "review PR comments", "fix the build", "address PR feedback", "clean up PR", or "resolve comments". Handles comment triage (resolve false positives, fix trivial issues, flag complex ones), build/lint/type errors, and e2e snapshot updates.

🧰 Not standalone — use together with tldraw/tldraw

turborepo

✓★ 30,654

by vercel

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

🧰 Not standalone — use together with vercel/turborepo

turborepo

★ 30,489

by langfuse

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

🧰 Not standalone — use together with langfuse/langfuse

adr-skill

✓★ 25,366

by vercel

Create and maintain Architecture Decision Records (ADRs) optimized for agentic coding workflows. Use when you need to propose, write, update, accept/reject, deprecate, or supersede an ADR; bootstrap an adr folder and index; consult existing ADRs before implementing changes; or enforce ADR conventions. This skill uses Socratic questioning to capture intent before drafting, and validates output against an agent-readiness checklist.

🧰 Not standalone — use together with vercel/ai

tdd

★ 6,200

by sanity-io

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

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

driver-test-runner

★ 5,667

by rivet-dev

Methodically run the RivetKit driver test suite file by file across the native (NAPI) and wasm runtimes, tracking progress in ~/.agents/notes/driver-test-progress.md. Use when you need to validate the driver test suite after changes, bring up a new driver, or debug test failures systematically.

🧰 Not standalone — use together with rivet-dev/rivet

openspec-apply-change

★ 5,667

by rivet-dev

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

🧰 Not standalone — use together with rivet-dev/rivet

openspec-bulk-archive-change

★ 5,667

by rivet-dev

Archive multiple completed changes at once. Use when archiving several parallel changes.

🧰 Not standalone — use together with rivet-dev/rivet

openspec-continue-change

★ 5,667

by rivet-dev

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

🧰 Not standalone — use together with rivet-dev/rivet

graphite-is-being-a-piece-of-shit-just-merge-my-stack

★ 5,667

by rivet-dev

🧰 Not standalone — use together with rivet-dev/rivet

openspec-ff-change

★ 5,667

by rivet-dev

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

🧰 Not standalone — use together with rivet-dev/rivet

openspec-explore

★ 5,667

by rivet-dev

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

🧰 Not standalone — use together with rivet-dev/rivet

openspec-onboard

★ 5,667

by rivet-dev

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

🧰 Not standalone — use together with rivet-dev/rivet

openspec-verify-change

★ 5,667

by rivet-dev

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

🧰 Not standalone — use together with rivet-dev/rivet

sanity-check

★ 5,667

by rivet-dev

Run an E2E smoke test that installs rivetkit packages from npm in an isolated temp project, starts the hello-world counter actor, then verifies both HTTP actions and WebSocket actions + events work end-to-end. Use when the user asks to sanity check, smoke test, or verify a rivetkit release/preview-publish works.

🧰 Not standalone — use together with rivet-dev/rivet

stack-merge

★ 5,667

by rivet-dev

Bulk-merge a Graphite stack into main via admin-bypass fast-forward push. Replaces the Graphite merge queue for rivet-dev/rivet. Invoke when the user says "merge the stack at <branch>", "ship everything through <branch>", "bulk-merge up to <branch>", "fast-forward main to <branch>", or any request to land multiple stacked PRs at once in one shot. Requires repo admin permissions (bypasses branch protection), Graphite (gt) CLI, and GitHub (gh) CLI. After the FF push, closes all in-scope PRs explic

🧰 Not standalone — use together with rivet-dev/rivet

openspec-sync-specs

★ 5,667

by rivet-dev

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

🧰 Not standalone — use together with rivet-dev/rivet

openspec-new-change

★ 5,667

by rivet-dev

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

🧰 Not standalone — use together with rivet-dev/rivet

openspec-archive-change

★ 5,667

by rivet-dev

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

🧰 Not standalone — use together with rivet-dev/rivet

turborepo

★ 950

by sanity-io

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

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

claimable-postgres

✓★ 617

by neondatabase

Provision instant temporary Postgres databases via Claimable Postgres by Neon (pg.new) with no login, signup, or credit card. Use when users ask for a quick Postgres environment, a throwaway DATABASE_URL for prototyping/tests, or "just give me a DB now". Triggers include: "quick postgres", "temporary postgres", "no signup database", "no credit card database", "instant DATABASE_URL".

🧰 Not standalone — use together with neondatabase/mcp-server-neon

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

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

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

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

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

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