Sign In With Vercel
Implement user login using Vercel as the OAuth 2.0/OIDC identity provider in App Router or Pages auth routes.
Overview
sign-in-with-vercel is an agent skill for the Build phase that implements user login with Vercel as the OAuth 2.0/OIDC identity provider.
Install
npx skills add https://github.com/vercel-labs/vercel-plugin --skill sign-in-with-vercelWhat is this skill?
- OAuth 2.0 and OIDC patterns for Sign in with Vercel as the identity provider
- Path-aware retrieval for app/api/auth, login, and pages/api/auth layouts
- Chains to auth skill when NextAuth or Auth.js is detected for middleware and provider setup
- Chains to env-vars skill when VERCEL_CLIENT_ID or VERCEL_CLIENT_SECRET appear for secure env management
Adoption & trust: 38 installs on skills.sh; 187 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need Vercel-account login in your app but are unsure how to configure OAuth routes, providers, and secrets correctly on Vercel.
Who is it for?
Solo builders on Vercel deploying Next.js apps who want Sign in with Vercel instead of bolting on an unrelated IdP first.
Skip if: Projects already fully on Clerk or Descope with no Vercel OAuth intent, or apps that do not need user authentication at all.
When should I use this skill?
Implementing user login with Vercel as the identity provider or when OAuth/OIDC Sign in with Vercel patterns apply.
What do I get? / Deliverables
You get doc-aligned OAuth/OIDC setup for Sign in with Vercel, with chained auth and env-vars guidance when NextAuth or client secrets are in play.
- Configured Sign in with Vercel OAuth/OIDC flow
- Aligned env var handling for VERCEL_CLIENT_ID and VERCEL_CLIENT_SECRET
Recommended Skills
Journey fit
Authentication against Vercel’s identity provider is wired during product build when API and login routes are created. The skill targets app/api/auth and login paths, client credentials, and provider configuration—backend identity integration, not marketing or SEO.
How it compares
Vercel-hosted OAuth identity guidance for your app routes—not a generic password-auth checklist or an MCP server.
Common Questions / FAQ
Who is sign-in-with-vercel for?
Indie developers implementing login on Vercel-hosted Next.js apps who want OAuth 2.0/OIDC through Sign in with Vercel.
When should I use sign-in-with-vercel?
In Build while creating app/api/auth or login routes, configuring the Vercel identity provider, or aligning NextAuth with Vercel OAuth env vars.
Is sign-in-with-vercel safe to install?
OAuth skills touch secrets and auth flows—review the Security Audits panel on this page and never commit VERCEL_CLIENT_SECRET to the repo.
SKILL.md
READMESKILL.md - Sign In With Vercel
# Sign in with Vercel You are an expert in Sign in with Vercel — Vercel's OAuth 2.0 / OpenID Connect identity provider. ## What It Is Sign in with Vercel lets users log in to your application using their **Vercel account**. Your app does not need to handle passwords, create accounts, or manage user sessions — Vercel acts as the identity provider (IdP). ## OAuth 2.0 Authorization Code Flow ``` 1. User clicks "Sign in with Vercel" 2. Redirect to Vercel authorization URL 3. User grants consent on Vercel's consent page 4. Vercel redirects back with authorization code 5. Exchange code for tokens (ID Token + Access Token + Refresh Token) ``` ## Tokens | Token | Lifetime | Purpose | |-------|----------|---------| | **ID Token** | Signed JWT | Proves user identity (name, email, avatar) | | **Access Token** | 1 hour | Bearer token for Vercel REST API calls | | **Refresh Token** | 30 days | Silent re-authentication (rotates on use) | ## Configuration 1. Register your app at `https://vercel.com/dashboard/{team}/integrations/console` (the Integrations Console). Click **Create Integration** → fill in the OAuth details → note the Client ID and Client Secret. 2. Configure redirect URIs and scopes 3. Use any standard OAuth 2.0 client library (no Vercel-specific SDK required) ## When to Use - Build tools/dashboards that need Vercel account identity - Grant users access to their own Vercel resources via your app - Developer-facing apps where users already have Vercel accounts ## When NOT to Use - General-purpose user auth (not everyone has Vercel) → use Clerk, Auth0 - Machine-to-machine auth → use Vercel OIDC Federation or API tokens - Internal team auth → use Teams & Access Control ## References - 📖 docs: https://vercel.com/docs/sign-in-with-vercel