Name: auth
Rating: 67.2 (1 reviews)
Author: vercel

auth

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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable integration guide with copy-paste-ready code across three providers. Adding explicit post-setup verification steps and offloading the lengthy breaking-changes detail to a reference would lift it to the top band.

Suggestions

Add an explicit verification step after each provider setup (e.g., hit a protected route and confirm a 401, then sign in and confirm 200) so the workflow has a feedback checkpoint.

Move the Clerk Core 3 Breaking Changes block into a references file (e.g. references/clerk-core-3.md) and link to it, keeping the main body leaner.

Trim provider intro sentences ("Auth0 provides a mature authentication platform...") that restate knowledge Claude already has.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code blocks and little padding, though provider intro lines ("Auth0 provides a mature authentication platform...") and body version dates could be trimmed; time-sensitive version info is appropriately isolated in the Core 3 Breaking Changes section.	4 / 5
Actionability	Fully executable, copy-paste-ready code for install, middleware, provider, sign-in/sign-up, and API/session protection across all three providers, plus a decision matrix for provider choice — covering the common cases.	5 / 5
Workflow Clarity	Each provider follows a clear install→SDK→middleware→provider→access sequence, but verification checkpoints (e.g., confirm env vars provisioned, test a protected route returns 401) are implicit rather than stated; auth setup is not destructive/batch so the workflow-3 cap does not apply.	4 / 5
Progressive Disclosure	Single-file skill with well-organized per-provider sections, a decision matrix, dedicated breaking-changes section, and clearly signaled one-level cross-references (⤳ skill: marketplace/routing-middleware/env-vars plus official doc links); the detailed Core 3 breaking-changes block could arguably move to a reference file.	4 / 5
	Total	17 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that names concrete providers and actions and includes an explicit "Use when" trigger. It would reach the top band by broadening the trigger clause with synonyms users actually say (login, OAuth, protect routes).

Suggestions

Expand the "Use when" clause to list multiple concrete triggers, e.g. "Use when implementing user authentication, login flows, OAuth, route protection, or session management."

Add natural synonyms users say (login, sign in, OAuth, sessions) directly into the description rather than only in the retrieval metadata.

Dimension	Reasoning	Score
Specificity	Names three concrete providers (Clerk, Descope, Auth0) and multiple specific actions — "middleware auth patterns, sign-in/sign-up flows, and Marketplace provisioning" — for comprehensive coverage.	5 / 5
Completeness	Clearly answers "what" (provider setup covering middleware/sign-in/sign-up/Marketplace) and "when" ("Use when implementing user authentication"), but the trigger clause is a single phrase rather than the multiple concrete triggers of the top anchor.	4 / 5
Trigger Term Quality	Includes natural terms like "authentication" and "sign-in/sign-up flows" and "implementing user authentication," but misses common synonyms (login, OAuth, sessions, protect routes) that appear only in the retrieval metadata, not the description.	4 / 5
Distinctiveness Conflict Risk	Carves a clear Next.js-auth niche across three named providers with Marketplace provisioning, distinct from adjacent skills it explicitly cross-references (routing-middleware, marketplace, env-vars); minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: vercel/vercel-plugin
Path: skills/auth/SKILL.md
Commit: 358400a

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.