The skill is the skills/deploy-to-vercel folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
about Vercel Deploy Claimable Skill by @vercel-labs
Deploy applications to Vercel instantly from a conversation, with claimable ownership transfer.
Auto-detects 40+ frameworks from package.json
Returns a preview URL and a claim URL to transfer ownership
Excludes node_modules and .git from uploads
our take
Walks an agent through deploying a project to Vercel from a conversation. It first gathers project state, then picks a deploy method depending on whether the project is linked, has a git remote, and whether the CLI is signed in, with ownership transferable afterwards.
when to use it
You want a quick preview deployment straight from a chat
You are unsure which deploy path fits your project state
You want to hand a deployed project to someone else
before you install
Deploying publishes your code, so check what is in the project first
The source repository publishes no license, so we link to it rather than host a copy
what's inside
The original SKILL.md is organised into these sections:
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)
source and license
Written and maintained by @vercel-labs. No license is published in that repository, so we link to the original and do not host a copy or offer a download. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.