vercel-deploy

The vercel-deploy skill deploys applications and websites to Vercel in response to requests like deploy my app, push this live, or create a preview deployment. Its default behavior is deliberate: it always creates a preview deployment rather than production unless the user explicitly asks for production, in which case the deploy command adds a production flag.

The workflow begins by checking whether the Vercel CLI is present using a non-escalated check such as command -v vercel. If the CLI is available, it runs the deploy against the target path with automatic confirmation, using a ten-minute (600000 ms) timeout because builds can take several minutes. If the CLI is missing or reports that no credentials are found, it falls back to a bundled deploy.sh script that handles framework detection, packaging, and deployment, waits for the build to complete, and returns JSON containing a preview URL and a claim URL to hand to the user.

The skill is intentionally conservative about verification and permissions: it does not curl or fetch the deployed URL to confirm it works, simply returning the link instead. If deployment fails due to network problems like timeouts, DNS errors, or connection resets under sandboxing, the guidance is to rerun only the actual deploy command with escalated permissions -- never the CLI installation check -- so that outbound requests to Vercel can go through.