Individual skill
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".
skills-imported/deploy-to-vercel/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 55
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytesSKILL.mdcore · 12,377 bytes
Read excerpt
# Deploy to Vercel
Deploy any project to Vercel. **Always deploy as preview** (not production) unless the user explicitly asks for production.
> **Muse adaptation note:** The upstream skill's no-auth fallback scripts (`resources/deploy.sh`, `resources/deploy-codex.sh`) are **not bundled** here — they upload your project files to a third-party endpoint (`https://claude-skills-deploy.vercel.com/api/deploy`). The primary CLI-based workflows below work unchanged. If you need the no-auth fallback, review and fetch the scripts from the upstream repo yourself: https://github.com/vercel-labs/agent-skills (`skills/deploy-to-vercel/resources/`).
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:
```bash
# 1. Check for a git remote