CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vercel-cli

Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, debugging a deployed app on Vercel (errors, 5xx responses, timeouts, slow routes, or a single failing request), managing domains, managing feature flags with vercel flags, reviewing security checks or Security Review vulnerabilities with vercel security, or interacting with the Vercel platform from the command line. Use the vercel-tracing skill instead for `vercel traces` span search, trace inspection, and sampling rules, or for OpenTelemetry setup.

Quality

95%

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

92%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 router skill: executable commands dominate, risky operations (linking, mutations) are gated by explicit validation and error-recovery guidance, and the decision tree provides excellent one-level-deep navigation to a complete reference bundle. The only weakness is mild redundancy between the linking section and the Anti-Patterns list, which could be consolidated to trim tokens.

DimensionReasoningScore

Conciseness

The body is dense and operational with no explanations of concepts Claude already knows, but there is minor redundancy: linking behaviors (project.json vs repo.json, auto-linking, whoami limits, project inspect verification) are explained in "Critical: Project Linking" and then restated as Anti-Patterns bullets, and the repo-resolution bullets could be tightened. This fits the 'efficient with minor instances that could be trimmed' anchor rather than 'every token earns its place'.

4 / 5

Actionability

Guidance is copy-paste ready throughout: a complete quick-start command block, `vercel project inspect --non-interactive` as a concrete verification command, `vercel deploy --force` without `--with-cache` for no-cache rebuilds, `VERCEL_TOKEN` instead of `--token`, and `vercel curl` for preview access. Specific commands cover the common cases, matching the fully-executable anchor.

5 / 5

Workflow Clarity

Multi-step workflows carry explicit validation checkpoints and feedback loops: before any consequential read or mutation the reader is told to run `vercel project inspect --non-interactive` and confirm owner/project, to stop on `link_required` or target mismatch rather than auto-linking, and the JSON error protocol (`status`, `reason`, `hint`, `next`) provides an explicit error-recovery path with cautions about mutation follow-ups. This matches the anchor for clear sequencing with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

The body is a clean overview: an intro with output-parsing rules, a linking gate, a quick start, a decision tree routing each task area to one of 26 real one-level-deep reference files (all verified present in references/), and anti-patterns. References are clearly signaled with topic descriptions, and the few cross-links between reference files are sibling pointers, not nested chains, so navigation stays one level deep.

5 / 5

Total

19

/

20

Passed

Description

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

An excellent description: it names the domain, lists comprehensive concrete capabilities, provides an explicit "Use when" clause rich with natural trigger terms and symptom synonyms, and actively reduces conflict risk by routing trace-related work to a sibling skill. It uses appropriate third-person imperative voice with no fluff or over-claims.

DimensionReasoningScore

Specificity

The description enumerates concrete, specific actions across the entire CLI surface: "deploying, managing environment variables, linking projects, viewing logs, querying metrics, debugging a deployed app on Vercel (errors, 5xx responses, timeouts, slow routes, or a single failing request), managing domains, managing feature flags with vercel flags, reviewing security checks or Security Review vulnerabilities with vercel security". This matches the anchor for multiple specific concrete actions with comprehensive coverage, exceeding the 'minor gaps' level below.

5 / 5

Completeness

It clearly answers both questions: the "what" is stated up front ("Vercel CLI expert guidance" over an enumerated command surface) and the "when" is an explicit "Use when deploying... or interacting with the Vercel platform from the command line" clause with concrete trigger phrases. This matches the anchor for explicitly answering both what and when with concrete triggers.

5 / 5

Trigger Term Quality

Natural trigger terms are comprehensively covered with synonyms and symptom variants users would actually say ("deploying", "environment variables", "logs", "metrics", "errors, 5xx responses, timeouts, slow routes", "domains", "feature flags", "security") plus literal command names ("vercel flags", "vercel security", "vercel traces"). This fits the comprehensive-coverage-with-synonyms anchor rather than the 'a few natural terms missing' level.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (Vercel platform operations from the command line) and the closest conflict is explicitly disambiguated: "Use the vercel-tracing skill instead for `vercel traces` span search, trace inspection, and sampling rules, or for OpenTelemetry setup". Distinct triggers with minimal conflict risk, matching the top anchor.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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/vercel-cli/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.