首页 › 龙虾技能列表 › Vercel Deploy — 技能工具

Vercel Deploy — 技能工具

v1.0.0

[自动翻译] Deploy and manage Vercel projects. Use when deploying applications to Vercel, managing environment variables, checking deployment status, viewing logs...

1· 4,400·0 当前·0 累计
by @nightfullstar·MIT-0
下载技能包
License
MIT-0
最后更新
2026/2/5
安全扫描
VirusTotal
无害
查看报告
OpenClaw
可疑
medium confidence
The skill's files mostly match a Vercel deployment helper, but there are inconsistencies and a few security/practical concerns (undeclared token in registry metadata, missing referenced script, and token-handling that can leak credentials).
评估建议
This skill appears to implement legitimate Vercel deployment helpers, but review a few points before installing: - The code expects VERCEL_TOKEN but the registry metadata does not declare it — assume you must provide a Vercel token. Prefer project-scoped tokens and rotate them regularly. - The scripts pass the token via the --token command-line flag and README suggests echoing the token into ~/.bashrc. Both approaches risk exposing the token (process lists, backups). Consider editing the script...
详细分析 ▾
⚠ 用途与能力
Name/description and the included scripts (deploy/env/status) coherently implement a Vercel deployment helper. However the registry metadata declares no required environment variables or primary credential while the SKILL.md and all scripts require VERCEL_TOKEN — a metadata vs implementation mismatch. The SKILL.md/README also reference a scripts/vercel_logs.sh that is not present in the file manifest, which is an operational inconsistency.
⚠ 指令范围
Runtime instructions are narrowly scoped to Vercel operations (deployments, env vars, status/logs) and do not request unrelated data. But instructions and scripts recommend persisting VERCEL_TOKEN in shell startup files and the scripts pass the token using the --token CLI flag. Passing tokens on the command line can expose them via process lists on multi-user systems; persisting in ~/.bashrc also increases risk if the machine is shared or backed up to remote storage.
ℹ 安装机制
No install spec is provided (instruction-only), which minimizes install-time risk. The scripts invoke npx to run the Vercel CLI; npx will fetch packages from the npm registry on first run, which is expected for a CLI-based deployer but still means remote code will be executed at runtime. There are no downloads from arbitrary URLs or other high-risk install behaviors.
⚠ 凭证需求
Only one credential is actually required (VERCEL_TOKEN), which is proportionate for a Vercel deploy tool. However the registry metadata does not declare this requirement (incoherent). Also the token handling (CLI flag + encouraging echo into .bashrc) increases the chance of accidental exposure; the skill should explicitly document safer alternatives (use project-scoped tokens, avoid command-line args, prefer ephemeral CI secrets or OS-level secret stores).
✓ 持久化与权限
The skill is not marked always:true and does not request system-wide privileges or modify other skills' configurations. The documentation suggests user actions to persist the token in shell profiles (which would be a user-initiated change), but the skill itself does not claim elevated or permanent privileges.
安全有层次，运行前请审查代码。

License

MIT-0

可自由使用、修改和再分发，无需署名。

运行时依赖

无特殊依赖

版本

latestv1.0.02026/2/5
● 无害

安装命令 点击复制

官方npx clawhub@latest install vercel-deploy
镜像加速npx clawhub@latest install vercel-deploy --registry https://cn.clawhub-mirror.com

技能文档

Deploy and manage Vercel projects. No "AI will build your app" nonsense - just practical Vercel operations.

Configuration

Vercel Setup

Get your token:

  • Go to https://vercel.com/account/tokens
  • Create token (name it "OpenClaw")
  • Set in environment:
export VERCEL_TOKEN="your-token-here"

Or store in .env: 

VERCEL_TOKEN=your-token-here

Vercel Operations

Deploy Project

# Deploy to preview
scripts/vercel_deploy.sh --project bountylock --preview
# Deploy to production
scripts/vercel_deploy.sh --project bountylock --production

Manage Environment Variables

# List env vars
scripts/vercel_env.sh --project bountylock --list
# Set env var
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_RPC_URL \
  --value "https://sepolia.base.org" \
  --env production
# Delete env var
scripts/vercel_env.sh --project bountylock --delete \
  --key OLD_VAR \
  --env production

Check Deployment Status

# Get latest deployment
scripts/vercel_status.sh --project bountylock
# Get specific deployment
scripts/vercel_status.sh --deployment dpl_abc123

View Logs

# Get deployment logs
scripts/vercel_logs.sh --deployment dpl_abc123
# Get runtime logs
scripts/vercel_logs.sh --project bountylock --function api/bounties

Common Workflows

Initial Testnet Deployment

  • Set environment variables:
# Contract addresses (after deploying to Sepolia)
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_CONTRACT_ADDRESS \
  --value "0x..." \
  --env production
# RPC URL
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_RPC_URL \
  --value "https://sepolia.base.org" \
  --env production
# Chain ID
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_CHAIN_ID \
  --value "84532" \
  --env production
  • Deploy:
scripts/vercel_deploy.sh --project bountylock --production
  • Check status:
scripts/vercel_status.sh --project bountylock

Update Environment Variables

# Update contract address after redeployment
scripts/vercel_env.sh --project bountylock --set \
  --key NEXT_PUBLIC_CONTRACT_ADDRESS \
  --value "0xNEW_ADDRESS" \
  --env production
# Trigger new deployment to use updated vars
scripts/vercel_deploy.sh --project bountylock --production

Debug Deployment Issues

# Get latest deployment info
scripts/vercel_status.sh --project bountylock
# Get build logs
scripts/vercel_logs.sh --deployment dpl_abc123
# Check environment variables
scripts/vercel_env.sh --project bountylock --list

Security Best Practices

  • Token Scope: Use project-scoped tokens when possible
  • Rotation: Rotate tokens periodically
  • Audit: Review deployment logs regularly
  • Secrets: Never commit tokens to git

Troubleshooting

"Authentication failed"

  • Check token is set correctly
  • Verify token hasn't expired

"Project not found"

  • Verify project name matches Vercel project
  • Check account has access to project

"Deployment failed"

  • Check build logs: scripts/vercel_logs.sh --deployment dpl_xxx
  • Verify environment variables are set correctly
  • Check for build errors in code

Reference Files

数据来源：ClawHub ↗ · 中文优化：龙虾技能库
OpenClaw 技能定制 / 插件定制 / 私有工作流定制

免费技能或插件可能存在安全风险，如需更匹配、更安全的方案，建议联系付费定制

了解定制服务