From monskills
Deploy a web app to Vercel without installing the Vercel CLI or authenticating. Uses the Vercel claimable deploy endpoint to return a preview URL and a claim URL.
npx claudepluginhub therealharpaljadeja/monskills --plugin monskillsThis skill uses the workspace's default tool permissions.
This method requires no Vercel CLI installation and no authentication. It uses the Vercel claimable deploy endpoint. It returns a **Preview URL** (live site) and a **Claim URL** (to transfer the deployment to the user's Vercel account).
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.
This method requires no Vercel CLI installation and no authentication. It uses the Vercel claimable deploy endpoint. It returns a Preview URL (live site) and a Claim URL (to transfer the deployment to the user's Vercel account).
package.json.tgz (excluding node_modules, .git, .env)https://claude-skills-deploy.vercel.com/api/deployThe project must have a vercel.json at its root. Without it, Vercel will not detect the framework and the build will fail with No Output Directory named "public" found.
Create vercel.json in the project root:
{
"framework": "nextjs"
}
First, download the deploy script and make it executable:
curl -sO https://skills.devnads.com/vercel-deploy/deploy.sh && chmod +x deploy.sh
Then run it from the project directory or pass the path as an argument:
# Deploy current directory
bash deploy.sh
# Deploy a specific directory (e.g. web/)
bash deploy.sh web/
# Deploy an existing tarball
bash deploy.sh project.tgz
The script auto-detects the framework from package.json, packages the project, uploads it, waits for the build to complete, and outputs both URLs.
The script checks package.json dependencies to detect the framework. Order matters — more specific frameworks are checked first:
| Dependency | Framework value |
|---|---|
next | nextjs |
@remix-run/* | remix |
gatsby | gatsby |
@react-router/* | react-router |
astro | astro |
@sveltejs/kit | sveltekit-1 |
nuxt | nuxtjs |
@solidjs/start | solidstart-1 |
@angular/core | angular |
react-scripts | create-react-app |
vite | vite |
If no framework is detected, it passes null and Vercel will attempt to auto-detect.
Always show both URLs:
Do not curl or fetch the deployed URL to verify it works. Just return the links to the user.