[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XG0WN3DPKHM368V5PN0AD7":3,"skill-same:01M6XG0WN3DPKHM368V5PN0AD7":70},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":14,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6XG0WN3DPKHM368V5PN0AD7","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.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\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,43],"automation","datadog","datadog automation","manage","2026","search tools","unknown","for","via","composio","query","community","MCP","first","Tools","logs","search","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.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\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":30,"source":35,"date_added":49,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Fdatadog-automation","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill datadog-automation",{"tool":62,"command":63},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill datadog-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill datadog-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fdatadog-automation\u002FSKILL.md",true,[],[71,94,120,130,143,160],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":44},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[83,84,40,85,86,87,88,89,90,91,92,93],"wechat search","wechat","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":44},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[101,102,103,104,105,106,40,107,108,109,110,111,112,113,114,115,116,117,118,119],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":44},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[127,128,101,112,113,114,115,105,40,117,129,118,119,111,109,108,107,116,106,104],"trend radar","radar","pulse",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":44},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[137,138,139,140,141,142],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":44},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[145,90,153,154,155,93,112,156,157,158,103,159,116],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":44},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[162,167,168,169,116,170,157,171,172,173,174,175],"status","play","go","latest","github","discover","control","cmd","volume"]