Menú
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".
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Set up a Mac to run the project. Installs Node.js if needed and runs npm install.
Begin the guided building experience. Helps the user brainstorm an idea and start building their first app.
Set up a Windows PC to run the project. Sets PowerShell execution policy, installs Node.js if needed, and runs npm install.
Run health checks and fix problems. Checks if the dev server is running, runs lint and build checks, verifies file integrity, and automatically fixes any issues found.
Context-aware help for when someone is stuck, confused, or needs guidance. Reads the conversation and project state to give specific, relevant help.
Deploy the app to the internet and get a shareable link. Triggers on "$deploy", "deploy my app", "push this live", "put it on the internet", or any deployment request. Handles build verification, deployment to Vercel, and guides the user through sharing their creation.
| name | vercel-deploy |
| description | 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". |
Note: In the Make Something project, the
$deployskill is the primary entry point for deployment. If$deployexists, defer to it instead of running this skill directly.
Deploy any project to Vercel instantly. Always deploy as preview (not production) unless the user explicitly asks for production.
command -v vercel).sandbox_permissions=require_escalated).command -v vercel
vercel is installed, run this (with a 10 minute timeout):vercel deploy [path] -y
Important: Use a 10 minute (600000ms) timeout for the deploy command since builds can take a while.
vercel is not installed, or if the CLI fails with "No existing credentials found", use the fallback method below.If CLI fails with auth error, use the deploy script:
skill_dir="<path-to-skill>"
# Deploy current directory
bash "$skill_dir/scripts/deploy.sh"
# Deploy specific project
bash "$skill_dir/scripts/deploy.sh" /path/to/project
# Deploy existing tarball
bash "$skill_dir/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:
vercel 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 actual deploy command with escalated permissions (use sandbox_permissions=require_escalated). Do not escalate the command -v vercel installation check. 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?