[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71TJR435MQBVMX33P9J5H0P":3,"skill-same:01M71TJR435MQBVMX33P9J5H0P":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71TJR435MQBVMX33P9J5H0P","vercel-automation",null,"Automate Vercel tasks via Rube MCP (Composio): manage deployments, domains, DNS, env vars, projects, and teams. Always search tools first for current schemas.","javiertarazon\u002Fide-agente-free-jt7-","javiertarazon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153141207?v=4","01M71R52TB3S9HXKH6WSNT8A7V","01M71R52VG5KS2DKDDH4GDQ30A",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fvercel-automation\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"automation","vercel automation","vercel","via","first","env","tasks","dns","unknown","MCP","deployments","teams","domains","schemas","search","manage","env vars","for","projects","community","2026-11-10 13:02:02",false,"---\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.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\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","# 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",{"name":5,"risk":31,"source":42,"requires":48,"description":7},{"mcp":49},[50],"rube","release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Fvercel-automation","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-","https:\u002F\u002Fgithub.com\u002Fjaviertarazon","2026-07-12 07:10:45",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add javiertarazon\u002Fide-agente-free-jt7- --skill vercel-automation",{"tool":63,"command":64},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill vercel-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill vercel-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fvercel-automation\u002FSKILL.md",true,[],[72,100,118,136,151,173],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":81,"publishedAt":43},"01M71TQ7Q6Z10VWF3C2H5X1KW9","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[82,83,84,42,85,86,87,88,89,31,90,91,92,93,94,95,96,97,98,99],"zustand","store","zustand store ts","middleware","implementing","use","react state management","when","react","with","state","create","state management","typescript","action","management","separation","global",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":107,"publishedAt":43},"01M71TQ5EAR40G6W0MV5ZDVEZT","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[106],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[108,109,23,42,110,40,37,36,32,31,27,26,111,112,113,114,115,116,97,117],"zoom automation","zoom","creation","meeting","search tools","tracking","webinars","composio","recordings","Tools",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":43},"01M71TQ29B1EYBCEAP1ZBGXQ1A","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[124],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[126,127,23,128,129,130,42,131,132,40,38,37,36,133,32,31,134,29,135,93],"crm automation","zoho crm automation","crm","zoho crm","zoho","leads","manage leads","records","convert","contacts",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":43},"01M71TPZPMN60DH0XV58KVHY23","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[142],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[144,23,145,42,40,37,36,32,146,31,29,147,148,27,26,149,112,115,117,150],"zendesk automation","zendesk","organizations","replies","users","tickets","automate",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":43},"01M71TPXDWKHKG4N6TVEPXWD0N","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[158,159,160,161,162,163,164,165,166,23,167,31,168,169,170,171,172,150],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":182,"publishedAt":43},"01M71TPT5T10WXNKW9G7ZXZ27W","youtube-summarizer","Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fyoutube-summarizer\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[183,184,185,186,42,187,188,189,190,191,192,193,168,194,195,196,197,198,199,200],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]