Deploy Projects Instantly to Vercel
A skill that deploys web projects to Vercel without authentication, auto-detects frameworks from package.json, and returns live preview and claim URLs.
Why it matters
Effortlessly deploy any project to Vercel without requiring authentication. This skill automates the packaging, framework detection, and deployment process, providing immediate preview and claim URLs.
Outcomes
What it gets done
Package project code for deployment
Auto-detect project framework (Next.js, React, Vue, Svelte, etc.)
Deploy to Vercel and generate preview URLs
Provide claim URLs for account integration
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-vercel-deploy-claimable | bash Capabilities
What this skill does
Runs build pipelines, tests, and deploys to environments.
Pulls structured data fields from unstructured text.
Writes source code or scripts from a description.
Overview
Vercel Deploy
What it does
Vercel Deploy packages local web projects and deploys them to Vercel without requiring authentication. It accepts a directory path or tarball file, auto-detects the framework from package.json, and returns both a Preview URL for the live site and a Claim URL to transfer the deployment to your Vercel account.
How it connects
Use this skill when you need to deploy a web project to Vercel, create preview deployments, push projects live, or obtain deployment links. It works with projects that have a package.json with framework dependencies, as well as static HTML projects.
Source README
Vercel Deploy
Deploy any project to Vercel instantly. No authentication required.
When to Use This Skill
Use this skill when:
- User requests deployment actions like "Deploy my app"
- Deploying to production
- Creating preview deployments
- User asks for deployment links
- Pushing projects live to Vercel
How It Works
- Packages your project into a tarball (excludes
node_modulesand.git) - Auto-detects framework from
package.json - Uploads to deployment service
- Returns Preview URL (live site) and Claim URL (transfer to your Vercel account)
Usage
bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh [path]
Arguments:
path- Directory to deploy, or a.tgzfile (defaults to current directory)
Examples:
### Deploy current directory
bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh
### Deploy specific project
bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh /path/to/project
### Deploy existing tarball
bash /mnt/skills/user/vercel-deploy/scripts/deploy.sh /path/to/project.tgz
Output
Preparing deployment...
Detected framework: nextjs
Creating deployment package...
Deploying...
✓ Deployment successful!
Preview URL: https://skill-deploy-abc123.vercel.app
Claim URL: https://vercel.com/claim-deployment?code=...
The script also outputs JSON to stdout for programmatic use:
{
"previewUrl": "https://skill-deploy-abc123.vercel.app",
"claimUrl": "https://vercel.com/claim-deployment?code=...",
"deploymentId": "dpl_...",
"projectId": "prj_..."
}
Framework Detection
The script auto-detects frameworks from package.json. Supported frameworks include:
- React: Next.js, Gatsby, Create React App, Remix, React Router
- Vue: Nuxt, Vitepress, Vuepress, Gridsome
- Svelte: SvelteKit, Svelte, Sapper
- Other Frontend: Astro, Solid Start, Angular, Ember, Preact, Docusaurus
- Backend: Express, Hono, Fastify, NestJS, Elysia, h3, Nitro
- Build Tools: Vite, Parcel
- And more: Blitz, Hydrogen, RedwoodJS, Storybook, Sanity, etc.
For static HTML projects (no package.json), framework is set to null.
Static HTML Projects
For projects without a package.json:
- If there's a single
.htmlfile not namedindex.html, it gets renamed automatically - This ensures the page is served at the root URL (
/)
Present Results to User
Always show both URLs:
✓ Deployment successful!
Preview URL: https://skill-deploy-abc123.vercel.app
Claim URL: https://vercel.com/claim-deployment?code=...
View your site at the Preview URL.
To transfer this deployment to your Vercel account, visit the Claim URL.
Troubleshooting
Network Egress Error
If deployment fails due to network restrictions (common on claude.ai), tell the user:
Deployment failed due to network restrictions. To fix this:
1. Go to https://claude.ai/settings/capabilities
2. Add *.vercel.com to the allowed domains
3. Try deploying again
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.