[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-8944e60f-c352-42d2-8185-673a19617393":3,"$fx2E4GDjBpH98xoZtCf2fRCthBZ2X2hu2-0-mZa8-j_A":43},{"id":4,"title":5,"description":6,"categoryId":7,"moduleId":8,"tags":9,"prompt":10,"icon":11,"source":12,"sourceUrl":13,"authorId":14,"authorName":15,"isPublic":16,"stars":17,"runs":18,"createdAt":19,"updatedAt":19,"module":20,"category":27,"packages":34},"8944e60f-c352-42d2-8185-673a19617393","vercel-automation","通过Rube MCP（Composio）自动化Vercel任务：管理部署、域名、DNS、环境变量、项目和团队。始终首先搜索当前架构的工具。","cat_prod_automation","mod_productivity","sickn33,productivity","---\nname: vercel-automation\ndescription: \"Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Vercel Automation via Rube MCP\n\nAutomate Vercel platform operations through Composio's Vercel toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Vercel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `vercel`\n3. If connection is not ACTIVE, follow the returned auth link to complete Vercel OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Monitor and Inspect Deployments\n\n**When to use**: User wants to list, inspect, or debug deployments\n\n**Tool sequence**:\n1. `VERCEL_LIST_ALL_DEPLOYMENTS` or `VERCEL_GET_DEPLOYMENTS` - List deployments with filters [Required]\n2. `VERCEL_GET_DEPLOYMENT` or `VERCEL_GET_DEPLOYMENT_DETAILS` - Get specific deployment info [Optional]\n3. `VERCEL_GET_DEPLOYMENT_LOGS` or `VERCEL_GET_RUNTIME_LOGS` - View build\u002Fruntime logs [Optional]\n4. `VERCEL_GET_DEPLOYMENT_EVENTS` - Get deployment event timeline [Optional]\n5. `VERCEL_LIST_DEPLOYMENT_CHECKS` - View deployment check results [Optional]\n\n**Key parameters**:\n- `projectId`: Filter deployments by project\n- `state`: Filter by deployment state (e.g., 'READY', 'ERROR', 'BUILDING')\n- `limit`: Number of deployments to return\n- `target`: Filter by environment ('production', 'preview')\n- `deploymentId` or `idOrUrl`: Specific deployment identifier\n\n**Pitfalls**:\n- Deployment IDs and URLs are both accepted as identifiers in most endpoints\n- Build logs and runtime logs are separate; use the appropriate tool\n- `VERCEL_GET_DEPLOYMENT_LOGS` returns build logs; `VERCEL_GET_RUNTIME_LOGS` returns serverless function logs\n- Deployment events include status transitions and are useful for debugging timing issues\n\n### 2. Create and Manage Deployments\n\n**When to use**: User wants to trigger a new deployment\n\n**Tool sequence**:\n1. `VERCEL_LIST_PROJECTS` - Find the target project [Prerequisite]\n2. `VERCEL_CREATE_NEW_DEPLOYMENT` - Trigger a new deployment [Required]\n3. `VERCEL_GET_DEPLOYMENT` - Monitor deployment progress [Optional]\n\n**Key parameters**:\n- `name`: Project name for the deployment\n- `target`: Deployment target ('production' or 'preview')\n- `gitSource`: Git repository source with ref\u002Fbranch info\n- `files`: Array of file objects for file-based deployments\n\n**Pitfalls**:\n- Either `gitSource` or `files` must be provided, not both\n- Git-based deployments require proper repository integration\n- Production deployments update the production domain alias automatically\n- Deployment creation is asynchronous; poll with GET_DEPLOYMENT for status\n\n### 3. Manage Environment Variables\n\n**When to use**: User wants to add, list, or remove environment variables for a project\n\n**Tool sequence**:\n1. `VERCEL_LIST_PROJECTS` - Find the project ID [Prerequisite]\n2. `VERCEL_LIST_ENV_VARIABLES` - List existing env vars [Required]\n3. `VERCEL_ADD_ENVIRONMENT_VARIABLE` - Add a new env var [Optional]\n4. `VERCEL_DELETE_ENVIRONMENT_VARIABLE` - Remove an env var [Optional]\n\n**Key parameters**:\n- `projectId`: Target project identifier\n- `key`: Environment variable name\n- `value`: Environment variable value\n- `target`: Array of environments ('production', 'preview', 'development')\n- `type`: Variable type ('plain', 'secret', 'encrypted', 'sensitive')\n\n**Pitfalls**:\n- Environment variable names must be unique per target environment\n- `type: 'secret'` variables cannot be read back after creation; only the ID is returned\n- Deleting an env var requires both `projectId` and the env var `id` (not the key name)\n- Changes require a new deployment to take effect\n\n### 4. Manage Domains and DNS\n\n**When to use**: User wants to configure custom domains or manage DNS records\n\n**Tool sequence**:\n1. `VERCEL_GET_DOMAIN` - Check domain status and configuration [Required]\n2. `VERCEL_GET_DOMAIN_CONFIG` - Get DNS\u002FSSL configuration details [Optional]\n3. `VERCEL_LIST_PROJECT_DOMAINS` - List domains attached to a project [Optional]\n4. `VERCEL_GET_DNS_RECORDS` - List DNS records for a domain [Optional]\n5. `VERCEL_CREATE_DNS_RECORD` - Add a new DNS record [Optional]\n6. `VERCEL_UPDATE_DNS_RECORD` - Modify an existing DNS record [Optional]\n\n**Key parameters**:\n- `domain`: Domain name (e.g., 'example.com')\n- `name`: DNS record name\u002Fsubdomain\n- `type`: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', 'SRV')\n- `value`: DNS record value\n- `ttl`: Time-to-live in seconds\n\n**Pitfalls**:\n- Domain must be added to the Vercel account before DNS management\n- SSL certificates are auto-provisioned but may take time for new domains\n- CNAME records at the apex domain are not supported; use A records instead\n- MX records require priority values\n\n### 5. Manage Projects\n\n**When to use**: User wants to list, inspect, or update project settings\n\n**Tool sequence**:\n1. `VERCEL_LIST_PROJECTS` - List all projects [Required]\n2. `VERCEL_GET_PROJECT` - Get detailed project information [Optional]\n3. `VERCEL_UPDATE_PROJECT` - Modify project settings [Optional]\n\n**Key parameters**:\n- `idOrName`: Project ID or name for lookup\n- `name`: Project name for updates\n- `framework`: Framework preset (e.g., 'nextjs', 'vite', 'remix')\n- `buildCommand`: Custom build command override\n- `rootDirectory`: Root directory if not repo root\n\n**Pitfalls**:\n- Project names are globally unique within a team\u002Faccount\n- Changing framework settings affects subsequent deployments\n- `rootDirectory` is relative to the repository root\n\n### 6. Team Management\n\n**When to use**: User wants to view team info or list team members\n\n**Tool sequence**:\n1. `VERCEL_LIST_TEAMS` - List all teams the user belongs to [Required]\n2. `VERCEL_GET_TEAM` - Get detailed team information [Optional]\n3. `VERCEL_GET_TEAM_MEMBERS` - List members of a specific team [Optional]\n\n**Key parameters**:\n- `teamId`: Team identifier\n- `limit`: Number of results per page\n- `role`: Filter members by role\n\n**Pitfalls**:\n- Team operations require appropriate team-level permissions\n- Personal accounts have no teams; team endpoints return empty results\n- Member roles include 'OWNER', 'MEMBER', 'DEVELOPER', 'VIEWER'\n\n## Common Patterns\n\n### ID Resolution\n\n**Project name -> Project ID**:\n```\n1. Call VERCEL_LIST_PROJECTS\n2. Find project by name in response\n3. Extract id field for subsequent operations\n```\n\n**Domain -> DNS Records**:\n```\n1. Call VERCEL_GET_DNS_RECORDS with domain name\n2. Extract record IDs for update\u002Fdelete operations\n```\n\n### Pagination\n\n- Use `limit` parameter to control page size\n- Check response for pagination tokens or `next` fields\n- Continue fetching until no more pages are indicated\n\n## Known Pitfalls\n\n**Deployment States**:\n- States include: INITIALIZING, ANALYZING, BUILDING, DEPLOYING, READY, ERROR, CANCELED, QUEUED\n- Only READY deployments are live and serving traffic\n- ERROR deployments should be inspected via logs for failure details\n\n**Environment Variables**:\n- Secret type vars are write-only; values cannot be retrieved after creation\n- Env vars are scoped to environments (production, preview, development)\n- A redeployment is needed for env var changes to take effect\n\n**Rate Limits**:\n- Vercel API has rate limits per endpoint\n- Implement backoff on 429 responses\n- Batch operations where possible to reduce API calls\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | VERCEL_LIST_PROJECTS | limit |\n| Get project details | VERCEL_GET_PROJECT | idOrName |\n| Update project | VERCEL_UPDATE_PROJECT | idOrName, name, framework |\n| List deployments | VERCEL_LIST_ALL_DEPLOYMENTS | projectId, state, limit |\n| Get deployment | VERCEL_GET_DEPLOYMENT | idOrUrl |\n| Create deployment | VERCEL_CREATE_NEW_DEPLOYMENT | name, target, gitSource |\n| Deployment logs | VERCEL_GET_DEPLOYMENT_LOGS | deploymentId |\n| Runtime logs | VERCEL_GET_RUNTIME_LOGS | deploymentId |\n| List env vars | VERCEL_LIST_ENV_VARIABLES | projectId |\n| Add env var | VERCEL_ADD_ENVIRONMENT_VARIABLE | projectId, key, value, target |\n| Delete env var | VERCEL_DELETE_ENVIRONMENT_VARIABLE | projectId, id |\n| Get domain | VERCEL_GET_DOMAIN | domain |\n| Get domain config | VERCEL_GET_DOMAIN_CONFIG | domain |\n| List DNS records | VERCEL_GET_DNS_RECORDS | domain |\n| Create DNS record | VERCEL_CREATE_DNS_RECORD | domain, name, type, value |\n| Update DNS record | VERCEL_UPDATE_DNS_RECORD | domain, recordId |\n| List project domains | VERCEL_LIST_PROJECT_DOMAINS | projectId |\n| List teams | VERCEL_LIST_TEAMS | (none) |\n| Get team | VERCEL_GET_TEAM | teamId |\n| Get team members | VERCEL_GET_TEAM_MEMBERS | teamId, limit |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","","imported","https:\u002F\u002Fgithub.com\u002Fsickn33\u002Fantigravity-awesome-skills","user_system_seed","SkillOPIC",true,57,409,"2026-05-16 13:46:08",{"id":8,"name":21,"slug":22,"icon":23,"description":24,"sort":25,"createdAt":26},"效率工具","productivity","mdi-lightning-bolt-outline","文档处理、数据分析、自动化工作流",4,"2026-05-16 12:53:40",{"id":7,"name":28,"slug":29,"icon":30,"description":31,"moduleId":8,"sort":32,"skillCount":33,"createdAt":26},"自动化","automation","mdi-robot-outline","工作流自动化、批处理",3,101,[35],{"id":36,"skillId":4,"version":37,"fileName":38,"fileSize":39,"filePath":40,"fileHash":41,"manifest":42,"createdAt":19},"9f248494-bbc0-4a1c-94bf-1ad6245b6cf1","1.0.0","vercel-automation.zip",3681,"uploads\u002Fskills\u002F8944e60f-c352-42d2-8185-673a19617393\u002Fvercel-automation.zip","809a3dab93ce4d7a0945e1563740c851a32c095735e5147eba6a85406ee54168","[{\"path\":\"SKILL.md\",\"isDirectory\":false,\"size\":9567}]",{"code":44,"message":45,"data":46},200,"success",{"items":47,"stats":48,"page":51},[],{"averageRating":49,"totalRatings":49,"ratingCounts":50},0,[49,49,49,49,49],{"limit":52,"offset":49,"hasMore":53,"nextOffset":52,"ratedOnly":16},15,false]