使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/hainrixz/claude-webkit --skill vercel-deploy开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
<!-- Copyright (c) 2026 Enrique Rocha (@soyenriquerocha) · tododeia.com · id er-67c88ab3 -->
Note: Inclaude-webkitthis skill is the primary deployment path. CLAUDE.md Phase 6 callsbash .claude/skills/vercel-deploy/scripts/deploy.sh sitedirectly.
Vercel Deploy
Deploy any project to Vercel instantly. Always deploy as preview (not production) unless the user explicitly asks for production.
Prerequisites
- Check whether the Vercel CLI is installed without escalated permissions (for example,
command -v vercel). - Only escalate the actual deploy command if sandboxing blocks the deployment network calls (
sandbox_permissions=require_escalated). - The deployment might take a few minutes. Use appropriate timeout values.
Quick Start
- Check whether the Vercel CLI is installed (no escalation for this check):
command -v vercel- If
vercelis installed, run this (with a 10 minute timeout):
vercel deploy [path] -yImportant: Use a 10 minute (600000ms) timeout for the deploy command since builds can take a while.
- If
vercelis not installed, or if the CLI fails with "No existing credentials found", use the fallback method below.
Fallback (No Auth)
If CLI fails with auth error, use the deploy script:
skill_dir="<path-to-skill>"
# Deploy current directory
bash "$skill_dir/scripts/deploy.sh"
# Deploy specific project
bash "$skill_dir/scripts/deploy.sh" /path/to/project
# Deploy existing tarball
bash "$skill_dir/scripts/deploy.sh" /path/to/project.tgzThe script handles framework detection, packaging, and deployment. It waits for the build to complete and returns JSON with previewUrl and claimUrl.
Tell the user: "Your deployment is ready at [previewUrl]. Claim it at [claimUrl] to manage your deployment."
Production Deploys
Only if user explicitly asks:
vercel deploy [path] --prod -yOutput
Show the user the deployment URL. For fallback deployments, also show the claim URL.
Do not curl or fetch the deployed URL to verify it works. Just return the link.
Troubleshooting
Escalated Network Access
If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the actual deploy command with escalated permissions (use sandbox_permissions=require_escalated). Do not escalate the command -v vercel installation check. The deploy requires escalated network access when sandbox networking blocks outbound requests.
Example guidance to the user:
The deploy needs escalated network access to deploy to Vercel. I can rerun the command with escalated permissions—want me to proceed?