vercel-labs/vercel-deploy
Deploy applications and websites to Vercel with a claimable preview. 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". No authentication required - returns preview URL and claimable deployment link.
npx skills add https://github.com/vercel-labs/vercel-deploy-codex-skill --skill vercel-deploy
Deploy any project to Vercel instantly. No authentication required.
.tar.gz (excludes node_modules and .git)package.jsonbash scripts/deploy.sh [path]
Arguments:
path - Directory to deploy, or a .tgz file (defaults to current directory)If you pass a directory, the script will create a .tar.gz before upload.
Examples:
# 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
node_modules and .gitpackage.json, keep framework as null.html file, rename it to index.html before packagingPreparing deployment...
Creating deployment package...
Deploying...
✓ Deployment successful!
Preview URL: https://skill-deploy-abc123.vercel.app
Claim URL: https://vercel.com/claim-deployment?code=...
The script also outputs JSON to stdout for programmatic use.
{
"previewUrl": "https://skill-deploy-abc123.vercel.app",
"claimUrl": "https://vercel.com/claim-deployment?code=...",
"deploymentId": "dpl_...",
"projectId": "prj_..."
}
The script auto-detects frameworks from package.json. Supported frameworks include:
For static HTML projects (no package.json), framework is set to null.
For projects without a package.json:
.html file not named index.html, it gets renamed automatically/)Always show both URLs:
✓ Deployment successful!
Preview URL: https://skill-deploy-abc123.vercel.app
Claim URL: https://vercel.com/claim-deployment?code=...
View your site at the Preview URL.
To transfer this deployment to your Vercel account, visit the Claim URL.
If deployment fails due to network restrictions, tell the user:
Deployment failed due to network restrictions. To fix this:
1. Allow outbound access to *.vercel.com
2. Try deploying again
Take vercel-labs/vercel-deploy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.