Project Tooling
alinaqi/maggy
gh, vercel, supabase, render CLI and deployment platform setup
Deploys applications to Vercel as previews by default, picking a deploy method from the project's link state, git remote and team.
Install Deploy to Vercel
$ npx skills add vercel-labs/agent-skills --skill deploy-to-vercel -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel-labs/agent-skills deploy-to-vercel --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/deploy-to-vercel .claude/skills/deploy-to-vercel && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deploy-to-vercel" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/deploy-to-vercel into .claude/skills/deploy-to-vercel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-vercel", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vercel-labs/agent-skills/tree/main/skills/deploy-to-vercelType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vercel-labs/agent-skills --skill deploy-to-vercel -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel-labs/agent-skills deploy-to-vercel --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/deploy-to-vercel .agents/skills/deploy-to-vercel && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deploy-to-vercel" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/deploy-to-vercel into .agents/skills/deploy-to-vercel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-vercel", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel-labs/agent-skills --skill deploy-to-vercel -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel-labs/agent-skills deploy-to-vercel --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/deploy-to-vercel .cursor/skills/deploy-to-vercel && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deploy-to-vercel" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/deploy-to-vercel into .cursor/skills/deploy-to-vercel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-vercel", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vercel-labs/agent-skills.git --path skills/deploy-to-vercel--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vercel-labs/agent-skills --skill deploy-to-vercel -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel-labs/agent-skills deploy-to-vercel --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/deploy-to-vercel .gemini/skills/deploy-to-vercel && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deploy-to-vercel" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/deploy-to-vercel into .gemini/skills/deploy-to-vercel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-vercel", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vercel-labs/agent-skills deploy-to-vercelInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vercel-labs/agent-skills --skill deploy-to-vercel -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/deploy-to-vercel .github/skills/deploy-to-vercel && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deploy-to-vercel" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/deploy-to-vercel into .github/skills/deploy-to-vercel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-vercel", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel-labs/agent-skills --skill deploy-to-vercel -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel-labs/agent-skills deploy-to-vercel --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/deploy-to-vercel .opencode/skills/deploy-to-vercel && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deploy-to-vercel" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/deploy-to-vercel into .opencode/skills/deploy-to-vercel/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-vercel", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
deploy-to-vercel- GitHub stars
- 32k
- Used in
- 11 other repos
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,302 words
- Files
- 4
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- None found
At a glance
Deploys applications to Vercel as previews by default, picking a deploy method from the project's link state, git remote and team.
- Works in 2 steps: Gather Project State → Choose a Deploy Method
- Deploying an app and getting a preview link
- SKILL.md covers Step 1: Gather Project State, Step 2: Choose a Deploy Method, Agent-Specific Notes and Output, plus 1 more section
- Runs Shell scripts from its folder; calls vercel, bash and git; reaches vercel.com and claude.ai
What it does
The skill deploys any project to Vercel and always makes a preview deployment unless you explicitly ask for production. Its goal is to move the project toward a linked setup with git-push deploys. It first gathers project state with several checks, including whether a git remote exists and whether `.vercel/project.json` or `.vercel/repo.json` marks the project as linked, and it treats `vercel whoami` as the only command safe to run in an unlinked directory.
When you belong to several teams, it lists the team slugs, asks which to use and then passes that slug with `--scope` on every later CLI command; a linked project's org id already decides the team. For a linked project with a git remote, the preferred method is to commit and push, but only after you approve the push. The bundle also ships `deploy.sh` and `deploy-codex.sh` helper scripts.
When your agent uses it
- Deploying an app and getting a preview link
- Pushing a linked project live through its git integration
- Choosing the right Vercel team when you belong to several
- Creating a preview deployment for a branch
Example prompts
- “Deploy my app and give me the link.”
- “Create a preview deployment of this branch on Vercel.”
- “Push this live to production on our Vercel team.”
Requirements
- The Vercel CLI (`vercel`)
- A Vercel account with access to the team you deploy to
Workflow steps
2 steps, taken from the step headings in SKILL.md.
- Gather Project State
- Choose a Deploy Method
What it can do on your machine
Read from SKILL.md and the folder at commit 063bee9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Shell), which the agent can run.
Shell commands in SKILL.md call:
vercelbashgitnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
vercel.comclaude.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Deploy to Vercel loads about 2.9k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 1,302 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:185
ject (excluding `node_modules`, `.git`, `.env`), uploads it, and waits for the build to complete.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,302 words (~2,936 tokens).
“Deploy any project to Vercel. Always deploy as preview (not production) unless the user explicitly asks for production.”
- name
- deploy-to-vercel
- metadata.author
- vercel
- metadata.version
- 3.0.0
Files
SKILL.md and 3 other files in skills/deploy-to-vercel of vercel-labs/agent-skills.
- SKILL.md
- Archive.zip
- resources/deploy-codex.sh
- resources/deploy.sh
Open the folder on GitHubat commit 063bee9
Used in 11 other repositories
We found 16 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 11 other GitHub owners. This page covers the copy in vercel-labs/agent-skills, which our catalogue first saw on October 7, 2026.
- JetBrains/skillsvercel-deploy-claimable
- ever-works/ever-works.agents/skills/deploy-to-vercel
- vmDeshpande/ai-agent-automation.agents/skills/deploy-to-vercel
- julianromli/ai-skillsskills/deploy-to-vercel
- fujioky/reach.agents/skills/deploy-to-vercel
- CraftOS-dev/CraftBotskills/deploy-to-vercel
- aiskillstore/marketplaceskills/vercel-labs/deploy-to-vercel
- Asymmetric-al/core.agents/skills/deploy-to-vercel.claude/skills/deploy-to-vercel+1 more
- sickn33/agentic-awesome-skillsskills/deploy-to-vercelplugins/agentic-awesome-skills-claude/skills/deploy-to-vercel
- Kilo-Org/kilo-marketplaceskills/deploy-to-vercel
- lingxling/awesome-skills-cnvercel-labs-agent-skills/skills/deploy-to-vercelantigravity-awesome-skills/skills/deploy-to-vercel+1 more
Compare with similar skills
Deploy to Vercel next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deploy to Vercel this skillvercel-labs/agent-skills | 32k | 11 repos | ~2.9k | Automated safety check: Notes | None | |
| Project Toolingalinaqi/maggy | 707 | — | ~2.5k | Automated safety check: Notes | MIT | |
| Vercel CI Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Vercel Deploy Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.7k | Automated safety check: Pass | MIT | |
| DeployHouseofmvps/ultraship | 123 | — | ~4.1k | Automated safety check: Pass | MIT | |
| Olore Vercel Latestolorehq/olore | 104 | — | ~620 | Automated safety check: Pass | MIT |
Similar skills
Vercel CI Integration
jeremylongshore/tons-of-skills-marketplace
Configure Vercel CI/CD with GitHub Actions, preview deployments, and automated testing.
Vercel Deploy Integration
jeremylongshore/tons-of-skills-marketplace
Deploy and manage Vercel production deployments with promotion, rollback, and multi-region strategies.
Deploy
Houseofmvps/ultraship
Pre-flight checks then deploy. An agent skill from Houseofmvps/ultraship.
Olore Vercel Latest
olorehq/olore
Local vercel documentation reference (latest). An agent skill from olorehq/olore.
Quartz Wiki
liangdabiao/llm-wiki
Set up and deploy Quartz v4 static site for markdown wikis. An agent skill from liangdabiao/llm-wiki.
More from vercel-labs/agent-skills
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Vercel CLI With Tokens
vercel-labs/agent-skills
Deploys and manages Vercel projects through the CLI using an access token from the environment or a .env file instead of interactive login.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Related
Categories
Questions about Deploy to Vercel
What does Deploy to Vercel do?
Deploys applications to Vercel as previews by default, picking a deploy method from the project's link state, git remote and team. The skill deploys any project to Vercel and always makes a preview deployment unless you explicitly ask for production. Its goal is to move the project toward a linked setup with git-push deploys.
When should I use Deploy to Vercel?
Deploy to Vercel fits situations like: deploying an app and getting a preview link; pushing a linked project live through its git integration; choosing the right Vercel team when you belong to several; creating a preview deployment for a branch.
How do I install Deploy to Vercel in Claude Code?
Run `npx skills add vercel-labs/agent-skills --skill deploy-to-vercel -a claude-code`. Or copy the skill folder (skills/deploy-to-vercel in vercel-labs/agent-skills) into .claude/skills/deploy-to-vercel in your project. Claude Code loads it when a task matches its description.
How do I install Deploy to Vercel in Codex?
Run `npx skills add vercel-labs/agent-skills --skill deploy-to-vercel -a codex`. Or copy the skill folder (skills/deploy-to-vercel in vercel-labs/agent-skills) into .agents/skills/deploy-to-vercel in your project. Codex loads it when a task matches its description.
Can I use Deploy to Vercel in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel-labs/agent-skills --skill deploy-to-vercel -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploy-to-vercel, .gemini/skills/deploy-to-vercel, .github/skills/deploy-to-vercel and .opencode/skills/deploy-to-vercel in your project.
What does Deploy to Vercel need to run?
Going by SKILL.md and its folder, Deploy to Vercel needs a shell for the scripts in its folder and the command-line tools its instructions call (vercel, bash, git and npm). Our summary lists: The Vercel CLI (`vercel`); A Vercel account with access to the team you deploy to.
Does Deploy to Vercel access the network?
SKILL.md names 2 domains. In commands or code: vercel.com and claude.ai; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Deploy to Vercel safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Deploy to Vercel use?
No licence was found for Deploy to Vercel or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Deploy to Vercel use?
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Deploy to Vercel?
Skills that share tags, products or a category with Deploy to Vercel: Project Tooling (alinaqi/maggy, 707 stars), Vercel CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Vercel Deploy Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Deploy (Houseofmvps/ultraship, 123 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deploy to Vercel?
vercel-labs (a GitHub organization, an official publisher) maintains it in vercel-labs/agent-skills, which has 32,103 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on August 28, 2026.
Source: vercel-labs/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.