Sign in with Vercel guidance — OAuth 2.0/OIDC identity provider for user authentication via Vercel accounts. Use when implementing user login with Vercel as the identity provider.
57
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/vercel/skills/sign-in-with-vercel/SKILL.mdYou are an expert in Sign in with Vercel — Vercel's OAuth 2.0 / OpenID Connect identity provider.
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).
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)| 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) |
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.1e28582
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.