CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deploy-to-vercel

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary operational skill: a state-driven decision tree with fully executable commands, explicit approval and validation checkpoints, and error-recovery guidance for every failure mode. The only weaknesses are mild redundancy across the four method branches and environment-specific fallback content that could be offloaded to reference files.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no padding explaining what Vercel or git is — but instructions repeat across branches (team selection appears three times, the claim-URL message is duplicated verbatim, and the link-then-deploy section restates the git-push/CLI-deploy guidance). This is 'efficient; minor instances that could be trimmed', not the fully lean 5.

4 / 5

Actionability

Every path provides copy-paste-ready commands with exact flags ('vercel deploy [path] -y --no-wait --scope <team-slug>', 'vercel link --repo --scope <team-slug>'), script invocations with argument examples for all three cases, and a concrete output template covering the common scenarios.

5 / 5

Workflow Clarity

The flow is a clear decision tree: four state-gathering checks first, then per-state methods with numbered steps, an explicit user-approval checkpoint before pushing, verification via 'vercel inspect'/'vercel ls', and a troubleshooting section with recovery loops (escalated permissions on network failure, no-auth script on auth failure).

5 / 5

Progressive Disclosure

No bundle files exist, and the single file is well-sectioned with clear headers ('Step 1/2', 'Agent-Specific Notes', 'Output', 'Troubleshooting'). However, ~90 lines of environment-specific fallback and Codex/claude.ai sandbox material are inlined in SKILL.md where separate reference files would keep the core decision flow leaner — 'minor organization gaps'.

4 / 5

Total

18

/

20

Passed

Description

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

A strong description with an explicit and well-phrased trigger clause using natural user language, clearly answering both what the skill does and when to use it. The main gap is that the capability statement is thin — a single verb — and the trigger phrases are deployment-generic, slightly raising overlap risk with other deploy skills.

Suggestions

Enumerate the skill's core capabilities in the 'what' clause (e.g., 'Deploy applications and websites to Vercel via git-push integration, the Vercel CLI, or no-auth fallback scripts; links projects and returns preview URLs') to lift specificity beyond one generic action.

Add a few missing natural trigger synonyms such as 'go live', 'publish this site', or 'ship it' to broaden trigger coverage.

Include 'Vercel' in at least one trigger phrase (e.g., 'or asks to put this on Vercel') to reduce conflict risk with skills for other hosting platforms.

DimensionReasoningScore

Specificity

The description names the domain ('Deploy applications and websites to Vercel') with a single concrete action, but does not enumerate the skill's capabilities (project linking, git-push deployments, preview vs. production deploys, CLI fallback). This matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive', and falls short of 4 ('lists several specific actions').

3 / 5

Completeness

Explicitly answers both questions: the 'what' ('Deploy applications and websites to Vercel') and the 'when' ('Use when the user requests deployment actions like...') with concrete trigger phrases. This directly matches the top anchor and the good_overall_example pattern.

5 / 5

Trigger Term Quality

Includes four natural quoted phrases users would actually say ('deploy my app', 'deploy and give me the link', 'push this live', 'create a preview deployment'), giving good keyword coverage. Missing common variations like 'go live', 'publish', or 'ship it', so it does not reach the comprehensive-synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The Vercel niche is distinct, but generic trigger phrases like 'push this live' could also apply to other hosting/deployment skills (Netlify, GitHub Pages), creating minor overlap risk with closely related skills rather than the minimal conflict of 5.

4 / 5

Total

16

/

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

databricks/devhub

Path

.agents/skills/deploy-to-vercel/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.