[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EY94JM24PWN4VCNW1DN8P1":3,"skill-same:01M6EY94JM24PWN4VCNW1DN8P1":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6EY94JM24PWN4VCNW1DN8P1","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.","ComeOnOliver\u002Fskillshub","ComeOnOliver","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F43215937?v=4","01M6E5JNFECJAAVFE0W7SMWWD2","Haoran Shu","01M6E5JNNDQS7AJZDYFQ8TPZCK",66,"MIT","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Fdatadog-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"automation","datadog automation","datadog","first","via","events","composio","query","manage","automate","dashboards","MCP","Tools","logs","search","metrics","create","tasks","query metrics","2026-11-10 10:12:30",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]\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","# 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",{"name":5,"requires":48,"description":7},{"mcp":49},[50],"rube","main","def8531e65114c0fca8fb8551c1871ee0eed705c","skills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Fdatadog-automation",24,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub","https:\u002F\u002Fskillshub.wtf","https:\u002F\u002Fgithub.com\u002FComeOnOliver","AI & Blockchain Engineer\r\n","2026-06-24 22:07:19",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add ComeOnOliver\u002Fskillshub --skill datadog-automation",{"tool":66,"command":67},"bunx","bunx skills add ComeOnOliver\u002Fskillshub --skill datadog-automation",{"tool":69,"command":70},"pnpm","pnpm dlx skills add ComeOnOliver\u002Fskillshub --skill datadog-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Fdatadog-automation\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"skill-report.json","REFERENCE","参考文档",9095,"https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Faiskillstore\u002Fmarketplace\u002Fsickn33\u002Fdatadog-automation\u002Fskill-report.json",[81,91,100,109,115,122],{"skillNo":82,"name":83,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":87,"publishedAt":43},"01M6FKJN13GMG4KY57J3QD8GY5","model-hierarchy-skill","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzscole\u002Fmodel-hierarchy-skill\u002Fmodel-hierarchy-skill\u002FSKILL.md",[86],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[88,89,90],"model","model hierarchy","model hierarchy skill",{"skillNo":92,"name":93,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":97,"publishedAt":43},"01M6FKJJJ6GCAMR4PPPRD12M5X","zoom-mcp","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-mcp\u002FSKILL.md",[96],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[35,98,99],"zoom","zoom mcp",{"skillNo":101,"name":102,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":43},"01M6FKJE3KYT3KPEZMEEHYKA6K","zoom-apps-sdk","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[106,107,108,98],"sdk","zoom apps sdk","apps",{"skillNo":110,"name":111,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":43},"01M6FKJ9EDH9Q5VWDF8HAJRSP0","windows","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwindows\u002FSKILL.md",[],[111],{"skillNo":116,"name":117,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":43},"01M6FKJ666BEEFC3AE9GJ72Q93","whiteboard","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwhiteboard\u002FSKILL.md",[120],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[117],{"skillNo":123,"name":124,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":43},"01M6FKJ21WFCDGTJQ2Q91T9DVW","websockets","https:\u002F\u002Fgithub.com\u002FComeOnOliver\u002Fskillshub\u002Fblob\u002Fmain\u002Fskills\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[124]]