Claude skills and agent skills

VercelSkill

building-components

vercel/components.build/skills/building-components/SKILL.md

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.

VercelReads credentialsSkill

flags-sdk

vercel/flags/skills/flags-sdk/SKILL.md

Implement feature flags in Next.js or SvelteKit code with the Flags SDK (`flags` npm package). Use when installing or configuring the SDK, declaring flags with `flag()`, setting up Project Connections, wiring a provider adapter (`@flags-sdk/vercel`, Statsig, LaunchDarkly, PostHog, GrowthBook, Global Config, OpenFeature, Split, Flagsmith, Reflag, Optimizely, or custom), using `identify`, `dedupe`, or `evaluate`, keeping pages static with precompute, setting up Flags Explorer and the Vercel Toolbar, or encrypting flag values. Triggers: `flags/next`, `flags/sveltekit`, `flags/react`, `@flags-sdk/*`, `vercelAdapter`, precompute. For planning a flag, for Vercel Flags rollouts, experiments, and the `vercel flags` CLI, or for other frameworks, use the `vercel-flags` skill.

VercelReads credentialsSkill

vercel-flags

vercel/flags/skills/vercel-flags/SKILL.md

Feature flags, A/B tests, and gradual rollouts with Vercel Flags, in any app or framework. Use whenever the user is planning, adding, changing, or cleaning up a feature flag, toggle, kill switch, experiment, percentage rollout, or targeting rule, or wants to gate or hide a feature for some users, even before a library or provider is chosen. Covers choosing an integration (Flags SDK, `@vercel/flags-core`, OpenFeature), the Vercel dashboard, the `vercel flags` CLI (create, inspect, set, split, rollout, rules, segments, evaluations, archive, connections), Project Connections, OIDC vs SDK keys, `FLAGS_SECRET`, and Flags Explorer overrides. For `flag()` declarations, adapters, precompute, and the Flags Explorer endpoint in Next.js or SvelteKit code, load the `flags-sdk` skill.

VercelReads credentialsSkill

v0

vercel/v0-sdk/packages/create-v0-sdk-app/templates/v0/SKILL.md

Build and modify applications that use the v0 API, TypeScript SDK, and React package.

VercelDeletes or force-pushesSkill

benchmark-agents

vercel/vercel-plugin/.claude/skills/benchmark-agents/SKILL.md

Advanced AI agent benchmark scenarios that push Vercel's cutting-edge platform features — Workflow SDK, AI Gateway, MCP, Chat SDK, Queues, Flags, Sandbox, and multi-agent orchestration. Designed to stress-test skill injection for complex, multi-system builds.

VercelDeletes or force-pushesSkill

benchmark-e2e

vercel/vercel-plugin/.claude/skills/benchmark-e2e/SKILL.md

End-to-end benchmark suite for vercel-plugin. Runs realistic projects through skill injection, launches dev servers, verifies everything works, analyzes conversation logs, and produces an improvement report for overnight self-improvement loops.

VercelReads credentialsSkill

benchmark-sandbox

vercel/vercel-plugin/.claude/skills/benchmark-sandbox/SKILL.md

Run vercel-plugin eval scenarios in Vercel Sandboxes instead of local WezTerm panels. Provisions ephemeral microVMs with Claude Code + plugin pre-installed, runs benchmark prompts, extracts hook artifacts, and produces coverage reports.

VercelDeletes or force-pushesSkill

benchmark-testing

vercel/vercel-plugin/.claude/skills/benchmark-testing/SKILL.md

Create and launch benchmark test projects to exercise vercel-plugin skill injection across realistic scenarios. Sets up isolated directories, installs the plugin, and spawns WezTerm panes running Claude Code with crafted prompts.

VercelSkill

plugin-audit

vercel/vercel-plugin/.claude/skills/plugin-audit/SKILL.md

Audit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, identifies pattern coverage gaps, and checks plugin cache staleness. Use when asked to audit, test, or investigate plugin skill injection on a real project.

VercelSkill

release

vercel/vercel-plugin/.claude/skills/release/SKILL.md

Release vercel-plugin — run gates, bump version, generate artifacts, commit, and push. Use when asked to "release", "ship", "bump and push", or "cut a release".

Often used withcreate-agent-adapter·documentation-consistency

VercelDeletes or force-pushesSkill

vercel-plugin-eval

vercel/vercel-plugin/.claude/skills/vercel-plugin-eval/SKILL.md

Run live eval sessions against the vercel-plugin to verify hook behavior, skill injection, dedup correctness, and coverage. Launches real Claude Code sessions via WezTerm, monitors debug logs, and produces a structured coverage report.

VercelReads credentialsSkill

access-protected-vercel-deployment

vercel/vercel-plugin/skills/access-protected-vercel-deployment/SKILL.md

Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection. Use when curl, agent-browser, Playwright, or another automated request reaches a Vercel login or protection page; when a protected preview or production URL returns 401 or 403; when TRUSTED_SOURCES_ENVIRONMENT_MISMATCH appears; or when choosing between `vercel curl` and the `x-vercel-trusted-oidc-idp-token` header.

VercelReads credentialsSkill

ai-gateway

vercel/vercel-plugin/skills/ai-gateway/SKILL.md

Vercel AI Gateway guidance for setup, model discovery, authentication, routing, fallbacks, virtual models, evaluation models, BYOK, budgets, spend reporting, observability, compatible APIs, and coding-agent configuration. Use when adding AI Gateway to an app, migrating provider calls, choosing models or providers, centralizing model configuration, evaluating application state, debugging gateway requests, or running `vercel ai-gateway` commands.

VercelReads credentialsSkill

ai-sdk

vercel/vercel-plugin/skills/ai-sdk/SKILL.md

Vercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.

VercelReads credentialsSkill

auth

vercel/vercel-plugin/skills/auth/SKILL.md

Authentication integration guidance — Clerk (native Vercel Marketplace), Better Auth, Descope, and Auth0 setup for Next.js applications, plus Sign in with Vercel, Vercel Passport, and Vercel KMS. Covers server config, route handlers, proxy.ts auth patterns, sign-in/sign-up flows, and Marketplace provisioning. Use when implementing user authentication, sessions, protected routes, or protecting deployments.

VercelReads credentialsSkill

bootstrap

vercel/vercel-plugin/skills/bootstrap/SKILL.md

Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations). Use when setting up or repairing a repository so linking, environment provisioning, env pulls, and first-run db/dev commands happen in the correct safe order.

VercelSkill

build-agents

vercel/vercel-plugin/skills/build-agents/SKILL.md

Default guidance for building AI agents. Use for generic requests to build, create, scaffold, design, architect, or implement an AI agent, agent app, tool-calling agent, durable agent, multi-agent system, or scheduled agent.

VercelSkill

cdn-caching

vercel/vercel-plugin/skills/cdn-caching/SKILL.md

Debug Vercel CDN caching — cache hit rate, stale content, revalidation behavior, ISR + PPR, per-request cache reasons (cacheReason) and PPR state (ppr_state), and costs.

VercelReads credentialsSkill

chat-sdk

vercel/vercel-plugin/skills/chat-sdk/SKILL.md

Vercel Chat SDK expert guidance. Use when building multi-platform chat bots — Slack, Telegram, Microsoft Teams, Discord, Google Chat, GitHub, Linear — with a single codebase. Covers the Chat class, adapters, threads, messages, cards, modals, streaming, state management, and webhook setup.

VercelSkill

create-a-backend

vercel/vercel-plugin/skills/create-a-backend/SKILL.md

Backend architecture guidance. Use when planning, building, or migrating an API or backend; choosing between Functions, Services, containers, Daemons, Workflow, Queues, and Marketplace databases; or selecting a supported backend framework or runtime.