Update to Vercel

{
  "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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 182
    }
  ],
  "name": "sign-in-with-vercel",
  "skill_md_contents": "---\nname: sign-in-with-vercel\ndescription: 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.\nmetadata:\n  priority: 6\n  docs:\n    - \"https://vercel.com/docs/sign-in-with-vercel\"\n  sitemap: \"https://vercel.com/sitemap/docs.xml\"\n  pathPatterns: \n    - 'app/api/auth/**'\n    - 'app/login/**'\n    - 'src/app/api/auth/**'\n    - 'src/app/login/**'\n    - 'pages/api/auth/**'\n  bashPatterns: []\n---\n\n# Sign in with Vercel\n\nYou are an expert in Sign in with Vercel — Vercel's OAuth 2.0 / OpenID Connect identity provider.\n\n## What It Is\n\nSign 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).\n\n## OAuth 2.0 Authorization Code Flow\n\n```\n1. User clicks \"Sign in with Vercel\"\n2. Redirect to Vercel authorization URL\n3. User grants consent on Vercel's consent page\n4. Vercel redirects back with authorization code\n5. Exchange code for tokens (ID Token + Access Token + Refresh Token)\n```\n\n## Tokens\n\n| Token | Lifetime | Purpose |\n|-------|----------|---------|\n| **ID Token** | Signed JWT | Proves user identity (name, email, avatar) |\n| **Access Token** | 1 hour | Bearer token for Vercel REST API calls |\n| **Refresh Token** | 30 days | Silent re-authentication (rotates on use) |\n\n## Configuration\n\n1. 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.\n2. Configure redirect URIs and scopes\n3. Use any standard OAuth 2.0 client library (no Vercel-specific SDK required)\n\n## When to Use\n\n- Build tools/dashboards that need Vercel account identity\n- Grant users access to their own Vercel resources via your app\n- Developer-facing apps where users already have Vercel accounts\n\n## When NOT to Use\n\n- General-purpose user auth (not everyone has Vercel) → use Clerk, Auth0\n- Machine-to-machine auth → use Vercel OIDC Federation or API tokens\n- Internal team auth → use Teams & Access Control\n\n## References\n\n- 📖 docs: https://vercel.com/docs/sign-in-with-vercel\n"
}