vercel-cli

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

Quality

60%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/vercel-cli/SKILL.md

Quality

Discovery

32%

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 identifies the platform (Vercel) and general actions but lacks specificity in concrete capabilities and completely omits explicit trigger guidance ('Use when...'). It would benefit from listing specific operations and adding natural trigger terms users would use when needing Vercel-related help.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about deploying to Vercel, managing Vercel projects, checking deployment status, or configuring Vercel settings.'

List more specific concrete actions like 'configure environment variables, set up custom domains, manage preview and production deployments, check deployment logs, link projects'.

Include additional natural trigger terms like 'vercel CLI', 'Next.js deployment', 'hosting', 'serverless functions', 'preview deployment', '.vercel' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Vercel) and lists some actions ('deploy, manage, and develop projects'), but these are fairly broad and not highly specific concrete actions like 'configure environment variables, set up custom domains, manage deployments'.	2 / 3
Completeness	Describes what it does (deploy, manage, develop on Vercel) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 1.	1 / 3
Trigger Term Quality	Includes 'Vercel' and 'deploy' which are strong natural trigger terms, and 'command line' is relevant. However, it misses common variations like 'hosting', 'serverless', 'Next.js deployment', 'vercel CLI', 'production deployment', or 'preview deployment'.	2 / 3
Distinctiveness Conflict Risk	'Vercel' is a distinct platform name that helps differentiate this from generic deployment skills, but 'deploy, manage, and develop projects' is broad enough that it could overlap with other deployment/hosting platform skills (e.g., Netlify, AWS). The 'command line' qualifier helps somewhat.	2 / 3
	Total	7 / 12 Passed

Implementation

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill that serves effectively as a routing hub for Vercel CLI operations. It excels at conciseness, actionability, and progressive disclosure with its decision tree pointing to specific reference files. The main weakness is that workflow clarity could benefit from more explicit validation checkpoints, particularly around the linking/troubleshooting process which is described narratively rather than as a step-by-step diagnostic workflow.

Suggestions

Consider restructuring the 'Critical: Project Linking' troubleshooting guidance into an explicit numbered diagnostic workflow with validation steps (e.g., 1. Run `vercel whoami` → verify team, 2. Check `ls .vercel/` → verify link type, 3. If wrong type → `rm -rf .vercel && vercel link --repo`)

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It doesn't explain what Vercel is or how CLIs work. Every section serves a purpose: linking context, quick start commands, decision tree for navigation, and anti-patterns. No unnecessary padding.	3 / 3
Actionability	The quick start section provides copy-paste ready commands. The anti-patterns section gives specific, concrete guidance (e.g., use `--prebuilt`, use `VERCEL_TOKEN` env var, use `vercel curl`). Diagnostic steps are concrete (`vercel whoami`, check `.vercel/` contents).	3 / 3
Workflow Clarity	The quick start provides a clear sequence for initial setup and deployment. However, the troubleshooting workflow for linking issues is described narratively rather than as explicit steps with validation checkpoints. The decision tree is a routing mechanism, not a workflow with feedback loops.	2 / 3
Progressive Disclosure	Excellent progressive disclosure structure. The SKILL.md serves as a concise overview with a clear decision tree routing to 15+ specific reference files. References are one level deep and clearly signaled with descriptive labels. However, no bundle files were provided to verify the referenced paths exist, so scoring based on the structure as presented.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: databricks/devhub
Commit: 1cfe305

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.