[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718QAM7NP8RFSVAQMBH2JSB":3,"skill-same:01M718QAM7NP8RFSVAQMBH2JSB":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},"01M718QAM7NP8RFSVAQMBH2JSB","freshservice-automation",null,"Automate Freshservice ITSM tasks via Rube MCP (Composio): create\u002Fupdate tickets, bulk operations, service requests, and outbound emails. 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\u002Fglobal\u002Ffreshservice-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","freshservice automation","2026","update","tickets","operations","via","requests","first","create","outbound","tasks","critical","bulk operations","MCP","emails","search","for","community","bulk","2026-11-10 10:12:30",false,"---\nname: freshservice-automation\ndescription: \"Automate Freshservice ITSM tasks via Rube MCP (Composio): create\u002Fupdate tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Freshservice Automation via Rube MCP\n\nAutomate Freshservice IT Service Management operations through Composio's Freshservice toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Freshservice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `freshservice`\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 `freshservice`\n3. If connection is not ACTIVE, follow the returned auth link to complete Freshservice authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Search Tickets\n\n**When to use**: User wants to find, list, or search for tickets\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - List tickets with optional filtering and pagination [Required]\n2. `FRESHSERVICE_GET_TICKET` - Get detailed information for a specific ticket [Optional]\n\n**Key parameters for listing**:\n- `filter`: Predefined filter ('all_tickets', 'deleted', 'spam', 'watching')\n- `updated_since`: ISO 8601 timestamp to get tickets updated after this time\n- `order_by`: Sort field ('created_at', 'updated_at', 'status', 'priority')\n- `order_type`: Sort direction ('asc' or 'desc')\n- `page`: Page number (1-indexed)\n- `per_page`: Results per page (1-100, default 30)\n- `include`: Additional fields ('requester', 'stats', 'description', 'conversations', 'assets')\n\n**Key parameters for get**:\n- `ticket_id`: Unique ticket ID or display_id\n- `include`: Additional fields to include\n\n**Pitfalls**:\n- By default, only tickets created within the past 30 days are returned\n- Use `updated_since` to retrieve older tickets\n- Each `include` value consumes additional API credits\n- `page` is 1-indexed; minimum value is 1\n- `per_page` max is 100; default is 30\n- Ticket IDs can be the internal ID or the display_id shown in the UI\n\n### 2. Create a Ticket\n\n**When to use**: User wants to log a new incident or request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET` - Create a new ticket [Required]\n\n**Key parameters**:\n- `subject`: Ticket subject line (required)\n- `description`: HTML description of the ticket (required)\n- `status`: Ticket status - 2 (Open), 3 (Pending), 4 (Resolved), 5 (Closed) (required)\n- `priority`: Ticket priority - 1 (Low), 2 (Medium), 3 (High), 4 (Urgent) (required)\n- `email`: Requester's email address (provide either email or requester_id)\n- `requester_id`: User ID of the requester\n- `type`: Ticket type ('Incident' or 'Service Request')\n- `source`: Channel - 1 (Email), 2 (Portal), 3 (Phone), 4 (Chat), 5 (Twitter), 6 (Facebook)\n- `impact`: Impact level - 1 (Low), 2 (Medium), 3 (High)\n- `urgency`: Urgency level - 1 (Low), 2 (Medium), 3 (High), 4 (Critical)\n\n**Pitfalls**:\n- `subject`, `description`, `status`, and `priority` are all required\n- Either `email` or `requester_id` must be provided to identify the requester\n- Status and priority use numeric codes, not string names\n- Description supports HTML formatting\n- If email does not match an existing contact, a new contact is created\n\n### 3. Bulk Update Tickets\n\n**When to use**: User wants to update multiple tickets at once\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - Find tickets to update [Prerequisite]\n2. `FRESHSERVICE_BULK_UPDATE_TICKETS` - Update multiple tickets [Required]\n\n**Key parameters**:\n- `ids`: Array of ticket IDs to update (required)\n- `update_fields`: Dictionary of fields to update (required)\n  - Allowed keys: 'subject', 'description', 'status', 'priority', 'responder_id', 'group_id', 'type', 'tags', 'custom_fields'\n\n**Pitfalls**:\n- Bulk update performs sequential updates internally; large batches may take time\n- All specified tickets receive the same field updates\n- If one ticket update fails, others may still succeed; check response for individual results\n- Cannot selectively update different fields per ticket in a single call\n- Custom fields must use their internal field names, not display names\n\n### 4. Create Ticket via Outbound Email\n\n**When to use**: User wants to create a ticket by sending an outbound email notification\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL` - Create ticket with email notification [Required]\n\n**Key parameters**:\n- `email`: Requester's email address (required)\n- `subject`: Email subject \u002F ticket subject (required)\n- `description`: HTML email body content\n- `status`: Ticket status (2=Open, 3=Pending, 4=Resolved, 5=Closed)\n- `priority`: Ticket priority (1=Low, 2=Medium, 3=High, 4=Urgent)\n- `cc_emails`: Array of CC email addresses\n- `email_config_id`: Email configuration ID for the sender address\n- `name`: Requester name\n\n**Pitfalls**:\n- This creates a standard ticket via the \u002Fapi\u002Fv2\u002Ftickets endpoint while sending an email\n- If the email does not match an existing contact, a new contact is created with the provided name\n- `email_config_id` determines which email address the notification appears to come from\n\n### 5. Create Service Requests\n\n**When to use**: User wants to submit a service catalog request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_SERVICE_REQUEST` - Create a service request for a catalog item [Required]\n\n**Key parameters**:\n- `item_display_id`: Display ID of the catalog item (required)\n- `email`: Requester's email address\n- `quantity`: Number of items to request (default: 1)\n- `custom_fields`: Custom field values for the service item form\n- `parent_ticket_id`: Display ID of a parent ticket (for child requests)\n\n**Pitfalls**:\n- `item_display_id` can be found in Admin > Service Catalog > item URL (e.g., \u002Fservice_catalog\u002Fitems\u002F1)\n- Custom fields keys must match the service item form field names\n- Quantity defaults to 1 if not specified\n- Service requests follow the approval workflow defined for the catalog item\n\n## Common Patterns\n\n### Status Code Reference\n\n| Code | Status |\n|------|--------|\n| 2 | Open |\n| 3 | Pending |\n| 4 | Resolved |\n| 5 | Closed |\n\n### Priority Code Reference\n\n| Code | Priority |\n|------|----------|\n| 1 | Low |\n| 2 | Medium |\n| 3 | High |\n| 4 | Urgent |\n\n### Pagination\n\n- Use `page` (1-indexed) and `per_page` (max 100) parameters\n- Increment `page` by 1 each request\n- Continue until returned results count \u003C `per_page`\n- Default page size is 30\n\n### Finding Tickets by Date Range\n\n```\n1. Call FRESHSERVICE_LIST_TICKETS with updated_since='2024-01-01T00:00:00Z'\n2. Optionally add order_by='updated_at' and order_type='desc'\n3. Paginate through results\n```\n\n## Known Pitfalls\n\n**Numeric Codes**:\n- Status and priority use numeric values, not strings\n- Source channel uses numeric codes (1-6)\n- Impact and urgency use numeric codes (1-3 or 1-4)\n\n**Date Filtering**:\n- Default returns only tickets from the last 30 days\n- Use `updated_since` parameter for older tickets\n- Date format is ISO 8601 (e.g., '2024-01-01T00:00:00Z')\n\n**Rate Limits**:\n- Freshservice API has per-account rate limits\n- Each `include` option consumes additional API credits\n- Implement backoff on 429 responses\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Ticket IDs are numeric integers\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | FRESHSERVICE_LIST_TICKETS | filter, updated_since, page, per_page |\n| Get ticket | FRESHSERVICE_GET_TICKET | ticket_id, include |\n| Create ticket | FRESHSERVICE_CREATE_TICKET | subject, description, status, priority, email |\n| Bulk update | FRESHSERVICE_BULK_UPDATE_TICKETS | ids, update_fields |\n| Outbound email ticket | FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL | email, subject, description |\n| Service request | FRESHSERVICE_CREATE_SERVICE_REQUEST | item_display_id, email, quantity |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Freshservice Automation via Rube MCP\n\nAutomate Freshservice IT Service Management operations through Composio's Freshservice toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Freshservice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `freshservice`\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 `freshservice`\n3. If connection is not ACTIVE, follow the returned auth link to complete Freshservice authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Search Tickets\n\n**When to use**: User wants to find, list, or search for tickets\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - List tickets with optional filtering and pagination [Required]\n2. `FRESHSERVICE_GET_TICKET` - Get detailed information for a specific ticket [Optional]\n\n**Key parameters for listing**:\n- `filter`: Predefined filter ('all_tickets', 'deleted', 'spam', 'watching')\n- `updated_since`: ISO 8601 timestamp to get tickets updated after this time\n- `order_by`: Sort field ('created_at', 'updated_at', 'status', 'priority')\n- `order_type`: Sort direction ('asc' or 'desc')\n- `page`: Page number (1-indexed)\n- `per_page`: Results per page (1-100, default 30)\n- `include`: Additional fields ('requester', 'stats', 'description', 'conversations', 'assets')\n\n**Key parameters for get**:\n- `ticket_id`: Unique ticket ID or display_id\n- `include`: Additional fields to include\n\n**Pitfalls**:\n- By default, only tickets created within the past 30 days are returned\n- Use `updated_since` to retrieve older tickets\n- Each `include` value consumes additional API credits\n- `page` is 1-indexed; minimum value is 1\n- `per_page` max is 100; default is 30\n- Ticket IDs can be the internal ID or the display_id shown in the UI\n\n### 2. Create a Ticket\n\n**When to use**: User wants to log a new incident or request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET` - Create a new ticket [Required]\n\n**Key parameters**:\n- `subject`: Ticket subject line (required)\n- `description`: HTML description of the ticket (required)\n- `status`: Ticket status - 2 (Open), 3 (Pending), 4 (Resolved), 5 (Closed) (required)\n- `priority`: Ticket priority - 1 (Low), 2 (Medium), 3 (High), 4 (Urgent) (required)\n- `email`: Requester's email address (provide either email or requester_id)\n- `requester_id`: User ID of the requester\n- `type`: Ticket type ('Incident' or 'Service Request')\n- `source`: Channel - 1 (Email), 2 (Portal), 3 (Phone), 4 (Chat), 5 (Twitter), 6 (Facebook)\n- `impact`: Impact level - 1 (Low), 2 (Medium), 3 (High)\n- `urgency`: Urgency level - 1 (Low), 2 (Medium), 3 (High), 4 (Critical)\n\n**Pitfalls**:\n- `subject`, `description`, `status`, and `priority` are all required\n- Either `email` or `requester_id` must be provided to identify the requester\n- Status and priority use numeric codes, not string names\n- Description supports HTML formatting\n- If email does not match an existing contact, a new contact is created\n\n### 3. Bulk Update Tickets\n\n**When to use**: User wants to update multiple tickets at once\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - Find tickets to update [Prerequisite]\n2. `FRESHSERVICE_BULK_UPDATE_TICKETS` - Update multiple tickets [Required]\n\n**Key parameters**:\n- `ids`: Array of ticket IDs to update (required)\n- `update_fields`: Dictionary of fields to update (required)\n  - Allowed keys: 'subject', 'description', 'status', 'priority', 'responder_id', 'group_id', 'type', 'tags', 'custom_fields'\n\n**Pitfalls**:\n- Bulk update performs sequential updates internally; large batches may take time\n- All specified tickets receive the same field updates\n- If one ticket update fails, others may still succeed; check response for individual results\n- Cannot selectively update different fields per ticket in a single call\n- Custom fields must use their internal field names, not display names\n\n### 4. Create Ticket via Outbound Email\n\n**When to use**: User wants to create a ticket by sending an outbound email notification\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL` - Create ticket with email notification [Required]\n\n**Key parameters**:\n- `email`: Requester's email address (required)\n- `subject`: Email subject \u002F ticket subject (required)\n- `description`: HTML email body content\n- `status`: Ticket status (2=Open, 3=Pending, 4=Resolved, 5=Closed)\n- `priority`: Ticket priority (1=Low, 2=Medium, 3=High, 4=Urgent)\n- `cc_emails`: Array of CC email addresses\n- `email_config_id`: Email configuration ID for the sender address\n- `name`: Requester name\n\n**Pitfalls**:\n- This creates a standard ticket via the \u002Fapi\u002Fv2\u002Ftickets endpoint while sending an email\n- If the email does not match an existing contact, a new contact is created with the provided name\n- `email_config_id` determines which email address the notification appears to come from\n\n### 5. Create Service Requests\n\n**When to use**: User wants to submit a service catalog request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_SERVICE_REQUEST` - Create a service request for a catalog item [Required]\n\n**Key parameters**:\n- `item_display_id`: Display ID of the catalog item (required)\n- `email`: Requester's email address\n- `quantity`: Number of items to request (default: 1)\n- `custom_fields`: Custom field values for the service item form\n- `parent_ticket_id`: Display ID of a parent ticket (for child requests)\n\n**Pitfalls**:\n- `item_display_id` can be found in Admin > Service Catalog > item URL (e.g., \u002Fservice_catalog\u002Fitems\u002F1)\n- Custom fields keys must match the service item form field names\n- Quantity defaults to 1 if not specified\n- Service requests follow the approval workflow defined for the catalog item\n\n## Common Patterns\n\n### Status Code Reference\n\n| Code | Status |\n|------|--------|\n| 2 | Open |\n| 3 | Pending |\n| 4 | Resolved |\n| 5 | Closed |\n\n### Priority Code Reference\n\n| Code | Priority |\n|------|----------|\n| 1 | Low |\n| 2 | Medium |\n| 3 | High |\n| 4 | Urgent |\n\n### Pagination\n\n- Use `page` (1-indexed) and `per_page` (max 100) parameters\n- Increment `page` by 1 each request\n- Continue until returned results count \u003C `per_page`\n- Default page size is 30\n\n### Finding Tickets by Date Range\n\n```\n1. Call FRESHSERVICE_LIST_TICKETS with updated_since='2024-01-01T00:00:00Z'\n2. Optionally add order_by='updated_at' and order_type='desc'\n3. Paginate through results\n```\n\n## Known Pitfalls\n\n**Numeric Codes**:\n- Status and priority use numeric values, not strings\n- Source channel uses numeric codes (1-6)\n- Impact and urgency use numeric codes (1-3 or 1-4)\n\n**Date Filtering**:\n- Default returns only tickets from the last 30 days\n- Use `updated_since` parameter for older tickets\n- Date format is ISO 8601 (e.g., '2024-01-01T00:00:00Z')\n\n**Rate Limits**:\n- Freshservice API has per-account rate limits\n- Each `include` option consumes additional API credits\n- Implement backoff on 429 responses\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Ticket IDs are numeric integers\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | FRESHSERVICE_LIST_TICKETS | filter, updated_since, page, per_page |\n| Get ticket | FRESHSERVICE_GET_TICKET | ticket_id, include |\n| Create ticket | FRESHSERVICE_CREATE_TICKET | subject, description, status, priority, email |\n| Bulk update | FRESHSERVICE_BULK_UPDATE_TICKETS | ids, update_fields |\n| Outbound email ticket | FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL | email, subject, description |\n| Service request | FRESHSERVICE_CREATE_SERVICE_REQUEST | item_display_id, email, quantity |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":36,"source":42,"date_added":49,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fglobal\u002Ffreshservice-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 freshservice-automation",{"tool":62,"command":63},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill freshservice-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill freshservice-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Ffreshservice-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"]