Agent Skills

deepsec

★ 1,542

by vercel-labs

Run DeepSec against a Vercel project checkout from dev3000. Use for one-click DeepSec setup, project context bootstrapping, bounded first-pass processing, and report generation.

🧰 Not standalone — use together with vercel-labs/dev3000

d3k

★ 1,542

by vercel

Bootstrap d3k in standalone AI apps (Codex, Cursor, Claude Code): detect/install dev3000, start d3k as the runtime, and use unified logs plus d3k-owned browser/session control instead of running npm/bun dev directly.

🧰 Not standalone — use together with vercel-labs/dev3000

analyze-bundle

★ 1,542

by vercel

Convert Next.js bundle analyzer data to NDJSON and explore it

🧰 Not standalone — use together with vercel-labs/dev3000

stripe

★ 1,494

by vercel

Emulated Stripe API for local development and testing. Use when the user needs to process payments locally, test checkout flows, create customers, manage products and prices, handle payment intents, work with webhooks, or use the Stripe SDK without hitting real Stripe servers. Triggers include "Stripe API", "emulate Stripe", "test payments locally", "checkout flow", "payment intent", "Stripe webhook", "Stripe SDK", "STRIPE_API_KEY", or any task requiring a local Stripe API.

🧰 Not standalone — use together with vercel-labs/emulate

slack

★ 1,494

by vercel

Emulated Slack API for local development and testing. Use when the user needs to interact with Slack API endpoints locally, test Slack integrations, emulate channels/messages/users/views, set up Slack OAuth flows, test incoming webhooks, or work with the Slack Web API without hitting the real Slack API. Triggers include "Slack API", "emulate Slack", "mock Slack", "test Slack OAuth", "Slack bot", "Slack views", "incoming webhook", "local Slack", or any task requiring a local Slack API.

🧰 Not standalone — use together with vercel-labs/emulate

resend

★ 1,494

by vercel

Emulated Resend email API for local development and testing. Use when the user needs to send emails locally, test transactional email flows, implement magic link or verification code auth, inspect sent emails, manage domains/contacts/API keys, or work with the Resend API without sending real emails. Triggers include "Resend API", "emulate Resend", "send email locally", "test email", "magic link", "verification email", "email inbox", "RESEND_BASE_URL", or any task requiring a local email API.

🧰 Not standalone — use together with vercel-labs/emulate

next

★ 1,494

by vercel

Next.js adapter for embedding emulators directly in a Next.js app via @emulators/adapter-next. Use when the user needs to embed emulators in Next.js, set up same-origin OAuth for Vercel preview deployments, create an emulate catch-all route handler, configure Auth.js/NextAuth with embedded emulators, add persistence to embedded emulators, or wrap next.config with withEmulate. Triggers include "Next.js emulator", "adapter-next", "embedded emulator", "same-origin OAuth", "Vercel preview", "createE

🧰 Not standalone — use together with vercel-labs/emulate

microsoft

★ 1,494

by vercel

Emulated Microsoft Entra ID (Azure AD) OAuth 2.0 / OpenID Connect for local development and testing. Use when the user needs to test Microsoft sign-in locally, emulate Entra ID OIDC discovery, handle Microsoft token exchange, configure Azure AD OAuth clients, work with Microsoft Graph /me, or test PKCE/client credentials flows without hitting real Microsoft APIs. Triggers include "Microsoft OAuth", "Entra ID", "Azure AD", "emulate Microsoft", "mock Microsoft login", "test Microsoft sign-in", "Mi

🧰 Not standalone — use together with vercel-labs/emulate

google

★ 1,494

by vercel

Emulated Google OAuth 2.0, OpenID Connect, Gmail, Calendar, and Drive for local development and testing. Use when the user needs to test Google sign-in locally, emulate OIDC discovery, handle Google token exchange, configure Google OAuth clients, work with Gmail messages/drafts/threads/labels, manage Calendar events, upload or list Drive files, or work with Google userinfo without hitting real Google APIs. Triggers include "Google OAuth", "emulate Google", "mock Google login", "test Google sign-

🧰 Not standalone — use together with vercel-labs/emulate

github

★ 1,494

by vercel

Emulated GitHub REST API for local development and testing. Use when the user needs to interact with GitHub API endpoints locally, test GitHub integrations, emulate repos/issues/PRs, set up GitHub OAuth flows, configure GitHub Apps, test webhooks, or work with actions/checks without hitting the real GitHub API. Triggers include "GitHub API", "emulate GitHub", "mock GitHub", "test GitHub OAuth", "GitHub App JWT", "local GitHub", or any task requiring a local GitHub API.

🧰 Not standalone — use together with vercel-labs/emulate

emulate

★ 1,494

by vercel

Local drop-in API emulator for Vercel, GitHub, Google, Slack, Apple, Microsoft, AWS, Linear, and other developer APIs. Use when the user needs to start emulated services, configure seed data, write tests against local APIs, set up CI without network access, or work with the emulate CLI or programmatic API. Triggers include "start the emulator", "emulate services", "mock API locally", "create emulator config", "test against local API", "npx emulate", or any task requiring local service emulation.

🧰 Not standalone — use together with vercel-labs/emulate

aws

★ 1,494

by vercel

Emulated AWS cloud services (S3, SQS, IAM, STS) for local development and testing. Use when the user needs to interact with AWS API endpoints locally, test S3 bucket and object operations, emulate SQS queues and messages, manage IAM users/roles/access keys, test STS assume role, or work without hitting real AWS APIs. Triggers include "AWS emulator", "emulate AWS", "mock S3", "local SQS", "test IAM", "emulate S3", "AWS locally", "STS assume role", or any task requiring local AWS service emulation

🧰 Not standalone — use together with vercel-labs/emulate

apple

★ 1,494

by vercel

Emulated Sign in with Apple / Apple OIDC for local development and testing. Use when the user needs to test Apple sign-in locally, emulate Apple OIDC discovery, handle Apple token exchange, configure Apple OAuth clients, or work with Apple userinfo without hitting real Apple APIs. Triggers include "Apple OAuth", "emulate Apple", "mock Apple login", "test Apple sign-in", "Sign in with Apple", "Apple OIDC", "local Apple auth", or any task requiring a local Apple OAuth/OIDC provider.

🧰 Not standalone — use together with vercel-labs/emulate

linear

★ 1,494

by vercel-labs

Emulated Linear GraphQL API for local development and testing. Use when the user needs to test Linear integrations locally, emulate Linear issues, comments, teams, workflow states, OAuth apps, webhooks, agent sessions, or work with the Linear API without hitting the real Linear service. Triggers include "Linear API", "emulate Linear", "mock Linear", "test Linear OAuth", "Linear webhook", "Linear agent", "local Linear", or any task requiring a local Linear API.

🧰 Not standalone — use together with vercel-labs/emulate

nuxt

★ 1,494

by vercel-labs

Nuxt adapter for embedding emulators directly in a Nuxt app via @emulators/adapter-nuxt. Use when the user needs to embed emulators in Nuxt, set up same-origin OAuth for preview deployments, create an emulate catch-all server route, configure persistence for embedded Nuxt emulators, or wrap nuxt.config with withEmulate. Triggers include "Nuxt emulator", "adapter-nuxt", "embedded emulator", "same-origin OAuth", "createEmulateHandler", "withEmulate", or any task requiring emulators inside a Nuxt a

🧰 Not standalone — use together with vercel-labs/emulate

twilio

★ 1,494

by vercel-labs

Emulated Twilio REST APIs for local development and testing. Use when the user needs to test Twilio Messaging, Verify, Voice, phone numbers, webhooks, status callbacks, inbound SMS simulation, or Twilio SDK integrations without hitting the real Twilio service.

🧰 Not standalone — use together with vercel-labs/emulate

vercel

★ 1,494

by vercel

Emulated Vercel REST API for local development and testing. Use when the user needs to interact with Vercel API endpoints locally, test Vercel integrations, emulate projects/deployments/domains, set up Vercel OAuth flows, manage environment variables, create API keys, configure protection bypass, emulate Vercel Blob storage, or test without hitting the real Vercel API. Triggers include "Vercel API", "emulate Vercel", "mock Vercel", "test Vercel OAuth", "Vercel integration", "Vercel Blob", "local

🧰 Not standalone — use together with vercel-labs/emulate

web-design-guidelines

★ 1,449

by vercel

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

🧰 Not standalone — use together with vercel-labs/openreview

vercel-composition-patterns

★ 1,449

by vercel

React composition patterns that scale. Use when refactoring components with

🧰 Not standalone — use together with vercel-labs/openreview

vercel-react-best-practices

★ 1,449

by vercel

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

🧰 Not standalone — use together with vercel-labs/openreview

vercel-react-native-skills

★ 1,449

by vercel

React Native and Expo best practices for building performant mobile apps. Use

🧰 Not standalone — use together with vercel-labs/openreview

next-upgrade

★ 1,449

by vercel

Upgrade Next.js to the latest version following official migration guides and codemods

🧰 Not standalone — use together with vercel-labs/openreview

next-best-practices

★ 1,449

by vercel

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

🧰 Not standalone — use together with vercel-labs/openreview

next-cache-components

★ 1,449

by vercel

Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag

🧰 Not standalone — use together with vercel-labs/openreview

webreel

★ 892

by vercel

Create and record scripted browser demo videos with webreel. Generates MP4, GIF, or WebM recordings with cursor animation, keystroke overlays, and sound effects from a JSON config. Use when the user wants to record a demo, create a browser video, edit a webreel config, generate a screen recording, preview a demo, or work with webreel in any way.

🧰 Not standalone — use together with vercel-labs/webreel

ai-cli

★ 638

by vercel

Generate text, images, video, and audio from the terminal using AI models.

🧰 Not standalone — use together with vercel-labs/ai-cli

text

★ 595

by vercel

Analyze and transform text files using bash tools

🧰 Not standalone — use together with vercel-labs/bash-tool

csv

★ 595

by vercel

Analyze and transform CSV data using bash tools

🧰 Not standalone — use together with vercel-labs/bash-tool

synthesize-transcript

★ 201

by vercel-labs

Analyze an agent transcript for generalizable learnings about next-browser CLI usage, then propose SKILL.md updates, feature requests, and bug fixes.

🧰 Not standalone — use together with vercel-labs/next-browser

before-and-after

★ 199

by vercel

Captures before/after screenshots of web pages or elements for visual comparison. Use when user says "take before and after", "screenshot comparison", "visual diff", "PR screenshots", "compare old and new", or needs to document UI changes. Accepts two URLs (file://, http://, https://) or two image paths.

🧰 Not standalone — use together with vercel-labs/before-and-after