[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71R87EWE2FPFZZ0DRMM5MNB":3,"skill-same:01M71R87EWE2FPFZZ0DRMM5MNB":70},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":13,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M71R87EWE2FPFZZ0DRMM5MNB","amplitude-automation",null,"Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. 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\u002Famplitude-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],"automation","amplitude","amplitude automation","automate","user","events","Tools","composio","activity","search tools","via","first","tasks","unknown","MCP","identification","search","for","community","2026-11-10 13:02:02",false,"---\nname: amplitude-automation\ndescription: \"Automate Amplitude tasks via Rube MCP (Composio): events, user activity, cohorts, user identification. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Amplitude Automation via Rube MCP\n\nAutomate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Amplitude connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `amplitude`\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 `amplitude`\n3. If connection is not ACTIVE, follow the returned auth link to complete Amplitude authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Send Events\n\n**When to use**: User wants to track events or send event data to Amplitude\n\n**Tool sequence**:\n1. `AMPLITUDE_SEND_EVENTS` - Send one or more events to Amplitude [Required]\n\n**Key parameters**:\n- `events`: Array of event objects, each containing:\n  - `event_type`: Name of the event (e.g., 'page_view', 'purchase')\n  - `user_id`: Unique user identifier (required if no `device_id`)\n  - `device_id`: Device identifier (required if no `user_id`)\n  - `event_properties`: Object with custom event properties\n  - `user_properties`: Object with user properties to set\n  - `time`: Event timestamp in milliseconds since epoch\n\n**Pitfalls**:\n- At least one of `user_id` or `device_id` is required per event\n- `event_type` is required for every event; cannot be empty\n- `time` must be in milliseconds (13-digit epoch), not seconds\n- Batch limit applies; check schema for maximum events per request\n- Events are processed asynchronously; successful API response does not mean data is immediately queryable\n\n### 2. Get User Activity\n\n**When to use**: User wants to view event history for a specific user\n\n**Tool sequence**:\n1. `AMPLITUDE_FIND_USER` - Find user by ID or property [Prerequisite]\n2. `AMPLITUDE_GET_USER_ACTIVITY` - Retrieve user's event stream [Required]\n\n**Key parameters**:\n- `user`: Amplitude internal user ID (from FIND_USER)\n- `offset`: Pagination offset for event list\n- `limit`: Maximum number of events to return\n\n**Pitfalls**:\n- `user` parameter requires Amplitude's internal user ID, NOT your application's user_id\n- Must call FIND_USER first to resolve your user_id to Amplitude's internal ID\n- Activity is returned in reverse chronological order by default\n- Large activity histories require pagination via `offset`\n\n### 3. Find and Identify Users\n\n**When to use**: User wants to look up users or set user properties\n\n**Tool sequence**:\n1. `AMPLITUDE_FIND_USER` - Search for a user by various identifiers [Required]\n2. `AMPLITUDE_IDENTIFY` - Set or update user properties [Optional]\n\n**Key parameters**:\n- For FIND_USER:\n  - `user`: Search term (user_id, email, or Amplitude ID)\n- For IDENTIFY:\n  - `user_id`: Your application's user identifier\n  - `device_id`: Device identifier (alternative to user_id)\n  - `user_properties`: Object with `$set`, `$unset`, `$add`, `$append` operations\n\n**Pitfalls**:\n- FIND_USER searches across user_id, device_id, and Amplitude ID\n- IDENTIFY uses special property operations (`$set`, `$unset`, `$add`, `$append`)\n- `$set` overwrites existing values; `$setOnce` only sets if not already set\n- At least one of `user_id` or `device_id` is required for IDENTIFY\n- User property changes are eventually consistent; not immediate\n\n### 4. Manage Cohorts\n\n**When to use**: User wants to list cohorts, view cohort details, or update cohort membership\n\n**Tool sequence**:\n1. `AMPLITUDE_LIST_COHORTS` - List all saved cohorts [Required]\n2. `AMPLITUDE_GET_COHORT` - Get detailed cohort information [Optional]\n3. `AMPLITUDE_UPDATE_COHORT_MEMBERSHIP` - Add\u002Fremove users from a cohort [Optional]\n4. `AMPLITUDE_CHECK_COHORT_STATUS` - Check async cohort operation status [Optional]\n\n**Key parameters**:\n- For LIST_COHORTS: No required parameters\n- For GET_COHORT: `cohort_id` (from list results)\n- For UPDATE_COHORT_MEMBERSHIP:\n  - `cohort_id`: Target cohort ID\n  - `memberships`: Object with `add` and\u002For `remove` arrays of user IDs\n- For CHECK_COHORT_STATUS: `request_id` from update response\n\n**Pitfalls**:\n- Cohort IDs are required for all cohort-specific operations\n- UPDATE_COHORT_MEMBERSHIP is asynchronous; use CHECK_COHORT_STATUS to verify\n- `request_id` from the update response is needed for status checking\n- Maximum membership changes per request may be limited; chunk large updates\n- Only behavioral cohorts support API membership updates\n\n### 5. Browse Event Categories\n\n**When to use**: User wants to discover available event types and categories in Amplitude\n\n**Tool sequence**:\n1. `AMPLITUDE_GET_EVENT_CATEGORIES` - List all event categories [Required]\n\n**Key parameters**:\n- No required parameters; returns all configured event categories\n\n**Pitfalls**:\n- Categories are configured in Amplitude UI; API provides read access\n- Event names within categories are case-sensitive\n- Use these categories to validate event_type values before sending events\n\n## Common Patterns\n\n### ID Resolution\n\n**Application user_id -> Amplitude internal ID**:\n```\n1. Call AMPLITUDE_FIND_USER with user=your_user_id\n2. Extract Amplitude's internal user ID from response\n3. Use internal ID for GET_USER_ACTIVITY\n```\n\n**Cohort name -> Cohort ID**:\n```\n1. Call AMPLITUDE_LIST_COHORTS\n2. Find cohort by name in results\n3. Extract id for cohort operations\n```\n\n### User Property Operations\n\nAmplitude IDENTIFY supports these property operations:\n- `$set`: Set property value (overwrites existing)\n- `$setOnce`: Set only if property not already set\n- `$add`: Increment numeric property\n- `$append`: Append to list property\n- `$unset`: Remove property entirely\n\nExample structure:\n```json\n{\n  \"user_properties\": {\n    \"$set\": {\"plan\": \"premium\", \"company\": \"Acme\"},\n    \"$add\": {\"login_count\": 1}\n  }\n}\n```\n\n### Async Operation Pattern\n\nFor cohort membership updates:\n```\n1. Call AMPLITUDE_UPDATE_COHORT_MEMBERSHIP -> get request_id\n2. Call AMPLITUDE_CHECK_COHORT_STATUS with request_id\n3. Repeat step 2 until status is 'complete' or 'error'\n```\n\n## Known Pitfalls\n\n**User IDs**:\n- Amplitude has its own internal user IDs separate from your application's\n- FIND_USER resolves your IDs to Amplitude's internal IDs\n- GET_USER_ACTIVITY requires Amplitude's internal ID, not your user_id\n\n**Event Timestamps**:\n- Must be in milliseconds since epoch (13 digits)\n- Seconds (10 digits) will be interpreted as very old dates\n- Omitting timestamp uses server receive time\n\n**Rate Limits**:\n- Event ingestion has throughput limits per project\n- Batch events where possible to reduce API calls\n- Cohort membership updates have async processing limits\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- User activity returns events in reverse chronological order\n- Cohort lists may include archived cohorts; check status field\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Send events | AMPLITUDE_SEND_EVENTS | events (array) |\n| Find user | AMPLITUDE_FIND_USER | user |\n| Get user activity | AMPLITUDE_GET_USER_ACTIVITY | user, offset, limit |\n| Identify user | AMPLITUDE_IDENTIFY | user_id, user_properties |\n| List cohorts | AMPLITUDE_LIST_COHORTS | (none) |\n| Get cohort | AMPLITUDE_GET_COHORT | cohort_id |\n| Update cohort members | AMPLITUDE_UPDATE_COHORT_MEMBERSHIP | cohort_id, memberships |\n| Check cohort status | AMPLITUDE_CHECK_COHORT_STATUS | request_id |\n| List event categories | AMPLITUDE_GET_EVENT_CATEGORIES | (none) |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Amplitude Automation via Rube MCP\n\nAutomate Amplitude product analytics through Composio's Amplitude toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Amplitude connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `amplitude`\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 `amplitude`\n3. If connection is not ACTIVE, follow the returned auth link to complete Amplitude authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Send Events\n\n**When to use**: User wants to track events or send event data to Amplitude\n\n**Tool sequence**:\n1. `AMPLITUDE_SEND_EVENTS` - Send one or more events to Amplitude [Required]\n\n**Key parameters**:\n- `events`: Array of event objects, each containing:\n  - `event_type`: Name of the event (e.g., 'page_view', 'purchase')\n  - `user_id`: Unique user identifier (required if no `device_id`)\n  - `device_id`: Device identifier (required if no `user_id`)\n  - `event_properties`: Object with custom event properties\n  - `user_properties`: Object with user properties to set\n  - `time`: Event timestamp in milliseconds since epoch\n\n**Pitfalls**:\n- At least one of `user_id` or `device_id` is required per event\n- `event_type` is required for every event; cannot be empty\n- `time` must be in milliseconds (13-digit epoch), not seconds\n- Batch limit applies; check schema for maximum events per request\n- Events are processed asynchronously; successful API response does not mean data is immediately queryable\n\n### 2. Get User Activity\n\n**When to use**: User wants to view event history for a specific user\n\n**Tool sequence**:\n1. `AMPLITUDE_FIND_USER` - Find user by ID or property [Prerequisite]\n2. `AMPLITUDE_GET_USER_ACTIVITY` - Retrieve user's event stream [Required]\n\n**Key parameters**:\n- `user`: Amplitude internal user ID (from FIND_USER)\n- `offset`: Pagination offset for event list\n- `limit`: Maximum number of events to return\n\n**Pitfalls**:\n- `user` parameter requires Amplitude's internal user ID, NOT your application's user_id\n- Must call FIND_USER first to resolve your user_id to Amplitude's internal ID\n- Activity is returned in reverse chronological order by default\n- Large activity histories require pagination via `offset`\n\n### 3. Find and Identify Users\n\n**When to use**: User wants to look up users or set user properties\n\n**Tool sequence**:\n1. `AMPLITUDE_FIND_USER` - Search for a user by various identifiers [Required]\n2. `AMPLITUDE_IDENTIFY` - Set or update user properties [Optional]\n\n**Key parameters**:\n- For FIND_USER:\n  - `user`: Search term (user_id, email, or Amplitude ID)\n- For IDENTIFY:\n  - `user_id`: Your application's user identifier\n  - `device_id`: Device identifier (alternative to user_id)\n  - `user_properties`: Object with `$set`, `$unset`, `$add`, `$append` operations\n\n**Pitfalls**:\n- FIND_USER searches across user_id, device_id, and Amplitude ID\n- IDENTIFY uses special property operations (`$set`, `$unset`, `$add`, `$append`)\n- `$set` overwrites existing values; `$setOnce` only sets if not already set\n- At least one of `user_id` or `device_id` is required for IDENTIFY\n- User property changes are eventually consistent; not immediate\n\n### 4. Manage Cohorts\n\n**When to use**: User wants to list cohorts, view cohort details, or update cohort membership\n\n**Tool sequence**:\n1. `AMPLITUDE_LIST_COHORTS` - List all saved cohorts [Required]\n2. `AMPLITUDE_GET_COHORT` - Get detailed cohort information [Optional]\n3. `AMPLITUDE_UPDATE_COHORT_MEMBERSHIP` - Add\u002Fremove users from a cohort [Optional]\n4. `AMPLITUDE_CHECK_COHORT_STATUS` - Check async cohort operation status [Optional]\n\n**Key parameters**:\n- For LIST_COHORTS: No required parameters\n- For GET_COHORT: `cohort_id` (from list results)\n- For UPDATE_COHORT_MEMBERSHIP:\n  - `cohort_id`: Target cohort ID\n  - `memberships`: Object with `add` and\u002For `remove` arrays of user IDs\n- For CHECK_COHORT_STATUS: `request_id` from update response\n\n**Pitfalls**:\n- Cohort IDs are required for all cohort-specific operations\n- UPDATE_COHORT_MEMBERSHIP is asynchronous; use CHECK_COHORT_STATUS to verify\n- `request_id` from the update response is needed for status checking\n- Maximum membership changes per request may be limited; chunk large updates\n- Only behavioral cohorts support API membership updates\n\n### 5. Browse Event Categories\n\n**When to use**: User wants to discover available event types and categories in Amplitude\n\n**Tool sequence**:\n1. `AMPLITUDE_GET_EVENT_CATEGORIES` - List all event categories [Required]\n\n**Key parameters**:\n- No required parameters; returns all configured event categories\n\n**Pitfalls**:\n- Categories are configured in Amplitude UI; API provides read access\n- Event names within categories are case-sensitive\n- Use these categories to validate event_type values before sending events\n\n## Common Patterns\n\n### ID Resolution\n\n**Application user_id -> Amplitude internal ID**:\n```\n1. Call AMPLITUDE_FIND_USER with user=your_user_id\n2. Extract Amplitude's internal user ID from response\n3. Use internal ID for GET_USER_ACTIVITY\n```\n\n**Cohort name -> Cohort ID**:\n```\n1. Call AMPLITUDE_LIST_COHORTS\n2. Find cohort by name in results\n3. Extract id for cohort operations\n```\n\n### User Property Operations\n\nAmplitude IDENTIFY supports these property operations:\n- `$set`: Set property value (overwrites existing)\n- `$setOnce`: Set only if property not already set\n- `$add`: Increment numeric property\n- `$append`: Append to list property\n- `$unset`: Remove property entirely\n\nExample structure:\n```json\n{\n  \"user_properties\": {\n    \"$set\": {\"plan\": \"premium\", \"company\": \"Acme\"},\n    \"$add\": {\"login_count\": 1}\n  }\n}\n```\n\n### Async Operation Pattern\n\nFor cohort membership updates:\n```\n1. Call AMPLITUDE_UPDATE_COHORT_MEMBERSHIP -> get request_id\n2. Call AMPLITUDE_CHECK_COHORT_STATUS with request_id\n3. Repeat step 2 until status is 'complete' or 'error'\n```\n\n## Known Pitfalls\n\n**User IDs**:\n- Amplitude has its own internal user IDs separate from your application's\n- FIND_USER resolves your IDs to Amplitude's internal IDs\n- GET_USER_ACTIVITY requires Amplitude's internal ID, not your user_id\n\n**Event Timestamps**:\n- Must be in milliseconds since epoch (13 digits)\n- Seconds (10 digits) will be interpreted as very old dates\n- Omitting timestamp uses server receive time\n\n**Rate Limits**:\n- Event ingestion has throughput limits per project\n- Batch events where possible to reduce API calls\n- Cohort membership updates have async processing limits\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- User activity returns events in reverse chronological order\n- Cohort lists may include archived cohorts; check status field\n- Parse defensively with fallbacks for optional fields\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Send events | AMPLITUDE_SEND_EVENTS | events (array) |\n| Find user | AMPLITUDE_FIND_USER | user |\n| Get user activity | AMPLITUDE_GET_USER_ACTIVITY | user, offset, limit |\n| Identify user | AMPLITUDE_IDENTIFY | user_id, user_properties |\n| List cohorts | AMPLITUDE_LIST_COHORTS | (none) |\n| Get cohort | AMPLITUDE_GET_COHORT | cohort_id |\n| Update cohort members | AMPLITUDE_UPDATE_COHORT_MEMBERSHIP | cohort_id, memberships |\n| Check cohort status | AMPLITUDE_CHECK_COHORT_STATUS | request_id |\n| List event categories | AMPLITUDE_GET_EVENT_CATEGORIES | (none) |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":36,"source":41,"requires":47,"description":7},{"mcp":48},[49],"rube","release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Famplitude-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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add javiertarazon\u002Fide-agente-free-jt7- --skill amplitude-automation",{"tool":62,"command":63},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill amplitude-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill amplitude-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Famplitude-automation\u002FSKILL.md",true,[],[71,99,115,134,148,170],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":80,"publishedAt":42},"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",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[81,82,83,41,84,85,86,87,88,36,89,90,91,92,93,94,95,96,97,98],"zustand","store","zustand store ts","middleware","implementing","use","react state management","when","react","with","state","create","state management","typescript","action","management","separation","global",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"publishedAt":42},"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",[105],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[107,108,23,41,109,40,39,110,37,36,34,33,111,32,112,113,30,114,96,29],"zoom automation","zoom","creation","schemas","meeting","tracking","webinars","recordings",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":42},"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",[121],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[123,124,23,125,126,127,41,128,129,40,130,39,110,131,37,36,132,35,133,92],"crm automation","zoho crm automation","crm","zoho crm","zoho","leads","manage leads","manage","records","convert","contacts",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":42},"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",[140],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[142,23,143,41,40,39,110,37,144,36,35,145,146,34,33,147,32,30,29,26],"zendesk automation","zendesk","organizations","replies","users","tickets",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":42},"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",[],[155,156,157,158,159,160,161,162,163,23,164,36,165,166,167,168,169,26],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":42},"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",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[180,181,182,183,41,184,185,186,187,188,189,190,165,191,192,193,194,195,196,197],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]