vercel-deploy
애플리케이션을 Vercel에 프리뷰 또는 프로덕션 환경으로 배포합니다. Vercel CLI와 폴백 스크립트 기반 배포 방식을 모두 지원하며, 자동 프레임워크 감지 및 패키징을 수행합니다. 사용자가 명시적으로 프로덕션 배포를 요청하지 않는 한 항상 프리뷰로 배포합니다. 프리뷰 URL을 즉시 반환하고, 폴백 배포의 경우 배포를 관리할 수 있는 클레임 URL을 제공합니다. 빌드 완료를 위해 10분 타임아웃이 필요하며, 샌드박스가 아웃바운드를 차단하는 경우에만 네트워크 권한을 상향 조정합니다...
npx skills add https://github.com/openai/skills --skill vercel-deployVercel Deploy
Deploy any project to Vercel instantly. Always deploy as preview (not production) unless the user explicitly asks for production.
Prerequisites
- Check whether the Vercel CLI is installed without escalated permissions (for example,
command -v vercel). - Only escalate the actual deploy command if sandboxing blocks the deployment network calls (
sandbox_permissions=require_escalated). - The deployment might take a few minutes. Use appropriate timeout values.
Quick Start
- Check whether the Vercel CLI is installed (no escalation for this check):
command -v vercel
- If
vercelis 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.
- If
vercelis not installed, or if the CLI fails with "No existing credentials found", use the fallback method below.
Fallback (No Auth)
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."
Production Deploys
Only if user explicitly asks:
vercel deploy [path] --prod -y
Output
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.
Troubleshooting
Escalated Network Access
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?