[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71S2TMFNTW0XXXQCNW0E43C":3,"skill-same:01M71S2TMFNTW0XXXQCNW0E43C":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},"01M71S2TMFNTW0XXXQCNW0E43C","datadog-automation",null,"Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors\u002Fdashboards, create events and downtimes. 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\u002Fdatadog-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],"datadog automation","datadog","automation","events","Tools","composio","search tools","query metrics","via","first","create","logs","tasks","query","unknown","MCP","search","manage","for","community","2026-11-10 13:02:02",false,"---\nname: datadog-automation\ndescription: \"Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors\u002Fdashboards, create events and downtimes. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Datadog Automation via Rube MCP\n\nAutomate Datadog monitoring and observability operations through Composio's Datadog toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Datadog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog`\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 `datadog`\n3. If connection is not ACTIVE, follow the returned auth link to complete Datadog authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Query and Explore Metrics\n\n**When to use**: User wants to query metric data or list available metrics\n\n**Tool sequence**:\n1. `DATADOG_LIST_METRICS` - List available metric names [Optional]\n2. `DATADOG_QUERY_METRICS` - Query metric time series data [Required]\n\n**Key parameters**:\n- `query`: Datadog metric query string (e.g., `avg:system.cpu.user{host:web01}`)\n- `from`: Start timestamp (Unix epoch seconds)\n- `to`: End timestamp (Unix epoch seconds)\n- `q`: Search string for listing metrics\n\n**Pitfalls**:\n- Query syntax follows Datadog's metric query format: `aggregation:metric_name{tag_filters}`\n- `from` and `to` are Unix epoch timestamps in seconds, not milliseconds\n- Valid aggregations: `avg`, `sum`, `min`, `max`, `count`\n- Tag filters use curly braces: `{host:web01,env:prod}`\n- Time range should not exceed Datadog's retention limits for the metric type\n\n### 2. Search and Analyze Logs\n\n**When to use**: User wants to search log entries or list log indexes\n\n**Tool sequence**:\n1. `DATADOG_LIST_LOG_INDEXES` - List available log indexes [Optional]\n2. `DATADOG_SEARCH_LOGS` - Search logs with query and filters [Required]\n\n**Key parameters**:\n- `query`: Log search query using Datadog log query syntax\n- `from`: Start time (ISO 8601 or Unix timestamp)\n- `to`: End time (ISO 8601 or Unix timestamp)\n- `sort`: Sort order ('asc' or 'desc')\n- `limit`: Number of log entries to return\n\n**Pitfalls**:\n- Log queries use Datadog's log search syntax: `service:web status:error`\n- Search is limited to retained logs within the configured retention period\n- Large result sets require pagination; check for cursor\u002Fpage tokens\n- Log indexes control routing and retention; filter by index if known\n\n### 3. Manage Monitors\n\n**When to use**: User wants to create, update, mute, or inspect monitors\n\n**Tool sequence**:\n1. `DATADOG_LIST_MONITORS` - List all monitors with filters [Required]\n2. `DATADOG_GET_MONITOR` - Get specific monitor details [Optional]\n3. `DATADOG_CREATE_MONITOR` - Create a new monitor [Optional]\n4. `DATADOG_UPDATE_MONITOR` - Update monitor configuration [Optional]\n5. `DATADOG_MUTE_MONITOR` - Silence a monitor temporarily [Optional]\n6. `DATADOG_UNMUTE_MONITOR` - Re-enable a muted monitor [Optional]\n\n**Key parameters**:\n- `monitor_id`: Numeric monitor ID\n- `name`: Monitor display name\n- `type`: Monitor type ('metric alert', 'service check', 'log alert', 'query alert', etc.)\n- `query`: Monitor query defining the alert condition\n- `message`: Notification message with @mentions\n- `tags`: Array of tag strings\n- `thresholds`: Alert threshold values (`critical`, `warning`, `ok`)\n\n**Pitfalls**:\n- Monitor `type` must match the query type; mismatches cause creation failures\n- `message` supports @mentions for notifications (e.g., `@slack-channel`, `@pagerduty`)\n- Thresholds vary by monitor type; metric monitors need `critical` at minimum\n- Muting a monitor suppresses notifications but the monitor still evaluates\n- Monitor IDs are numeric integers\n\n### 4. Manage Dashboards\n\n**When to use**: User wants to list, view, update, or delete dashboards\n\n**Tool sequence**:\n1. `DATADOG_LIST_DASHBOARDS` - List all dashboards [Required]\n2. `DATADOG_GET_DASHBOARD` - Get full dashboard definition [Optional]\n3. `DATADOG_UPDATE_DASHBOARD` - Update dashboard layout or widgets [Optional]\n4. `DATADOG_DELETE_DASHBOARD` - Remove a dashboard (irreversible) [Optional]\n\n**Key parameters**:\n- `dashboard_id`: Dashboard identifier string\n- `title`: Dashboard title\n- `layout_type`: 'ordered' (grid) or 'free' (freeform positioning)\n- `widgets`: Array of widget definition objects\n- `description`: Dashboard description\n\n**Pitfalls**:\n- Dashboard IDs are alphanumeric strings (e.g., 'abc-def-ghi'), not numeric\n- `layout_type` cannot be changed after creation; must recreate the dashboard\n- Widget definitions are complex nested objects; get existing dashboard first to understand structure\n- DELETE is permanent; there is no undo\n\n### 5. Create Events and Manage Downtimes\n\n**When to use**: User wants to post events or schedule maintenance downtimes\n\n**Tool sequence**:\n1. `DATADOG_LIST_EVENTS` - List existing events [Optional]\n2. `DATADOG_CREATE_EVENT` - Post a new event [Required]\n3. `DATADOG_CREATE_DOWNTIME` - Schedule a maintenance downtime [Optional]\n\n**Key parameters for events**:\n- `title`: Event title\n- `text`: Event body text (supports markdown)\n- `alert_type`: Event severity ('error', 'warning', 'info', 'success')\n- `tags`: Array of tag strings\n\n**Key parameters for downtimes**:\n- `scope`: Tag scope for the downtime (e.g., `host:web01`)\n- `start`: Start time (Unix epoch)\n- `end`: End time (Unix epoch; omit for indefinite)\n- `message`: Downtime description\n- `monitor_id`: Specific monitor to downtime (optional, omit for scope-based)\n\n**Pitfalls**:\n- Event `text` supports Datadog's markdown format including @mentions\n- Downtimes scope uses tag syntax: `host:web01`, `env:staging`\n- Omitting `end` creates an indefinite downtime; always set an end time for maintenance\n- Downtime `monitor_id` narrows to a single monitor; scope applies to all matching monitors\n\n### 6. Manage Hosts and Traces\n\n**When to use**: User wants to list infrastructure hosts or inspect distributed traces\n\n**Tool sequence**:\n1. `DATADOG_LIST_HOSTS` - List all reporting hosts [Required]\n2. `DATADOG_GET_TRACE_BY_ID` - Get a specific distributed trace [Optional]\n\n**Key parameters**:\n- `filter`: Host search filter string\n- `sort_field`: Sort hosts by field (e.g., 'name', 'apps', 'cpu')\n- `sort_dir`: Sort direction ('asc' or 'desc')\n- `trace_id`: Distributed trace ID for trace lookup\n\n**Pitfalls**:\n- Host list includes all hosts reporting to Datadog within the retention window\n- Trace IDs are long numeric strings; ensure exact match\n- Hosts that stop reporting are retained for a configured period before removal\n\n## Common Patterns\n\n### Monitor Query Syntax\n\n**Metric alerts**:\n```\navg(last_5m):avg:system.cpu.user{env:prod} > 90\n```\n\n**Log alerts**:\n```\nlogs(\"service:web status:error\").index(\"main\").rollup(\"count\").last(\"5m\") > 10\n```\n\n### Tag Filtering\n\n- Tags use `key:value` format: `host:web01`, `env:prod`, `service:api`\n- Multiple tags: `{host:web01,env:prod}` (AND logic)\n- Wildcard: `host:web*`\n\n### Pagination\n\n- Use `page` and `page_size` or offset-based pagination depending on endpoint\n- Check response for total count to determine if more pages exist\n- Continue until all results are retrieved\n\n## Known Pitfalls\n\n**Timestamps**:\n- Most endpoints use Unix epoch seconds (not milliseconds)\n- Some endpoints accept ISO 8601; check tool schema\n- Time ranges should be reasonable (not years of data)\n\n**Query Syntax**:\n- Metric queries: `aggregation:metric{tags}`\n- Log queries: `field:value` pairs\n- Monitor queries vary by type; check Datadog documentation\n\n**Rate Limits**:\n- Datadog API has per-endpoint rate limits\n- Implement backoff on 429 responses\n- Batch operations where possible\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Query metrics | DATADOG_QUERY_METRICS | query, from, to |\n| List metrics | DATADOG_LIST_METRICS | q |\n| Search logs | DATADOG_SEARCH_LOGS | query, from, to, limit |\n| List log indexes | DATADOG_LIST_LOG_INDEXES | (none) |\n| List monitors | DATADOG_LIST_MONITORS | tags |\n| Get monitor | DATADOG_GET_MONITOR | monitor_id |\n| Create monitor | DATADOG_CREATE_MONITOR | name, type, query, message |\n| Update monitor | DATADOG_UPDATE_MONITOR | monitor_id |\n| Mute monitor | DATADOG_MUTE_MONITOR | monitor_id |\n| Unmute monitor | DATADOG_UNMUTE_MONITOR | monitor_id |\n| List dashboards | DATADOG_LIST_DASHBOARDS | (none) |\n| Get dashboard | DATADOG_GET_DASHBOARD | dashboard_id |\n| Update dashboard | DATADOG_UPDATE_DASHBOARD | dashboard_id, title, widgets |\n| Delete dashboard | DATADOG_DELETE_DASHBOARD | dashboard_id |\n| List events | DATADOG_LIST_EVENTS | start, end |\n| Create event | DATADOG_CREATE_EVENT | title, text, alert_type |\n| Create downtime | DATADOG_CREATE_DOWNTIME | scope, start, end |\n| List hosts | DATADOG_LIST_HOSTS | filter, sort_field |\n| Get trace | DATADOG_GET_TRACE_BY_ID | trace_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Datadog Automation via Rube MCP\n\nAutomate Datadog monitoring and observability operations through Composio's Datadog toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Datadog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog`\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 `datadog`\n3. If connection is not ACTIVE, follow the returned auth link to complete Datadog authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Query and Explore Metrics\n\n**When to use**: User wants to query metric data or list available metrics\n\n**Tool sequence**:\n1. `DATADOG_LIST_METRICS` - List available metric names [Optional]\n2. `DATADOG_QUERY_METRICS` - Query metric time series data [Required]\n\n**Key parameters**:\n- `query`: Datadog metric query string (e.g., `avg:system.cpu.user{host:web01}`)\n- `from`: Start timestamp (Unix epoch seconds)\n- `to`: End timestamp (Unix epoch seconds)\n- `q`: Search string for listing metrics\n\n**Pitfalls**:\n- Query syntax follows Datadog's metric query format: `aggregation:metric_name{tag_filters}`\n- `from` and `to` are Unix epoch timestamps in seconds, not milliseconds\n- Valid aggregations: `avg`, `sum`, `min`, `max`, `count`\n- Tag filters use curly braces: `{host:web01,env:prod}`\n- Time range should not exceed Datadog's retention limits for the metric type\n\n### 2. Search and Analyze Logs\n\n**When to use**: User wants to search log entries or list log indexes\n\n**Tool sequence**:\n1. `DATADOG_LIST_LOG_INDEXES` - List available log indexes [Optional]\n2. `DATADOG_SEARCH_LOGS` - Search logs with query and filters [Required]\n\n**Key parameters**:\n- `query`: Log search query using Datadog log query syntax\n- `from`: Start time (ISO 8601 or Unix timestamp)\n- `to`: End time (ISO 8601 or Unix timestamp)\n- `sort`: Sort order ('asc' or 'desc')\n- `limit`: Number of log entries to return\n\n**Pitfalls**:\n- Log queries use Datadog's log search syntax: `service:web status:error`\n- Search is limited to retained logs within the configured retention period\n- Large result sets require pagination; check for cursor\u002Fpage tokens\n- Log indexes control routing and retention; filter by index if known\n\n### 3. Manage Monitors\n\n**When to use**: User wants to create, update, mute, or inspect monitors\n\n**Tool sequence**:\n1. `DATADOG_LIST_MONITORS` - List all monitors with filters [Required]\n2. `DATADOG_GET_MONITOR` - Get specific monitor details [Optional]\n3. `DATADOG_CREATE_MONITOR` - Create a new monitor [Optional]\n4. `DATADOG_UPDATE_MONITOR` - Update monitor configuration [Optional]\n5. `DATADOG_MUTE_MONITOR` - Silence a monitor temporarily [Optional]\n6. `DATADOG_UNMUTE_MONITOR` - Re-enable a muted monitor [Optional]\n\n**Key parameters**:\n- `monitor_id`: Numeric monitor ID\n- `name`: Monitor display name\n- `type`: Monitor type ('metric alert', 'service check', 'log alert', 'query alert', etc.)\n- `query`: Monitor query defining the alert condition\n- `message`: Notification message with @mentions\n- `tags`: Array of tag strings\n- `thresholds`: Alert threshold values (`critical`, `warning`, `ok`)\n\n**Pitfalls**:\n- Monitor `type` must match the query type; mismatches cause creation failures\n- `message` supports @mentions for notifications (e.g., `@slack-channel`, `@pagerduty`)\n- Thresholds vary by monitor type; metric monitors need `critical` at minimum\n- Muting a monitor suppresses notifications but the monitor still evaluates\n- Monitor IDs are numeric integers\n\n### 4. Manage Dashboards\n\n**When to use**: User wants to list, view, update, or delete dashboards\n\n**Tool sequence**:\n1. `DATADOG_LIST_DASHBOARDS` - List all dashboards [Required]\n2. `DATADOG_GET_DASHBOARD` - Get full dashboard definition [Optional]\n3. `DATADOG_UPDATE_DASHBOARD` - Update dashboard layout or widgets [Optional]\n4. `DATADOG_DELETE_DASHBOARD` - Remove a dashboard (irreversible) [Optional]\n\n**Key parameters**:\n- `dashboard_id`: Dashboard identifier string\n- `title`: Dashboard title\n- `layout_type`: 'ordered' (grid) or 'free' (freeform positioning)\n- `widgets`: Array of widget definition objects\n- `description`: Dashboard description\n\n**Pitfalls**:\n- Dashboard IDs are alphanumeric strings (e.g., 'abc-def-ghi'), not numeric\n- `layout_type` cannot be changed after creation; must recreate the dashboard\n- Widget definitions are complex nested objects; get existing dashboard first to understand structure\n- DELETE is permanent; there is no undo\n\n### 5. Create Events and Manage Downtimes\n\n**When to use**: User wants to post events or schedule maintenance downtimes\n\n**Tool sequence**:\n1. `DATADOG_LIST_EVENTS` - List existing events [Optional]\n2. `DATADOG_CREATE_EVENT` - Post a new event [Required]\n3. `DATADOG_CREATE_DOWNTIME` - Schedule a maintenance downtime [Optional]\n\n**Key parameters for events**:\n- `title`: Event title\n- `text`: Event body text (supports markdown)\n- `alert_type`: Event severity ('error', 'warning', 'info', 'success')\n- `tags`: Array of tag strings\n\n**Key parameters for downtimes**:\n- `scope`: Tag scope for the downtime (e.g., `host:web01`)\n- `start`: Start time (Unix epoch)\n- `end`: End time (Unix epoch; omit for indefinite)\n- `message`: Downtime description\n- `monitor_id`: Specific monitor to downtime (optional, omit for scope-based)\n\n**Pitfalls**:\n- Event `text` supports Datadog's markdown format including @mentions\n- Downtimes scope uses tag syntax: `host:web01`, `env:staging`\n- Omitting `end` creates an indefinite downtime; always set an end time for maintenance\n- Downtime `monitor_id` narrows to a single monitor; scope applies to all matching monitors\n\n### 6. Manage Hosts and Traces\n\n**When to use**: User wants to list infrastructure hosts or inspect distributed traces\n\n**Tool sequence**:\n1. `DATADOG_LIST_HOSTS` - List all reporting hosts [Required]\n2. `DATADOG_GET_TRACE_BY_ID` - Get a specific distributed trace [Optional]\n\n**Key parameters**:\n- `filter`: Host search filter string\n- `sort_field`: Sort hosts by field (e.g., 'name', 'apps', 'cpu')\n- `sort_dir`: Sort direction ('asc' or 'desc')\n- `trace_id`: Distributed trace ID for trace lookup\n\n**Pitfalls**:\n- Host list includes all hosts reporting to Datadog within the retention window\n- Trace IDs are long numeric strings; ensure exact match\n- Hosts that stop reporting are retained for a configured period before removal\n\n## Common Patterns\n\n### Monitor Query Syntax\n\n**Metric alerts**:\n```\navg(last_5m):avg:system.cpu.user{env:prod} > 90\n```\n\n**Log alerts**:\n```\nlogs(\"service:web status:error\").index(\"main\").rollup(\"count\").last(\"5m\") > 10\n```\n\n### Tag Filtering\n\n- Tags use `key:value` format: `host:web01`, `env:prod`, `service:api`\n- Multiple tags: `{host:web01,env:prod}` (AND logic)\n- Wildcard: `host:web*`\n\n### Pagination\n\n- Use `page` and `page_size` or offset-based pagination depending on endpoint\n- Check response for total count to determine if more pages exist\n- Continue until all results are retrieved\n\n## Known Pitfalls\n\n**Timestamps**:\n- Most endpoints use Unix epoch seconds (not milliseconds)\n- Some endpoints accept ISO 8601; check tool schema\n- Time ranges should be reasonable (not years of data)\n\n**Query Syntax**:\n- Metric queries: `aggregation:metric{tags}`\n- Log queries: `field:value` pairs\n- Monitor queries vary by type; check Datadog documentation\n\n**Rate Limits**:\n- Datadog API has per-endpoint rate limits\n- Implement backoff on 429 responses\n- Batch operations where possible\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Query metrics | DATADOG_QUERY_METRICS | query, from, to |\n| List metrics | DATADOG_LIST_METRICS | q |\n| Search logs | DATADOG_SEARCH_LOGS | query, from, to, limit |\n| List log indexes | DATADOG_LIST_LOG_INDEXES | (none) |\n| List monitors | DATADOG_LIST_MONITORS | tags |\n| Get monitor | DATADOG_GET_MONITOR | monitor_id |\n| Create monitor | DATADOG_CREATE_MONITOR | name, type, query, message |\n| Update monitor | DATADOG_UPDATE_MONITOR | monitor_id |\n| Mute monitor | DATADOG_MUTE_MONITOR | monitor_id |\n| Unmute monitor | DATADOG_UNMUTE_MONITOR | monitor_id |\n| List dashboards | DATADOG_LIST_DASHBOARDS | (none) |\n| Get dashboard | DATADOG_GET_DASHBOARD | dashboard_id |\n| Update dashboard | DATADOG_UPDATE_DASHBOARD | dashboard_id, title, widgets |\n| Delete dashboard | DATADOG_DELETE_DASHBOARD | dashboard_id |\n| List events | DATADOG_LIST_EVENTS | start, end |\n| Create event | DATADOG_CREATE_EVENT | title, text, alert_type |\n| Create downtime | DATADOG_CREATE_DOWNTIME | scope, start, end |\n| List hosts | DATADOG_LIST_HOSTS | filter, sort_field |\n| Get trace | DATADOG_GET_TRACE_BY_ID | trace_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":37,"source":42,"requires":48,"description":7},{"mcp":49},[50],"rube","release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Fdatadog-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 datadog-automation",{"tool":63,"command":64},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill datadog-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill datadog-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fdatadog-automation\u002FSKILL.md",true,[],[72,99,115,133,148,170],{"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,37,90,91,92,33,93,94,95,96,97,98],"zustand","store","zustand store ts","middleware","implementing","use","react state management","when","react","with","state","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":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",[105],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[107,108,25,42,109,41,39,110,38,37,32,31,111,29,112,113,28,114,96,27],"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":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,41,40,39,110,130,38,37,131,35,132,33],"crm automation","zoho crm automation","crm","zoho crm","zoho","leads","manage leads","records","convert","contacts",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"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",[139],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[141,25,142,42,41,39,110,38,143,37,35,144,145,32,31,146,29,28,27,147],"zendesk automation","zendesk","organizations","replies","users","tickets","automate",{"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":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",[],[155,156,157,158,159,160,161,162,163,25,164,37,165,166,167,168,169,147],"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":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",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[180,181,182,183,42,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"]