Agent Skills
› openai/plugins
› sign-in-with-vercel
sign-in-with-vercel
GitHub指导开发者使用 Vercel 作为 OAuth 2.0/OIDC 身份提供商实现用户登录。涵盖授权码流程、令牌管理（ID/Access/Refresh Token）及配置步骤，适用于需 Vercel 账户身份或访问其资源的开发者工具与仪表盘应用。
Trigger Scenarios
需要集成 Vercel 账号登录功能
实现基于 Vercel 的 OAuth 2.0 认证
获取 Vercel 用户身份信息
Install
npx skills add openai/plugins --skill sign-in-with-vercel -g -y
SKILL.md
Frontmatter
{
"name": "sign-in-with-vercel",
"metadata": {
"docs": [
"https:\/\/vercel.com\/docs\/sign-in-with-vercel"
],
"sitemap": "https:\/\/vercel.com\/sitemap\/docs.xml",
"priority": 6,
"bashPatterns": [],
"pathPatterns": [
"app\/api\/auth\/**",
"app\/login\/**",
"src\/app\/api\/auth\/**",
"src\/app\/login\/**",
"pages\/api\/auth\/**"
]
},
"description": "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."
}
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
- 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. - Configure redirect URIs and scopes
- 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
Version History
- 11c74d6 Current 2026-07-19 09:52
