CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

67%

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.

The body is well-structured and token-efficient with a single clean external reference, but its guidance is conceptually framed rather than executable and its flows lack validation checkpoints. Adding concrete endpoint/scope/code details and token-validation steps would move it toward the top anchors.

Suggestions

Add executable specifics: the Vercel authorization URL format, the required scopes, and a minimal token-exchange request example using a standard OAuth library.

Insert validation checkpoints into the flow, e.g. 'Verify the ID token JWT signature and claims before trusting user identity' and 'Handle expired/invalid authorization codes by re-initiating the flow'.

Trim the mild redundancy between the 'You are an expert' opener and the 'What It Is' paragraph to push conciseness to a 5.

DimensionReasoningScore

Conciseness

The body is largely lean — a tight token table, compact flow steps, and brief config steps — with only minor redundancy such as restating that the app avoids password handling after the 'expert in' opener, so it sits just below the fully lean 5 anchor.

4 / 5

Actionability

It gives a real console URL and high-level steps (register integration, configure redirect URIs and scopes, use a standard OAuth library), but stops short of executable specifics — no authorization endpoint, no scope list, no token-exchange request example or library snippet — leaving key implementation details missing.

3 / 5

Workflow Clarity

The authorization-code flow and configuration are presented as clear sequences, but there are no validation checkpoints or feedback loops (e.g., verify the ID token signature, handle expired codes), which the workflow-clarity anchors expect for a 4.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and a single, clearly-signaled one-level external reference (the docs URL), with well-organized sections, matching the simple-skill allowance for a top progressive-disclosure score.

5 / 5

Total

15

/

20

Passed

Description

70%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.

The description clearly identifies a distinct niche and pairs a concrete 'what' with an explicit 'Use when' trigger, but it is light on concrete action verbs and only modestly broad in trigger phrasing. Strengthening action specificity and trigger synonyms would lift it toward the top anchors.

Suggestions

Replace the vague 'guidance' framing with concrete actions (e.g., 'Configure OAuth 2.0 redirect URIs, exchange authorization codes for tokens, validate ID tokens').

Broaden trigger coverage with natural synonyms users say, such as 'Vercel OAuth login', 'sign in users with their Vercel account', or 'Vercel identity provider'.

Name key prerequisites or artifacts in the 'when' clause (e.g., when you have a Vercel integration Client ID/Secret) to sharpen distinctiveness from generic OAuth skills.

DimensionReasoningScore

Specificity

Names the domain ('OAuth 2.0/OIDC identity provider for user authentication via Vercel accounts') but the only action framing is the vague word 'guidance', with no concrete enumerated actions, so it does not reach the multi-action coverage of 4.

3 / 5

Completeness

Provides a clear 'what' and an explicit 'when' ('Use when implementing user login with Vercel as the identity provider'), but the trigger names a single scenario without enumerating multiple trigger phrasings, matching 4 rather than the broadened 5 anchor.

4 / 5

Trigger Term Quality

Includes natural user-facing phrases such as 'Sign in with Vercel', 'user login with Vercel as the identity provider', and 'Vercel accounts', but misses several common synonyms/variants a user might say, stopping short of comprehensive 5-level coverage.

4 / 5

Distinctiveness Conflict Risk

The Vercel-as-IdP niche and 'Sign in with Vercel' trigger are specific and unlikely to misfire, though the description lives in the crowded auth space, leaving minor overlap risk with adjacent auth skills.

4 / 5

Total

15

/

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.

Validation14 / 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
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.