Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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).
.claude/skills/tech-leads-club-vercel-deploy/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-05 | ✗→✓ | ▲ Improved | -50% | 0% |
| case-09 | ✗→✓ | ▲ Improved | -51% | 0% |
| case-10 | ✗→✓ | ▲ Improved | -2% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -48% | 0% |
| case-15 | ✗→✓ | ▲ Improved | -37% | 0% |
Deploy any project to Vercel instantly. Always deploy as preview (not production) unless the user explicitly asks for production.
sandbox_permissions=require_escalated.Just run this (with a 10 minute timeout):
bashvercel deploy [path] -y
Important: Use a 10 minute (600000ms) timeout for the deploy command since builds can take a while.
If that fails with "No existing credentials found", use the fallback method below.
If CLI fails with auth error, use the deploy script:
bash# Deploy current directory bash scripts/deploy.sh # Deploy specific project bash scripts/deploy.sh /path/to/project # Deploy existing tarball bash scripts/deploy.sh /path/to/project.tgz
The script handles framework detection, packaging, and deployment. It waits for the build to complete and returns JSON with previewUrl and claimUrl.
Tell the user: "Your deployment is ready at previewUrl]. Claim it at claimUrl] to manage your deployment."
Only if user explicitly asks:
bashvercel deploy [path] --prod -y
Show the user the deployment URL. For fallback deployments, also show the claim URL.
Do not curl or fetch the deployed URL to verify it works. Just return the link.
If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the deploy with escalated permissions (use sandbox_permissions=require_escalated). The deploy requires escalated network access when sandbox networking blocks outbound requests.
Example guidance to the user:
The deploy needs escalated network access to deploy to Vercel. I can rerun the command with escalated permissions—want me to proceed?| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-04 | fail→fail | 9,128 | 57,476 | +530% | 1 | 1 | 0% | 1,536 | 797 | -48% | 0 | 0 | — |
case-01 | fail→fail | 2,397 | 4,320 | +80% | 1 | 1 | 0% | 278 | 704 | +153% | 0 | 0 | — |
case-02 | fail→fail | 4,735 | 5,377 | +14% | 1 | 1 | 0% | 831 | 738 | -11% | 0 | 0 | — |
case-03 | fail→fail | 3,877 | 5,784 | +49% | 1 | 1 | 0% | 674 | 857 | +27% | 0 | 0 | — |
case-05 | fail→pass | 10,079 | 2,626 | -74% | 1 | 1 | 0% | 1,759 | 888 | -50% | 0 | 0 | — |
case-06 | pass→pass | 6,839 | 3,182 | -53% | 1 | 1 | 0% | 613 | 1,031 | +68% | 0 | 0 | — |
case-07 | fail→fail | 52,992 | 5,713 | -89% | 1 | 1 | 0% | 1,723 | 1,507 | -13% | 0 | 0 | — |
case-08 | fail→fail | 13,301 | 4,423 | -67% | 1 | 1 | 0% | 2,308 | 1,256 | -46% | 0 | 0 | — |
case-14 | pass→pass | 7,865 | 2,197 | -72% | 1 | 1 | 0% | 1,267 | 850 | -33% | 0 | 0 | — |
case-09 | fail→pass | 8,604 | 1,787 | -79% | 1 | 1 | 0% | 1,568 | 771 | -51% | 0 | 0 | — |
case-10 | fail→pass | 4,657 | 2,298 | -51% | 1 | 1 | 0% | 839 | 819 | -2% | 0 | 0 | — |
case-11 | pass→pass | 3,926 | 2,235 | -43% | 1 | 1 | 0% | 836 | 901 | +8% | 0 | 0 | — |
case-12 | fail→fail | 6,008 | 4,573 | -24% | 1 | 1 | 0% | 1,011 | 714 | -29% | 0 | 0 | — |
case-13 | fail→pass | 7,464 | 1,285 | -83% | 1 | 1 | 0% | 1,265 | 660 | -48% | 0 | 0 | — |
case-15 | fail→pass | 7,328 | 1,801 | -75% | 1 | 1 | 0% | 1,259 | 791 | -37% | 0 | 0 | — |
case-16 | pass→pass | 3,656 | 1,369 | -63% | 1 | 1 | 0% | 529 | 648 | +22% | 0 | 0 | — |
case-17 | pass→pass | 9,115 | 1,748 | -81% | 1 | 1 | 0% | 1,675 | 705 | -58% | 0 | 0 | — |
case-18 | fail→pass | 7,924 | 1,544 | -81% | 1 | 1 | 0% | 1,279 | 662 | -48% | 0 | 0 | — |
case-19 | pass→fail | 7,546 | 3,049 | -60% | 1 | 1 | 0% | 1,324 | 932 | -30% | 0 | 0 | — |
case-20 | pass→pass | 8,509 | 6,096 | -28% | 1 | 1 | 0% | 1,753 | 1,547 | -12% | 0 | 0 | — |
case-21 | pass→pass | 12,689 | 5,664 | -55% | 1 | 1 | 0% | 2,691 | 1,633 | -39% | 0 | 0 | — |
case-22 | pass→pass | 5,355 | 3,162 | -41% | 1 | 1 | 0% | 885 | 1,028 | +16% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 17 counted toward the lift figure. The other 5 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +23 percentage points is the difference between those two pass rates over the 17 comparable cases. 4 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.