monkilabs/vercel-deployment
src/orchestrator/plugins/vercel/SKILL.md
Vercel deployment workflows, environment management, domain configuration, and build troubleshooting. Use when deploying, checking deployment status, reviewing build logs, or managing environments.
$ install --global
skillsauthnpx skillsauth add monkilabs/opencastle vercel-deploymentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 9:24 AM25.0s1 file scanned
SKILL.md
- name:
- vercel-deployment
- description:
- Vercel deployment workflows, environment management, domain configuration, and build troubleshooting. Use when deploying, checking deployment status, reviewing build logs, or managing environments.
Vercel Deployment
Vercel-specific deployment patterns and MCP tool usage. For project-specific deployment architecture, environment variables, and key files, see deployment-config.md.
Deployment Model
Branch → Environment mapping:
| Branch pattern | Environment |
|----------------|-------------|
| main | Production deployment (auto) |
| feature/*, fix/* | Preview deployment (auto) |
MCP Tools
The Vercel MCP server provides these tools through https://mcp.vercel.com:
| Tool | Purpose |
|------|---------|
| deploy_to_vercel | Trigger a deployment |
| get_deployment | Check deployment status and metadata |
| get_deployment_build_logs | Read build output for debugging |
| get_runtime_logs | Read runtime logs for debugging |
| list_deployments | List recent deployments |
| get_project | Get project configuration |
| list_projects | List all projects in the team |
| list_teams | List available teams |
| search_vercel_documentation | Search Vercel docs |
| check_domain_availability_and_price | Domain availability check |
Environment Variables
Vercel Environment Scoping
Vercel supports three environment scopes — set variables for each appropriately:
| Scope | When Applied | Use For |
|-------|-------------|---------|
| Production | main branch deploys | Live secrets, production API keys |
| Preview | All non-production branches | Staging/test API keys |
| Development | vercel dev local server | Local development overrides |
Best Practices
Verify required env vars exist in production and preview scopes; see REFERENCE.md for details.
Build Troubleshooting
When builds fail, follow this workflow:
- Read build logs — use
get_deployment_build_logsto get the full output - Check common causes:
- Missing environment variables
- Node.js version mismatch (check
enginesinpackage.json) - Build command mismatch (verify in project settings)
- Dependency resolution issues (lockfile out of sync)
- Check runtime logs — use
get_runtime_logsfor post-deploy errors - Verify deployment status — use
get_deploymentto check state and error details
Example troubleshooting commands (MCP payloads)
- Get build logs:
// tool: vercel/get_deployment_build_logs
{ "deployment_id": "dpl_abc123" }
- Get runtime logs:
// tool: vercel/get_runtime_logs
{ "deployment_id": "dpl_abc123", "limit": 200 }
- Re-deploy a specific commit after fixing an issue:
// tool: vercel/deploy_to_vercel
{ "project_id": "proj_xxx", "gitCommitSha": "abcd1234" }
After re-deploying, re-check get_deployment_build_logs and get_runtime_logs to confirm the fix. Repeat until build succeeds.
Cron Jobs (vercel.json)
Configure cron jobs in vercel.json under crons[] with path and schedule.
Related Skills
monkilabs/validation-gates
development
VerifiedTrustedCommunity
Defines 10 sequential validation gates: secret scanning, lint/test/build checks, blast radius analysis, dependency auditing, browser testing, cache management, regression checks, smoke tests. Use when running pre-deploy validation or CI checks, CI/CD pipelines, deployment pipeline validation, pre-merge checks, continuous integration, or pull request validation.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/testing-workflow
development
VerifiedTrustedCommunity
Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/team-lead-reference
development
VerifiedTrustedCommunity
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting delegation session, running multi-agent workflow, delegating work, choosing which model to use, or assigning tasks.
44SKILL.mdUpdated Apr 21, 2026
monkilabs/session-checkpoints
testing
VerifiedTrustedCommunity
Saves, restores session state including task progress, file changes, delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.
44SKILL.mdUpdated Apr 21, 2026