vercel-deploy
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.
What this skill does
# Vercel Deployment & Management Deploy and manage Vercel projects. No "AI will build your app" nonsense - just practical Vercel operations. ## Configuration ### Vercel Setup **Get your token:** 1. Go to https://vercel.com/account/tokens 2. Create token (name it "OpenClaw") 3. Set in environment: ```bash export VERCEL_TOKEN="your-token-here" ``` Or store in `.env`: ``` VERCEL_TOKEN=your-token-here ``` ## Vercel Operations ### Deploy Project ```bash # Deploy to preview scripts/vercel_deploy.sh --project bountylock --preview # Deploy to production scripts/vercel_deploy.sh --project bountylock --production ``` ### Manage Environment Variables ```bash # 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 ```bash # Get latest deployment scripts/vercel_status.sh --project bountylock # Get specific deployment scripts/vercel_status.sh --deployment dpl_abc123 ``` ### View Logs ```bash # 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 1. **Set environment variables:** ```bash # 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 ``` 2. **Deploy:** ```bash scripts/vercel_deploy.sh --project bountylock --production ``` 3. **Check status:** ```bash scripts/vercel_status.sh --project bountylock ``` ### Update Environment Variables ```bash # 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 ```bash # 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 1. **Token Scope:** Use project-scoped tokens when possible 2. **Rotation:** Rotate tokens periodically 3. **Audit:** Review deployment logs regularly 4. **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 - **Vercel API Reference:** See [vercel-api.md](references/vercel-api.md) for complete API documentation - **Deployment Patterns:** See [deployment-patterns.md](references/deployment-patterns.md) for common deployment workflows
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.