vercel-cli

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

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

The body exemplifies progressive disclosure and actionability: a lean overview with a routing decision tree to real reference files, concrete executable commands, and clear linking workflows with explicit error-recovery guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and operational — a quick start, a linking decision section, a decision tree, and anti-patterns — with no padding explaining what Vercel is or basic CLI concepts; every token earns its place.	3 / 3
Actionability	It provides concrete, copy-paste-ready commands (`npm i -g vercel`, `vercel link --repo`, `vercel pull`, `vercel dev`, `vercel --prod`, `vercel curl`, `vercel api`) and a full executable quick-start sequence.	3 / 3
Workflow Clarity	The linking section gives a clear project.json-vs-repo.json decision and an explicit error-recovery loop ("When something goes wrong, check how things are linked first... verify with `vercel whoami`"), and the anti-patterns act as a checklist for fragile operations.	3 / 3
Progressive Disclosure	SKILL.md is a well-signaled overview with a decision tree routing to 16 one-level-deep reference files, all of which exist on disk; content is appropriately split and easy to navigate.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 concise and clearly tied to the Vercel CLI niche, but it lacks an explicit "Use when..." trigger clause and relies on somewhat generic verbs ("manage"), leaving the what/when completeness and trigger coverage at the mid level.

Suggestions

Add an explicit trigger clause, e.g. "Use when deploying, managing, or developing projects on Vercel from the command line, or when the user mentions Vercel, `vercel`, or `vc`."

Replace the generic "manage" with concrete actions (e.g., "deploy, alias, manage env vars, and inspect logs") to lift specificity.

Include common natural variations like "Vercel CLI", "`vc`", and "preview/production deployments" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Deploy, manage, and develop projects on Vercel from the command line" names a clear domain and three actions, but "manage" is generic and the actions are high-level rather than the concrete, comprehensive set the top anchor expects.	2 / 3
Completeness	It clearly states what the skill does, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	The natural trigger "Vercel" and "deploy" are present, but common variations a user would actually say ("vc" alias, "preview/production deploy", "deploy to Vercel") are missing.	2 / 3
Distinctiveness Conflict Risk	"Vercel" is a clear, narrow niche tied to a specific CLI, making it highly distinguishable and unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: databricks/devhub
Commit: 131db95

Reviewed: 5 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.