[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SSH99M5EP93X7S4T95QS2":3,"skill-same:01M71SSH99M5EP93X7S4T95QS2":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},"01M71SSH99M5EP93X7S4T95QS2","mixpanel-automation",null,"Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. 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\u002Fmixpanel-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],"mixpanel automation","mixpanel","automation","events","Tools","composio","search tools","via","first","jql","queries","tasks","unknown","MCP","profiles","schemas","search","for","segmentation","community","2026-11-10 13:02:02",false,"---\nname: mixpanel-automation\ndescription: \"Automate Mixpanel tasks via Rube MCP (Composio): events, segmentation, funnels, cohorts, user profiles, JQL queries. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Mixpanel Automation via Rube MCP\n\nAutomate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`\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 `mixpanel`\n3. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Aggregate Event Data\n\n**When to use**: User wants to count events, get totals, or track event trends over time\n\n**Tool sequence**:\n1. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]\n2. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]\n\n**Key parameters**:\n- `event`: Event name or array of event names to aggregate\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')\n- `type`: Aggregation type ('general', 'unique', 'average')\n- `where`: Filter expression for event properties\n\n**Pitfalls**:\n- Date format must be 'YYYY-MM-DD'; other formats cause errors\n- Event names are case-sensitive; use exact names from your Mixpanel project\n- `where` filter uses Mixpanel expression syntax (e.g., `properties[\"country\"] == \"US\"`)\n- Maximum date range may be limited depending on your Mixpanel plan\n\n### 2. Run Segmentation Queries\n\n**When to use**: User wants to break down events by properties for detailed analysis\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]\n\n**Key parameters**:\n- `event`: Event name to segment\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `on`: Property to segment by (e.g., `properties[\"country\"]`)\n- `unit`: Time granularity\n- `type`: Count type ('general', 'unique', 'average')\n- `where`: Filter expression\n- `limit`: Maximum number of segments to return\n\n**Pitfalls**:\n- The `on` parameter uses Mixpanel property expression syntax\n- Property references must use `properties[\"prop_name\"]` format\n- Segmentation on high-cardinality properties returns capped results; use `limit`\n- Results are grouped by the segmentation property and time unit\n\n### 3. Analyze Funnels\n\n**When to use**: User wants to track conversion funnels and identify drop-off points\n\n**Tool sequence**:\n1. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]\n2. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]\n\n**Key parameters**:\n- `funnel_id`: ID of the saved funnel to query\n- `from_date` \u002F `to_date`: Date range\n- `unit`: Time granularity\n- `where`: Filter expression\n- `on`: Property to segment funnel by\n- `length`: Conversion window in days\n\n**Pitfalls**:\n- `funnel_id` is required; resolve via LIST_FUNNELS first\n- Funnels must be created in Mixpanel UI first; API only queries existing funnels\n- Conversion window (`length`) defaults vary; set explicitly for accuracy\n- Large date ranges with segmentation can produce very large responses\n\n### 4. Manage User Profiles\n\n**When to use**: User wants to query or update user profiles in Mixpanel\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]\n2. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]\n\n**Key parameters**:\n- `where`: Filter expression for profile properties (e.g., `properties[\"plan\"] == \"premium\"`)\n- `output_properties`: Array of property names to include in results\n- `page`: Page number for pagination\n- `session_id`: Session ID for consistent pagination (from first response)\n- For batch update: array of profile updates with `$distinct_id` and property operations\n\n**Pitfalls**:\n- Profile queries return paginated results; use `session_id` from first response for consistent paging\n- `where` uses Mixpanel expression syntax for profile properties\n- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles\n- Batch update has a maximum number of profiles per request; chunk larger updates\n- Profile property names are case-sensitive\n\n### 5. Manage Cohorts\n\n**When to use**: User wants to list or analyze user cohorts\n\n**Tool sequence**:\n1. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]\n\n**Key parameters**:\n- No required parameters; returns all accessible cohorts\n- Response includes cohort `id`, `name`, `description`, `count`\n\n**Pitfalls**:\n- Cohorts are created and managed in Mixpanel UI; API provides read access\n- Cohort IDs are numeric; use exact ID from list results\n- Cohort counts may be approximate for very large cohorts\n- Cohorts can be used as filters in other queries via `where` expressions\n\n### 6. Run JQL and Insight Queries\n\n**When to use**: User wants to run custom JQL queries or insight analyses\n\n**Tool sequence**:\n1. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]\n2. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]\n\n**Key parameters**:\n- For JQL: `script` containing the JQL JavaScript code\n- For Insight: `bookmark_id` of the saved insight\n- `project_id`: Project context for the query\n\n**Pitfalls**:\n- JQL uses JavaScript-like syntax specific to Mixpanel\n- JQL queries have execution time limits; optimize for efficiency\n- Insight `bookmark_id` must reference an existing saved insight\n- JQL is a legacy feature; check Mixpanel documentation for current availability\n\n## Common Patterns\n\n### ID Resolution\n\n**Project name -> Project ID**:\n```\n1. Call MIXPANEL_GET_ALL_PROJECTS\n2. Find project by name in results\n3. Extract project id\n```\n\n**Funnel name -> Funnel ID**:\n```\n1. Call MIXPANEL_LIST_FUNNELS\n2. Find funnel by name\n3. Extract funnel_id\n```\n\n### Mixpanel Expression Syntax\n\nUsed in `where` and `on` parameters:\n- Property reference: `properties[\"property_name\"]`\n- Equality: `properties[\"country\"] == \"US\"`\n- Comparison: `properties[\"age\"] > 25`\n- Boolean: `properties[\"is_premium\"] == true`\n- Contains: `\"search_term\" in properties[\"name\"]`\n- AND\u002FOR: `properties[\"country\"] == \"US\" and properties[\"plan\"] == \"pro\"`\n\n### Pagination\n\n- Event queries: Follow date-based pagination by adjusting date ranges\n- Profile queries: Use `page` number and `session_id` for consistent results\n- Funnel\u002Fcohort lists: Typically return complete results without pagination\n\n## Known Pitfalls\n\n**Date Formats**:\n- Always use 'YYYY-MM-DD' format\n- Date ranges are inclusive on both ends\n- Data freshness depends on Mixpanel ingestion delay (typically minutes)\n\n**Expression Syntax**:\n- Property references always use `properties[\"name\"]` format\n- String values must be quoted: `properties[\"status\"] == \"active\"`\n- Numeric values are unquoted: `properties[\"count\"] > 10`\n- Boolean values: `true` \u002F `false` (lowercase)\n\n**Rate Limits**:\n- Mixpanel API has rate limits per project\n- Large segmentation queries may time out; reduce date range or segments\n- Use batch operations where available to minimize API calls\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Event data is typically grouped by date and segment\n- Numeric values may be returned as strings; parse explicitly\n- Empty date ranges return empty objects, not empty arrays\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |\n| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |\n| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |\n| List funnels | MIXPANEL_LIST_FUNNELS | (none) |\n| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |\n| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |\n| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |\n| List cohorts | MIXPANEL_COHORTS_LIST | (none) |\n| JQL query | MIXPANEL_JQL_QUERY | script |\n| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Mixpanel Automation via Rube MCP\n\nAutomate Mixpanel product analytics through Composio's Mixpanel toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Mixpanel connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `mixpanel`\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 `mixpanel`\n3. If connection is not ACTIVE, follow the returned auth link to complete Mixpanel authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Aggregate Event Data\n\n**When to use**: User wants to count events, get totals, or track event trends over time\n\n**Tool sequence**:\n1. `MIXPANEL_GET_ALL_PROJECTS` - List projects to get project ID [Prerequisite]\n2. `MIXPANEL_AGGREGATE_EVENT_COUNTS` - Get event counts and aggregations [Required]\n\n**Key parameters**:\n- `event`: Event name or array of event names to aggregate\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `unit`: Time granularity ('minute', 'hour', 'day', 'week', 'month')\n- `type`: Aggregation type ('general', 'unique', 'average')\n- `where`: Filter expression for event properties\n\n**Pitfalls**:\n- Date format must be 'YYYY-MM-DD'; other formats cause errors\n- Event names are case-sensitive; use exact names from your Mixpanel project\n- `where` filter uses Mixpanel expression syntax (e.g., `properties[\"country\"] == \"US\"`)\n- Maximum date range may be limited depending on your Mixpanel plan\n\n### 2. Run Segmentation Queries\n\n**When to use**: User wants to break down events by properties for detailed analysis\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_SEGMENTATION` - Run segmentation analysis [Required]\n\n**Key parameters**:\n- `event`: Event name to segment\n- `from_date` \u002F `to_date`: Date range in 'YYYY-MM-DD' format\n- `on`: Property to segment by (e.g., `properties[\"country\"]`)\n- `unit`: Time granularity\n- `type`: Count type ('general', 'unique', 'average')\n- `where`: Filter expression\n- `limit`: Maximum number of segments to return\n\n**Pitfalls**:\n- The `on` parameter uses Mixpanel property expression syntax\n- Property references must use `properties[\"prop_name\"]` format\n- Segmentation on high-cardinality properties returns capped results; use `limit`\n- Results are grouped by the segmentation property and time unit\n\n### 3. Analyze Funnels\n\n**When to use**: User wants to track conversion funnels and identify drop-off points\n\n**Tool sequence**:\n1. `MIXPANEL_LIST_FUNNELS` - List saved funnels to find funnel ID [Prerequisite]\n2. `MIXPANEL_QUERY_FUNNEL` - Execute funnel analysis [Required]\n\n**Key parameters**:\n- `funnel_id`: ID of the saved funnel to query\n- `from_date` \u002F `to_date`: Date range\n- `unit`: Time granularity\n- `where`: Filter expression\n- `on`: Property to segment funnel by\n- `length`: Conversion window in days\n\n**Pitfalls**:\n- `funnel_id` is required; resolve via LIST_FUNNELS first\n- Funnels must be created in Mixpanel UI first; API only queries existing funnels\n- Conversion window (`length`) defaults vary; set explicitly for accuracy\n- Large date ranges with segmentation can produce very large responses\n\n### 4. Manage User Profiles\n\n**When to use**: User wants to query or update user profiles in Mixpanel\n\n**Tool sequence**:\n1. `MIXPANEL_QUERY_PROFILES` - Search and filter user profiles [Required]\n2. `MIXPANEL_PROFILE_BATCH_UPDATE` - Update multiple user profiles [Optional]\n\n**Key parameters**:\n- `where`: Filter expression for profile properties (e.g., `properties[\"plan\"] == \"premium\"`)\n- `output_properties`: Array of property names to include in results\n- `page`: Page number for pagination\n- `session_id`: Session ID for consistent pagination (from first response)\n- For batch update: array of profile updates with `$distinct_id` and property operations\n\n**Pitfalls**:\n- Profile queries return paginated results; use `session_id` from first response for consistent paging\n- `where` uses Mixpanel expression syntax for profile properties\n- BATCH_UPDATE applies operations (`$set`, `$unset`, `$add`, `$append`) to profiles\n- Batch update has a maximum number of profiles per request; chunk larger updates\n- Profile property names are case-sensitive\n\n### 5. Manage Cohorts\n\n**When to use**: User wants to list or analyze user cohorts\n\n**Tool sequence**:\n1. `MIXPANEL_COHORTS_LIST` - List all saved cohorts [Required]\n\n**Key parameters**:\n- No required parameters; returns all accessible cohorts\n- Response includes cohort `id`, `name`, `description`, `count`\n\n**Pitfalls**:\n- Cohorts are created and managed in Mixpanel UI; API provides read access\n- Cohort IDs are numeric; use exact ID from list results\n- Cohort counts may be approximate for very large cohorts\n- Cohorts can be used as filters in other queries via `where` expressions\n\n### 6. Run JQL and Insight Queries\n\n**When to use**: User wants to run custom JQL queries or insight analyses\n\n**Tool sequence**:\n1. `MIXPANEL_JQL_QUERY` - Execute a custom JQL (JavaScript Query Language) query [Optional]\n2. `MIXPANEL_QUERY_INSIGHT` - Run a saved insight query [Optional]\n\n**Key parameters**:\n- For JQL: `script` containing the JQL JavaScript code\n- For Insight: `bookmark_id` of the saved insight\n- `project_id`: Project context for the query\n\n**Pitfalls**:\n- JQL uses JavaScript-like syntax specific to Mixpanel\n- JQL queries have execution time limits; optimize for efficiency\n- Insight `bookmark_id` must reference an existing saved insight\n- JQL is a legacy feature; check Mixpanel documentation for current availability\n\n## Common Patterns\n\n### ID Resolution\n\n**Project name -> Project ID**:\n```\n1. Call MIXPANEL_GET_ALL_PROJECTS\n2. Find project by name in results\n3. Extract project id\n```\n\n**Funnel name -> Funnel ID**:\n```\n1. Call MIXPANEL_LIST_FUNNELS\n2. Find funnel by name\n3. Extract funnel_id\n```\n\n### Mixpanel Expression Syntax\n\nUsed in `where` and `on` parameters:\n- Property reference: `properties[\"property_name\"]`\n- Equality: `properties[\"country\"] == \"US\"`\n- Comparison: `properties[\"age\"] > 25`\n- Boolean: `properties[\"is_premium\"] == true`\n- Contains: `\"search_term\" in properties[\"name\"]`\n- AND\u002FOR: `properties[\"country\"] == \"US\" and properties[\"plan\"] == \"pro\"`\n\n### Pagination\n\n- Event queries: Follow date-based pagination by adjusting date ranges\n- Profile queries: Use `page` number and `session_id` for consistent results\n- Funnel\u002Fcohort lists: Typically return complete results without pagination\n\n## Known Pitfalls\n\n**Date Formats**:\n- Always use 'YYYY-MM-DD' format\n- Date ranges are inclusive on both ends\n- Data freshness depends on Mixpanel ingestion delay (typically minutes)\n\n**Expression Syntax**:\n- Property references always use `properties[\"name\"]` format\n- String values must be quoted: `properties[\"status\"] == \"active\"`\n- Numeric values are unquoted: `properties[\"count\"] > 10`\n- Boolean values: `true` \u002F `false` (lowercase)\n\n**Rate Limits**:\n- Mixpanel API has rate limits per project\n- Large segmentation queries may time out; reduce date range or segments\n- Use batch operations where available to minimize API calls\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Event data is typically grouped by date and segment\n- Numeric values may be returned as strings; parse explicitly\n- Empty date ranges return empty objects, not empty arrays\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | MIXPANEL_GET_ALL_PROJECTS | (none) |\n| Aggregate events | MIXPANEL_AGGREGATE_EVENT_COUNTS | event, from_date, to_date, unit |\n| Segmentation | MIXPANEL_QUERY_SEGMENTATION | event, on, from_date, to_date |\n| List funnels | MIXPANEL_LIST_FUNNELS | (none) |\n| Query funnel | MIXPANEL_QUERY_FUNNEL | funnel_id, from_date, to_date |\n| Query profiles | MIXPANEL_QUERY_PROFILES | where, output_properties, page |\n| Batch update profiles | MIXPANEL_PROFILE_BATCH_UPDATE | (profile update objects) |\n| List cohorts | MIXPANEL_COHORTS_LIST | (none) |\n| JQL query | MIXPANEL_JQL_QUERY | script |\n| Query insight | MIXPANEL_QUERY_INSIGHT | bookmark_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":35,"source":42,"requires":48,"description":7},{"mcp":49},[50],"rube","release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Fmixpanel-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 mixpanel-automation",{"tool":63,"command":64},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill mixpanel-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill mixpanel-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fmixpanel-automation\u002FSKILL.md",true,[],[72,100,115,134,149,171],{"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,35,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,25,42,110,40,39,38,36,35,31,30,111,29,112,113,28,114,97,27],"zoom automation","zoom","creation","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":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",[121],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[123,124,25,125,126,127,42,128,129,40,130,39,38,131,36,35,132,34,133,93],"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":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",[140],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[142,25,143,42,40,39,38,36,144,35,34,145,146,31,30,147,29,28,27,148],"zendesk automation","zendesk","organizations","replies","users","tickets","automate",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"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",[],[156,157,158,159,160,161,162,163,164,25,165,35,166,167,168,169,170,148],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":180,"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",[177],{"categoryNo":178,"categoryName":179,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[181,182,183,184,42,185,186,187,188,189,190,191,166,192,193,194,195,196,197,198],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]