Agent skill · practicalswan
deploy-to-vercel
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\".
What it needs
About 9k tokens when loaded.
What this skill does
Deploy to Vercel Deploy any project to Vercel. Always deploy as preview (not production) unless the user explicitly asks for production. The goal is to get the user into the best long-term setup: their project linked to Vercel with git-push deploys. Every method below tries to move the user closer to that state. Step 1: Gather Project State Run all four checks before deciding which method to use: Team selection If the user belongs to multiple teams, present all available team slugs as a bulleted list and ask which one to deploy to. Once the user picks a team, proceed immediately to the next step — do not ask for additional confirmation. Pass the team slug via --scope on all subsequent CLI commands (vercel deploy, vercel link, vercel inspect, etc.): If the project is already linked (.vercel/project.json or .vercel/repo.json exists), the orgId in those files determines the team — no need to ask again. If there is only one team (or just a personal account), skip the prompt and use it directly. About the .vercel/ directory: A linked project has either: .vercel/project.json — created by vercel link (single project linking). Contains projectId and orgId. .vercel/repo.json — created by vercel link --repo (repo-based linking). Contains orgId, remoteName, and a projects array mapping directories to Vercel project IDs. Either file means the project is linked. Check for both. Do NOT use vercel project inspect, vercel ls, or vercel link to detect state in an unlinked directory — without a .vercel/ config, they will interactively prompt (or with --yes, silently link as a side-effect). Only vercel whoami is safe to run anywhere. Step 2: Choose a Deploy Method Linked (.vercel/ exists) + has git remote → Git Push This is the ideal state. The project is linked and has git integration. 1. Ask the user before pushing. Never push without explicit approval: 2. Commit and push: Vercel automatically builds from the push. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills practicalswan/deploy-to-vercel