Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.
.claude/skills/davepoon-vercel-automation/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-07 | ✗→✓ | ▲ Improved | 64% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 371% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 116% | 0% |
| case-17 | ✗→✓ | ▲ Improved | 58% | 0% |
| case-15 | ✓→✗ | ▼ Worse | 201% | 0% |
Automate Vercel platform operations through Composio's Vercel toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/vercel
RUBE_MANAGE_CONNECTIONS with toolkit vercelRUBE_SEARCH_TOOLS first to get current tool schemasGet Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit vercelWhen to use: User wants to list, inspect, or debug deployments
Tool sequence:
VERCEL_LIST_ALL_DEPLOYMENTS or VERCEL_GET_DEPLOYMENTS - List deployments with filters Required]VERCEL_GET_DEPLOYMENT or VERCEL_GET_DEPLOYMENT_DETAILS - Get specific deployment info Optional]VERCEL_GET_DEPLOYMENT_LOGS or VERCEL_GET_RUNTIME_LOGS - View build/runtime logs Optional]VERCEL_GET_DEPLOYMENT_EVENTS - Get deployment event timeline Optional]VERCEL_LIST_DEPLOYMENT_CHECKS - View deployment check results Optional]Key parameters:
projectId: Filter deployments by projectstate: Filter by deployment state (e.g., 'READY', 'ERROR', 'BUILDING')limit: Number of deployments to returntarget: Filter by environment ('production', 'preview')deploymentId or idOrUrl: Specific deployment identifierPitfalls:
VERCEL_GET_DEPLOYMENT_LOGS returns build logs; VERCEL_GET_RUNTIME_LOGS returns serverless function logsWhen to use: User wants to trigger a new deployment
Tool sequence:
VERCEL_LIST_PROJECTS - Find the target project Prerequisite]VERCEL_CREATE_NEW_DEPLOYMENT - Trigger a new deployment Required]VERCEL_GET_DEPLOYMENT - Monitor deployment progress Optional]Key parameters:
name: Project name for the deploymenttarget: Deployment target ('production' or 'preview')gitSource: Git repository source with ref/branch infofiles: Array of file objects for file-based deploymentsPitfalls:
gitSource or files must be provided, not bothWhen to use: User wants to add, list, or remove environment variables for a project
Tool sequence:
VERCEL_LIST_PROJECTS - Find the project ID Prerequisite]VERCEL_LIST_ENV_VARIABLES - List existing env vars Required]VERCEL_ADD_ENVIRONMENT_VARIABLE - Add a new env var Optional]VERCEL_DELETE_ENVIRONMENT_VARIABLE - Remove an env var Optional]Key parameters:
projectId: Target project identifierkey: Environment variable namevalue: Environment variable valuetarget: Array of environments ('production', 'preview', 'development')type: Variable type ('plain', 'secret', 'encrypted', 'sensitive')Pitfalls:
type: 'secret' variables cannot be read back after creation; only the ID is returnedprojectId and the env var id (not the key name)When to use: User wants to configure custom domains or manage DNS records
Tool sequence:
VERCEL_GET_DOMAIN - Check domain status and configuration Required]VERCEL_GET_DOMAIN_CONFIG - Get DNS/SSL configuration details Optional]VERCEL_LIST_PROJECT_DOMAINS - List domains attached to a project Optional]VERCEL_GET_DNS_RECORDS - List DNS records for a domain Optional]VERCEL_CREATE_DNS_RECORD - Add a new DNS record Optional]VERCEL_UPDATE_DNS_RECORD - Modify an existing DNS record Optional]Key parameters:
domain: Domain name (e.g., 'example.com')name: DNS record name/subdomaintype: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', 'SRV')value: DNS record valuettl: Time-to-live in secondsPitfalls:
When to use: User wants to list, inspect, or update project settings
Tool sequence:
VERCEL_LIST_PROJECTS - List all projects Required]VERCEL_GET_PROJECT - Get detailed project information Optional]VERCEL_UPDATE_PROJECT - Modify project settings Optional]Key parameters:
idOrName: Project ID or name for lookupname: Project name for updatesframework: Framework preset (e.g., 'nextjs', 'vite', 'remix')buildCommand: Custom build command overriderootDirectory: Root directory if not repo rootPitfalls:
rootDirectory is relative to the repository rootWhen to use: User wants to view team info or list team members
Tool sequence:
VERCEL_LIST_TEAMS - List all teams the user belongs to Required]VERCEL_GET_TEAM - Get detailed team information Optional]VERCEL_GET_TEAM_MEMBERS - List members of a specific team Optional]Key parameters:
teamId: Team identifierlimit: Number of results per pagerole: Filter members by rolePitfalls:
Project name -> Project ID:
1. Call VERCEL_LIST_PROJECTS
2. Find project by name in response
3. Extract id field for subsequent operationsDomain -> DNS Records:
1. Call VERCEL_GET_DNS_RECORDS with domain name
2. Extract record IDs for update/delete operationslimit parameter to control page sizenext fieldsDeployment States:
Environment Variables:
Rate Limits:
| Task | Tool Slug | Key Params | |------|-----------|------------| | List projects | VERCEL_LIST_PROJECTS | limit | | Get project details | VERCEL_GET_PROJECT | idOrName | | Update project | VERCEL_UPDATE_PROJECT | idOrName, name, framework | | List deployments | VERCEL_LIST_ALL_DEPLOYMENTS | projectId, state, limit | | Get deployment | VERCEL_GET_DEPLOYMENT | idOrUrl | | Create deployment | VERCEL_CREATE_NEW_DEPLOYMENT | name, target, gitSource | | Deployment logs | VERCEL_GET_DEPLOYMENT_LOGS | deploymentId | | Runtime logs | VERCEL_GET_RUNTIME_LOGS | deploymentId | | List env vars | VERCEL_LIST_ENV_VARIABLES | projectId | | Add env var | VERCEL_ADD_ENVIRONMENT_VARIABLE | projectId, key, value, target | | Delete env var | VERCEL_DELETE_ENVIRONMENT_VARIABLE | projectId, id | | Get domain | VERCEL_GET_DOMAIN | domain | | Get domain config | VERCEL_GET_DOMAIN_CONFIG | domain | | List DNS records | VERCEL_GET_DNS_RECORDS | domain | | Create DNS record | VERCEL_CREATE_DNS_RECORD | domain, name, type, value | | Update DNS record | VERCEL_UPDATE_DNS_RECORD | domain, recordId | | List project domains | VERCEL_LIST_PROJECT_DOMAINS | projectId | | List teams | VERCEL_LIST_TEAMS | (none) | | Get team | VERCEL_GET_TEAM | teamId | | Get team members | VERCEL_GET_TEAM_MEMBERS | teamId, limit |
Powered by Composio
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-21 | pass→pass | 13,381 | 14,032 | +5% | 1 | 1 | 0% | 2,357 | 4,877 | +107% | 0 | 0 | — |
case-01 | fail→fail | 4,674 | 6,241 | +34% | 1 | 1 | 0% | 184 | 2,747 | +1393% | 0 | 0 | — |
case-22 | pass→pass | 7,514 | 6,822 | -9% | 1 | 1 | 0% | 1,617 | 3,722 | +130% | 0 | 0 | — |
case-02 | fail→fail | 11,302 | 4,993 | -56% | 1 | 1 | 0% | 1,339 | 2,726 | +104% | 0 | 0 | — |
case-03 | fail→fail | 6,890 | 4,977 | -28% | 1 | 1 | 0% | 1,403 | 2,688 | +92% | 0 | 0 | — |
case-04 | fail→fail | 4,774 | 5,560 | +16% | 1 | 1 | 0% | 351 | 2,660 | +658% | 0 | 0 | — |
case-05 | pass→pass | 8,072 | 4,501 | -44% | 1 | 1 | 0% | 1,255 | 3,253 | +159% | 0 | 0 | — |
case-06 | pass→pass | 6,345 | 8,559 | +35% | 1 | 1 | 0% | 1,071 | 3,294 | +208% | 0 | 0 | — |
case-07 | fail→pass | 10,607 | 3,621 | -66% | 1 | 1 | 0% | 1,848 | 3,023 | +64% | 0 | 0 | — |
case-08 | pass→pass | 10,966 | 5,860 | -47% | 1 | 1 | 0% | 1,408 | 3,472 | +147% | 0 | 0 | — |
case-09 | pass→pass | 8,406 | 1,935 | -77% | 1 | 1 | 0% | 1,457 | 2,673 | +83% | 0 | 0 | — |
case-10 | pass→pass | 5,373 | 4,932 | -8% | 1 | 1 | 0% | 987 | 3,106 | +215% | 0 | 0 | — |
case-11 | fail→pass | 4,281 | 4,206 | -2% | 1 | 1 | 0% | 680 | 3,201 | +371% | 0 | 0 | — |
case-12 | fail→pass | 8,676 | 2,487 | -71% | 1 | 1 | 0% | 1,257 | 2,711 | +116% | 0 | 0 | — |
case-13 | pass→pass | 6,477 | 1,842 | -72% | 1 | 1 | 0% | 1,057 | 2,696 | +155% | 0 | 0 | — |
case-14 | pass→pass | 6,755 | 1,903 | -72% | 1 | 1 | 0% | 1,193 | 2,640 | +121% | 0 | 0 | — |
case-15 | pass→fail | 5,112 | 6,493 | +27% | 1 | 1 | 0% | 888 | 2,676 | +201% | 0 | 0 | — |
case-16 | pass→pass | 7,203 | 3,634 | -50% | 1 | 1 | 0% | 1,220 | 3,013 | +147% | 0 | 0 | — |
case-17 | fail→pass | 11,004 | 6,528 | -41% | 1 | 1 | 0% | 1,901 | 2,995 | +58% | 0 | 0 | — |
case-18 | pass→fail | 11,799 | 7,652 | -35% | 1 | 1 | 0% | 1,760 | 2,720 | +55% | 0 | 0 | — |
case-19 | pass→pass | 4,115 | 2,980 | -28% | 1 | 1 | 0% | 470 | 2,847 | +506% | 0 | 0 | — |
case-20 | pass→pass | 17,219 | 9,623 | -44% | 1 | 1 | 0% | 3,137 | 4,158 | +33% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 16 counted toward the lift figure. The other 6 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +9 percentage points is the difference between those two pass rates over the 16 comparable cases. 2 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.