CtrlK
BlogDocsLog inGet started
Tessl Logo

vercel-cli-with-tokens

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable, well-sequenced CLI runbook with executable commands and explicit checkpoints for risky operations. Slight verbosity from restated guardrails and a long single-file form are the only drags on an otherwise excellent skill body.

Suggestions

Collapse the 'Working Agreement' section where it merely restates inline guidance already present in the relevant steps to trim token cost.

Consider moving the 'What Pro gives you' plan-feature detail to a reference file so the main body stays focused on actions.

DimensionReasoningScore

Conciseness

Mostly lean, command-driven content with minimal over-explanation of concepts Claude already knows; the 'Working Agreement' section restates a few points already made inline, keeping it just short of a 5.

4 / 5

Actionability

Dense, copy-paste-ready executable commands throughout (printenv/grep/exports, vercel deploy/inspect/env/domains) with concrete examples covering the common deploy, env-var, domain, and plan-change cases.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (Step 1 token, Step 2 project/team, deploy flows) with explicit validation checkpoints and feedback loops — 'Ask the user before pushing', vercel inspect status, build-log troubleshooting, and confirmation before paid/destructive plan changes.

5 / 5

Progressive Disclosure

Well-organized single-file structure with clear section headers and no nested references; for a CLI skill with no external bundle files this is appropriate, though the long monolithic body (e.g. 'What Pro gives you') could in principle be split out.

4 / 5

Total

18

/

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 strong, third-person description that clearly answers both what the skill does and when to use it, with natural trigger phrases. Minor room to widen trigger-term synonyms and surface more of the underlying capabilities.

Suggestions

Add a couple more natural trigger phrases or synonyms (e.g. 'vercel env vars', 'vercel domains') to broaden trigger coverage.

Mention a few more concrete capabilities beyond deploy/manage (e.g. domains, environment variables, inspecting deployments) to lift specificity toward comprehensive.

DimensionReasoningScore

Specificity

Names the Vercel domain and several concrete actions — 'Deploy and manage projects', plus trigger examples 'deploy to vercel', 'set up vercel', 'add environment variables to vercel' — covering multiple specific operations with only minor gaps (e.g. domains/inspection not surfaced).

4 / 5

Completeness

Explicitly states both what ('Deploy and manage projects on Vercel using token-based authentication') and when ('Use when working with Vercel CLI using access tokens rather than interactive login — e.g. ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user-facing phrases like "deploy to vercel", "set up vercel", and "add environment variables to vercel" are quoted, which are phrases users would actually say; a few synonyms or broader variations are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

The 'token-based authentication rather than interactive login' framing carves a clear niche distinct from a general Vercel skill, though 'deploy to vercel' style triggers could still overlap marginally with a sibling Vercel skill.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
vercel-labs/agent-skills
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.