CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sign-in-with-vercel

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.

59

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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-organized, token-efficient overview that frames Sign in with Vercel correctly and gives useful when/when-not guidance. However, it stops at the conceptual level — without the actual OAuth endpoints, scope names, or a token-exchange example, Claude cannot implement the flow from this skill alone.

Suggestions

Add the concrete OAuth endpoints (authorization URL, token endpoint) and the list of available scopes so the flow can actually be implemented.

Include a short code example of the authorization-code exchange and ID token verification, since 'use any standard OAuth 2.0 client library' leaves the critical token-validation step unspecified.

Trim the opening 'You are an expert in...' line, which duplicates the 'What It Is' section.

DimensionReasoningScore

Conciseness

Mostly lean with dense, useful tables (token lifetimes, when/when-not lists), but the opening 'You are an expert in Sign in with Vercel...' line duplicates the 'What It Is' section and could be trimmed.

4 / 5

Actionability

Provides some concrete facts (registration console URL, token lifetimes, 'any standard OAuth 2.0 client library') but is missing the key implementation details — authorization endpoint URL, token endpoint, available scopes, redirect URI format — and contains no code example for the token exchange.

3 / 5

Workflow Clarity

The OAuth flow is a coherent 5-step numbered sequence and Configuration is a 3-step sequence, but there are no validation checkpoints (e.g., verify the ID token signature, check the state parameter) and no error-recovery guidance.

3 / 5

Progressive Disclosure

No bundle files exist and the body is under 50 lines with well-organized sections and a single clearly signaled one-level-deep reference to the official docs URL, which merits a 5 under the simple-skill exception.

5 / 5

Total

15

/

20

Passed

Description

73%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 concise, well-targeted description that clearly states both what the skill covers and when to use it, with strong distinctiveness from generic auth skills. Its main limitation is a single trigger phrase and a thin action list, which keep specificity and trigger breadth below top marks.

DimensionReasoningScore

Specificity

Names the domain clearly ('OAuth 2.0/OIDC identity provider for user authentication via Vercel accounts') with 1-2 concrete actions ('user authentication', 'implementing user login'), but does not list several specific actions as the level-4 anchor requires.

3 / 5

Completeness

Explicitly answers both what ('OAuth 2.0/OIDC identity provider for user authentication via Vercel accounts') and when ('Use when implementing user login with Vercel as the identity provider'), but the when-clause is single-triggered and less rich than the level-5 anchor's multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('Sign in with Vercel', 'user login', 'user authentication', 'identity provider') that users would actually say, though common variations like 'log in with Vercel' or 'authenticate users' are missing.

4 / 5

Distinctiveness Conflict Risk

'Sign in with Vercel' is a clear niche with distinct triggers; the explicit Vercel requirement means it cannot fire for generic auth skills like Clerk or Auth0, which the body even names as alternatives.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

openai/plugins

Path

plugins/vercel/skills/sign-in-with-vercel/SKILL.md

Reviewed

Table of Contents

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.