Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Deploy and manage Vercel projects. Use when deploying applications to Vercel, managing environment variables, checking deployment status, viewing logs, or performing Vercel operations. Supports production and preview deployments. Practical infrastructure operations - no "AI will build your app" magic.
Deploy and manage Vercel projects. Use when deploying applications to Vercel, managing environment variables, checking deployment status, viewing logs, or performing Vercel operations. Supports production and preview deployments. Practical infrastructure operations - no "AI will build your app" magic.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Deploy and manage Vercel projects. No "AI will build your app" nonsense - just practical Vercel operations.
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
# Deploy to preview scripts/vercel_deploy.sh --project bountylock --preview # Deploy to production scripts/vercel_deploy.sh --project bountylock --production
# 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
# Get latest deployment scripts/vercel_status.sh --project bountylock # Get specific deployment scripts/vercel_status.sh --deployment dpl_abc123
# Get deployment logs scripts/vercel_logs.sh --deployment dpl_abc123 # Get runtime logs scripts/vercel_logs.sh --project bountylock --function api/bounties
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 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
# 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
Token Scope: Use project-scoped tokens when possible Rotation: Rotate tokens periodically Audit: Review deployment logs regularly Secrets: Never commit tokens to git
"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
Vercel API Reference: See vercel-api.md for complete API documentation Deployment Patterns: See deployment-patterns.md for common deployment workflows
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.