CtrlK
BlogDocsLog inGet started
Tessl Logo

vercel-cli

Deploy, manage, and develop projects on Vercel from the command line

65

Quality

77%

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 ./.agents/skills/vercel-cli/SKILL.md
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.

The skill body is a well-structured overview with executable commands, an explicit validation checkpoint for linking, and clean progressive disclosure into real reference files. It is concise and action-oriented with only minor tightening possible.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding explanations of what Vercel or monorepos are; a few sentences in the linking section could be trimmed but mostly earn their place as non-obvious failure guidance.

4 / 5

Actionability

Copy-paste ready commands appear throughout (install, login, link --repo, --prod, whoami, teams switch, curl) and Anti-Patterns pair each pitfall with a concrete fix command.

5 / 5

Workflow Clarity

Quick Start sequences install→login→link→pull→dev/deploy, and the Critical Project Linking section provides an explicit validation checkpoint ('check how things are linked first… verify with vercel whoami') plus error-recovery guidance in Anti-Patterns.

5 / 5

Progressive Disclosure

A concise overview routes to 16 one-level-deep reference files via a clear Decision Tree; spot-checks confirm the references hold real content rather than forwarding chains.

5 / 5

Total

19

/

20

Passed

Description

62%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 clear and distinctive but lacks explicit trigger guidance, which caps its completeness. It names concrete actions and a clear domain niche.

Suggestions

Add a 'Use when...' clause naming trigger phrases users would naturally say (e.g., 'Use when deploying or managing projects on Vercel, working with the Vercel CLI, or troubleshooting Vercel deploys').

Include common synonyms/tool names like 'vercel CLI', 'vc', 'preview deployment', and 'production deploy' to improve trigger-term coverage.

Replace or supplement the generic 'manage' with more specific actions (e.g., 'link projects, manage env vars, configure domains') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('projects on Vercel', 'from the command line') and three concrete actions ('Deploy, manage, and develop'), with only minor generic gaps in coverage.

4 / 5

Completeness

Clearly states what the skill does but includes no 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Has relevant keywords (Deploy, manage, develop, Vercel, command line) but misses common synonyms and tool-specific terms like 'vc', 'preview deployment', or 'vercel CLI' that users would say.

3 / 5

Distinctiveness Conflict Risk

The explicit 'on Vercel' and 'from the command line' scoping carves a clear niche with minimal conflict risk against other skills.

5 / 5

Total

15

/

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
databricks/devhub
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.