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".
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Critical
Do not install without reviewing
Quality
Discovery
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 solid skill description with excellent trigger terms and completeness. The explicit 'Use when' clause with natural user phrases is a strong point. The main weakness is that the 'what' portion could be more specific about the range of Vercel-related actions supported beyond just 'deploy'.
Suggestions
Expand the capability list with more specific actions, e.g., 'Deploy applications and websites to Vercel, manage preview and production deployments, configure environment variables, and check deployment status.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Vercel deployment) and the general action (deploy applications and websites), but doesn't list multiple specific concrete actions like configuring environment variables, managing domains, checking deployment status, or rolling back. | 2 / 3 |
Completeness | Clearly answers both 'what' (deploy applications and websites to Vercel) and 'when' (explicit 'Use when' clause with specific trigger phrases like 'deploy my app', 'push this live', etc.). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger phrases users would actually say: 'deploy my app', 'deploy and give me the link', 'push this live', 'create a preview deployment'. These cover common variations of deployment requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Vercel specifically, which distinguishes it from generic deployment skills or other platform-specific deployment skills. The trigger terms are deployment-focused and platform-specific, reducing conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive deployment skill with excellent actionability and workflow clarity. The decision tree approach (gather state → choose method → deploy) is well-designed with clear branching logic and safety constraints. The main weakness is length — the document covers many scenarios (5+ deployment methods, 3 agent types, troubleshooting) which makes it somewhat verbose, though most content is justified by the complexity of the task.
Suggestions
Consider splitting agent-specific notes (Claude Code, claude.ai sandbox, Codex) and troubleshooting into separate referenced files to reduce the main SKILL.md length and improve progressive disclosure.
Reduce redundancy in team selection logic — it's explained in Step 1, then re-explained in the 'Not linked + CLI authenticated' and 'Not linked + CLI not authenticated' methods. A single reference back to Step 1 would suffice.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~200+ lines) and includes some redundant explanations (e.g., re-explaining team selection logic multiple times across methods, explaining what .vercel/project.json vs .vercel/repo.json contain). However, most content is genuinely necessary given the complexity of the decision tree. Some tightening is possible but it's not egregiously verbose. | 2 / 3 |
Actionability | Excellent actionability throughout — every method includes specific, executable bash commands with flags explained, concrete examples for each deployment path, and clear instructions for what to tell the user. Commands are copy-paste ready with appropriate flags like `-y`, `--no-wait`, `--scope`. | 3 / 3 |
Workflow Clarity | The skill has a clear decision tree: gather state → choose method → deploy → output. Each method is well-sequenced with explicit steps. Validation is present (vercel inspect for status checks, checking .vercel/ files before acting). Important safety constraints are called out (never push without approval, always preview unless explicitly asked for production, don't run interactive commands in unlinked directories). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a monolithic document that could benefit from splitting agent-specific notes or fallback methods into separate files. The references to deploy.sh and deploy-codex.sh scripts are clear, but the main file is quite long. No bundle files were provided to verify referenced paths. | 2 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- vercel-labs/agent-skills
- Commit
b9c8ee0
- 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.