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).
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 strong skill description with excellent trigger terms, clear completeness with both 'Use when' and 'Do NOT use' clauses, and outstanding distinctiveness through explicit platform differentiation. The main weakness is that the specificity of capabilities could be improved by listing more concrete actions beyond the general 'deploy' action.
Suggestions
Add more specific concrete actions like 'create preview deployments, promote to production, configure environment variables, link projects' to improve specificity.
| 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 beyond 'deploy'. Could mention specific capabilities like linking projects, setting environment variables, managing preview vs production deployments, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (deploy applications and websites to Vercel) and 'when' (explicit 'Use when' clause with trigger phrases). Also includes a helpful 'Do NOT use' clause that further clarifies scope boundaries. | 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 'Vercel' itself. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with explicit platform targeting (Vercel) and an explicit exclusion clause listing competing platforms (Netlify, Cloudflare, Render), making it very unlikely to conflict with similar deployment skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, well-structured deployment skill with clear actionable commands and good organization. Its main weaknesses are minor redundancy (escalated permissions mentioned twice) and the lack of deployment verification steps — the skill explicitly discourages checking if the deployment works, which is a gap in workflow validation. Overall it serves its purpose well as a quick-reference deployment guide.
Suggestions
Remove the duplicate escalated permissions guidance — keep it in Troubleshooting only and reference it from Prerequisites with a brief note like 'See Troubleshooting if sandbox blocks network calls.'
Consider adding a lightweight verification step (e.g., checking the Vercel API for deployment status) instead of completely prohibiting URL verification, or explain why verification is skipped.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some redundancy — the sandbox/escalated permissions point is mentioned in both Prerequisites and Troubleshooting, and the timeout guidance is repeated. The 'Tell the user' instruction and some explanatory sentences could be tightened. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready commands for both the primary CLI approach and the fallback script. Includes specific timeout values, flags (-y, --prod), and clear paths. The fallback script examples cover multiple use cases. | 3 / 3 |
Workflow Clarity | The workflow follows a clear primary → fallback sequence, but lacks explicit validation checkpoints. There's no step to verify the deployment succeeded beyond showing the URL, and the instruction explicitly says 'Do not curl or fetch the deployed URL to verify it works,' which removes a natural verification step without providing an alternative. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~60 lines), the content is well-organized into logical sections (Quick Start, Fallback, Production, Output, Troubleshooting) with clear headers. No unnecessary nesting or external references needed for this scope. | 3 / 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
- tech-leads-club/agent-skills
- Commit
81e7e0d
- 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.