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\".
npx skills add sickn33/agentic-awesome-skills --skill deploy-to-vercel --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. ## When to Use - Use this skill when the task matches this 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". ## Step 1: Gather Project State Run all four checks before deciding which method to use: ```bash # 1. Check for a git remote git remote get-url origin 2>/dev/null # 2. Check if locally linked to a Vercel project (either file means linked) cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null # 3. Check if the Vercel CLI is installed and authenticated vercel whoami 2>/dev/null # 4. List available teams (if authenticated) vercel teams list --format json 2>/dev/null ``` ### Team selection If the user belongs to multiple teams, present all available team slugs as a bulleted list and ask whi
- When to Use
- Step 1: Gather Project State
- Team selection
- Step 2: Choose a Deploy Method
- Linked (.vercel/ exists) + has git remote → Git Push
- Linked (.vercel/ exists) + no git remote → vercel deploy
- Not linked + CLI is authenticated → Link first, then deploy
- Not linked + CLI not authenticated → Install, auth, link, deploy
- No-Auth Fallback — claude.ai sandbox
- No-Auth Fallback — Codex sandbox
- Agent-Specific Notes
- Claude Code / terminal-based agents
- Sandboxed environments (claude.ai)
- Codex
git remote get-url origin 2>/dev/null cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null vercel whoami 2>/dev/null vercel teams list --format json 2>/dev/null vercel deploy [path] -y --no-wait --scope <team-slug> git add . git commit -m "deploy: <description of changes>" git push sleep 5 vercel ls --format json
What does the deploy-to-vercel skill do?
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\".
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill deploy-to-vercel --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.