Deploy apps and websites to Vercel and get a URL to share. The workflow defaults to preview deployments, supports production when explicitly requested, and includes an alternative deployment script when CLI credentials are unavailable.
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".
Review the instructions the agent will receive before you install.
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?
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build, review, and refactor ASP.NET Core web applications using official guidance. Helps choose application structure, implement pages and APIs, configure authentication and services, and plan testing, performance improvements, deployment, and version upgrades.
Build and troubleshoot ChatGPT apps with an MCP server that exposes tools and an optional interactive widget. Use current official documentation and examples to create scaffolds, configure security settings, and guide local validation and deployment when requested.
Turn API documentation or existing scripts into reusable command-line tools that Codex can run from any folder. Builds focused read and write commands, consistent JSON output, authentication handling, installation instructions, and a companion skill.
Deploy applications and infrastructure on Cloudflare by matching project needs to services such as Workers and Pages. Guides service selection and authentication checks, with references covering storage, AI, networking, security, and infrastructure configuration.
Turn a vague intention into a concrete goal with clear scope, measurable success criteria, and evidence of completion. Check existing goals before creating one, so the agent has a specific outcome to pursue without duplicating active work.
Turn a linked Figma frame or layer into application code using the Figma MCP server, a connection for accessing design data. Retrieve design details, screenshots, and assets, reuse existing project components, and compare the implementation with the design.