auth Skill
Authentication integration guidance — Clerk (native Vercel Marketplace), Descope, and Auth0 setup for Next.js applications. Covers middleware auth patterns, sign-in/sign-up flows, and Marketplace provisioning. Use when implementing user authentication. Published by openai in plugins.
Decision snapshot
Is this a fit?
Developers using plugins, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
API key required authentication, Credentials required
Copy skill directory
18 days ago
Access note: API key required.
What is auth Skill?
Authentication integration guidance — Clerk (native Vercel Marketplace), Descope, and Auth0 setup for Next.js applications. Covers middleware auth patterns, sign-in/sign-up flows, and Marketplace provisioning. Use when implementing user authentication. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using plugins
Declared skill metadata
- Source file: plugins/vercel/skills/auth/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- API key required
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use auth Skill
- Use it for developers using plugins.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/vercel/skills/auth/SKILL.md
What it does
Authentication integration guidance — Clerk (native Vercel Marketplace), Descope, and Auth0 setup for Next.js applications. Covers middleware auth patterns, sign-in/sign-up flows, and Marketplace provisioning. Use when implementing user authentication.
Skill instructions
Authentication Integrations You are an expert in authentication for Vercel-deployed applications — covering Clerk (native Vercel Marketplace integration), Descope, and Auth0. Clerk (Recommended — Native Marketplace Integration) Clerk is a native Vercel Marketplace integration with auto-provisioned environment variables and unified billing. Current SDK: @clerk/nextjs v7 (Core 3, March 2026). Install via Marketplace bash Install Clerk from Vercel Marketplace (auto-provisions env vars) vercel integration add clerk Auto-provisioned environment variables: - CLERKSECRETKEY — server-side API key - NEXTPUBLICCLERKPUBLISHABLEKEY — client-side publishable key SDK Setup bash Install the Clerk Next.js SDK npm install @clerk/nextjs Middleware Configuration ts // middleware.ts import { clerkMiddleware } from "@clerk/nextjs/server"; export default clerkMiddleware(); export const config = { matcher: [ // Skip Next.js internals and static files "/((?!next|[^?]\.(?:html?|css|js(?!on)|jpe?g|webp|png|gif
Verified compatibility and discovery
Frequently asked questions
What is auth?
auth is a open-source AI agent skill with Copy skill directory. Authentication integration guidance — Clerk (native Vercel Marketplace), Descope, and Auth0 setup for Next.js applications. Covers middleware auth patterns, sign-in/sign-up flows, and Marketplace provisioning.
Who is auth best for?
auth is best for reusing agent instructions, scripts, and references.
How do I install auth?
Install or run auth using Copy skill directory. Check auth for the latest setup command.
Is auth actively maintained?
auth may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
