CtrlK
BlogDocsLog inGet started
Tessl Logo

vercel-deploy

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". Do NOT use for deploying to Netlify, Cloudflare, or Render (use their respective skills).

65

Quality

77%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./packages/skills-catalog/skills/(cloud)/vercel-deploy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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

This is a functional deployment skill with clear, executable commands and a sensible primary/fallback structure. Its main weaknesses are redundancy between the prerequisites and troubleshooting sections, and the lack of explicit validation steps after deployment. The referenced deploy script (scripts/deploy.sh) is not included in the bundle, making it impossible to verify the fallback path.

Suggestions

Consolidate the sandbox/escalated permissions guidance into a single section instead of repeating it in both Prerequisites and Troubleshooting.

Add a brief validation checkpoint after deployment (e.g., check the JSON output for success/error status) to improve workflow clarity.

Include the referenced scripts/deploy.sh in the bundle or clarify where it comes from, since the fallback path depends entirely on it.

DimensionReasoningScore

Conciseness

Mostly efficient but has some unnecessary explanation. The 'Tell the user' template and some repeated mentions of sandbox permissions/escalated access could be tightened. The troubleshooting section largely repeats the prerequisites section.

2 / 3

Actionability

Provides concrete, executable commands for both primary and fallback deployment paths. The bash commands are copy-paste ready with clear flags (-y, --prod), specific timeout guidance (600000ms), and concrete script paths.

3 / 3

Workflow Clarity

The workflow follows a clear primary path → fallback pattern, but lacks explicit validation checkpoints. There's no step to verify the build succeeded before sharing the URL, and the error recovery flow (auth failure → fallback script) is implicit rather than structured as a decision tree.

2 / 3

Progressive Disclosure

Content is reasonably structured with clear sections (Quick Start, Fallback, Production, Troubleshooting), but the bundle has no supporting files despite referencing 'scripts/deploy.sh'. The troubleshooting section could be separated or the prerequisites and troubleshooting sections consolidated to avoid redundancy.

2 / 3

Total

9

/

12

Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description with excellent trigger terms, clear completeness, and outstanding distinctiveness through its explicit exclusion clause. The main weakness is that the specificity of capabilities could be improved by listing more concrete actions beyond the general 'deploy' verb, such as managing domains, environment variables, or checking deployment logs.

Suggestions

Add more specific concrete actions beyond 'deploy', such as 'configure custom domains, manage environment variables, check deployment status, create preview and production deployments' to improve specificity.

DimensionReasoningScore

Specificity

The description names the domain (Vercel deployment) and the general action (deploy applications and websites), but doesn't list multiple specific concrete actions like managing environment variables, checking deployment status, rolling back, or configuring domains.

2 / 3

Completeness

Clearly answers both 'what' (deploy applications and websites to Vercel) and 'when' (explicit 'Use when' clause with trigger phrases), plus includes a helpful 'Do NOT use' exclusion clause that further clarifies scope.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'deploy my app', 'deploy and give me the link', 'push this live', 'create a preview deployment', plus the keyword 'Vercel'. These are realistic phrases users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with the explicit 'Vercel' niche and the 'Do NOT use' clause that explicitly differentiates from Netlify, Cloudflare, and Render deployment skills, making conflicts very unlikely.

3 / 3

Total

11

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-skills
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.