- Home
- Skills
- Vercel Labs
- Agent Skills
- Vercel Deploy Claimable
vercel-deploy-claimable_skill
- JavaScript
22.1k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill vercel-labs/agent-skills --skill vercel-deploy-claimable- SKILL.md3.1 KB
Overview
This skill deploys applications and websites to Vercel instantly and returns a live preview URL plus a claim link to transfer the deployment to your Vercel account. No authentication is required from the user; the skill packages the project, auto-detects the framework, uploads the bundle, and reports results. It works with many frontend and backend frameworks and supports static HTML projects.
How this skill works
The skill creates a tarball of the project (excluding node_modules and .git), inspects package.json to detect the framework or treats the content as static HTML, and uploads the package to the deployment service. On success it prints a human-friendly summary and emits JSON containing previewUrl, claimUrl, deploymentId, and projectId for programmatic use. It also handles simple static-site adjustments like renaming a single non-index HTML file to serve at root.
When to use it
- Push a local project or tarball live to Vercel quickly
- Create a preview deployment for QA or stakeholder review
- Generate a claimable deployment to transfer into a personal or team Vercel account
- Deploy static HTML sites without package.json
- Obtain both a usable preview URL and a claim URL for ownership transfer
Best practices
- Run from the project directory or pass the project path or .tgz file to the deploy script
- Ensure package.json accurately reflects build and start scripts for correct framework detection
- Exclude large node_modules; the script ignores node_modules automatically but keep repositories lean for faster uploads
- Check the JSON output (previewUrl and claimUrl) for automation or CI integration
- If network egress is blocked, add *.vercel.com to allowed domains and retry
Example use cases
- Deploy the current project directory for a quick preview link to share with stakeholders
- Deploy a production-ready build and get a claim URL for transferring ownership to your Vercel account
- Create an ephemeral preview from a feature branch for QA validation
- Upload a static HTML site where a single non-index HTML file should serve at /
- Automate deployments in CI by consuming the JSON output (previewUrl, claimUrl, deploymentId)
FAQ
No. The skill creates preview deployments and returns a claim URL so you can transfer the deployment into your Vercel account if desired.
What happens if framework detection fails?
If package.json is missing or no framework is detected the project is treated as static; for a single non-index HTML file the script will rename it to index.html so the site serves at root.
What output formats are available?
The skill prints a human-readable summary with Preview and Claim URLs and also writes JSON to stdout with previewUrl, claimUrl, deploymentId, and projectId.