CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vercel-cli

Deploy apps to Vercel. Use when asked to deploy, ship, or publish a web application, or manage Vercel projects, domains, and environment variables.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 skill: commands are executable end to end, and the pre-send validation checklist with a fix-and-redeploy loop is exemplary. The main costs are token efficiency — repeated auth-token explanation and a duplicated delegation rule — and no use of bundle files to move detail out of SKILL.md.

Suggestions

State the '--token placeholder' rule once in the Auth section and drop it from the Deploying preamble and individual command comments, saving repeated tokens without losing the instruction.

Merge the top 'HARD RULE' box into the 'Building Websites' section so the delegate-don't-build rule is stated once, trimming emphasis markers that add tokens without adding information.

Move the Project Management / Domains / Environment Variables command catalogs into a references/ file (e.g., commands.md) linked from SKILL.md, keeping the overview lean while preserving copy-paste-ready detail.

DimensionReasoningScore

Conciseness

Command blocks are lean, but the '--token placeholder' mechanism is explained in the Auth section, restated as a preamble to Deploying, and repeated in every code comment, and the 'do not build websites yourself' rule appears twice with redundant emphasis ('This is not optional', 'MANDATORY', '⚠️ CRITICAL'). This is more than the 'minor instances' of the anchor-4 example, matching 'mostly efficient but could be tightened'.

3 / 5

Actionability

Every section gives copy-paste-ready commands with inline comments (deploy variants, whoami auth check, link, domain add, piped env add, curl status check), the error table pairs messages with concrete fixes, and the delegation section includes complete pseudo-API payloads. Fully executable and covers the common cases.

5 / 5

Workflow Clarity

The deploy workflow has an explicit pre-send checklist with validation checkpoints (local build passes, READY status confirmed via 'vercel inspect', live URL responds via curl) and a fix-and-redeploy feedback loop; the auth and delegation workflows also include explicit verify-and-retry loops. Matches the anchor-5 example pattern of validate, fix, and only then proceed.

5 / 5

Progressive Disclosure

No bundle files exist, and this single-file skill is well organized with clearly headed sections covering auth, deploying, checks, projects, domains, env vars, errors, and delegation. At ~130 lines with some cross-section redundancy, a split (e.g., a command reference or delegation guide) would help, so it sits just below the ideal anchor 5.

4 / 5

Total

17

/

20

Passed

Description

87%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 is a strong match to the ideal pattern: a concrete 'what' statement followed by an explicit 'Use when' clause with natural trigger synonyms. Its only weakness is slightly incomplete action coverage relative to everything the skill body actually supports.

DimensionReasoningScore

Specificity

Names the domain ('Deploy apps to Vercel') and several concrete actions ('manage Vercel projects, domains, and environment variables'), but coverage has minor gaps — inspecting deployments, preview deploys, and listing deployments are handled by the skill yet unmentioned. Fits 'several specific actions; minor gaps' rather than the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both: what ('Deploy apps to Vercel... manage Vercel projects, domains, and environment variables') and when ('Use when asked to deploy, ship, or publish a web application, or manage...') with concrete trigger phrases. This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

'deploy, ship, or publish a web application' covers natural synonyms users would say, and 'Vercel projects, domains, and environment variables' are natural trigger terms. A few common variations (e.g., 'preview deployment', 'roll back', 'redesign') are missing, so it falls just short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

A clear Vercel-specific niche with distinct, platform-named triggers; other deployment or web skills would not collide with these terms. Minimal conflict risk.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

nanocoai/nanoclaw

Path

.claude/skills/add-vercel/container-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.