[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M716834PRKJSVERTFDAZTYQS":3,"skill-same:01M716834PRKJSVERTFDAZTYQS":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},"01M716834PRKJSVERTFDAZTYQS","helpdesk-automation",null,"Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. 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\u002Fcursor\u002Fhelpdesk-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],"helpdesk automation","automation","composio","list","fields","search tools","2026","tickets","via","first","tasks","unknown","configure","use","MCP","custom","search","manage","for","community","2026-11-10 10:12:30",false,"---\nname: helpdesk-automation\ndescription: \"Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# HelpDesk Automation via Rube MCP\n\nAutomate HelpDesk ticketing operations through Composio's HelpDesk toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active HelpDesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `helpdesk`\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 `helpdesk`\n3. If connection is not ACTIVE, follow the returned auth link to complete HelpDesk authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Browse Tickets\n\n**When to use**: User wants to retrieve, browse, or paginate through support tickets\n\n**Tool sequence**:\n1. `HELPDESK_LIST_TICKETS` - List tickets with sorting and pagination [Required]\n\n**Key parameters**:\n- `silo`: Ticket folder - 'tickets', 'archive', 'trash', or 'spam' (default: 'tickets')\n- `sortBy`: Sort field - 'createdAt', 'updatedAt', or 'lastMessageAt' (default: 'createdAt')\n- `order`: Sort direction - 'asc' or 'desc' (default: 'desc')\n- `pageSize`: Results per page, 1-100 (default: 20)\n- `next.value`: Timestamp cursor for forward pagination\n- `next.ID`: ID cursor for forward pagination\n- `prev.value`: Timestamp cursor for backward pagination\n- `prev.ID`: ID cursor for backward pagination\n\n**Pitfalls**:\n- Pagination uses cursor-based approach with timestamp + ID pairs\n- Forward pagination requires both `next.value` and `next.ID` from previous response\n- Backward pagination requires both `prev.value` and `prev.ID`\n- `silo` determines which folder to list from; default is active tickets\n- `pageSize` max is 100; default is 20\n- Archived and trashed tickets are in separate silos\n\n### 2. Manage Ticket Views\n\n**When to use**: User wants to see saved agent views for organizing tickets\n\n**Tool sequence**:\n1. `HELPDESK_LIST_VIEWS` - List all agent views [Required]\n\n**Key parameters**: (none required)\n\n**Pitfalls**:\n- Views are predefined saved filters configured by agents in the HelpDesk UI\n- View definitions include filter criteria that can be used to understand ticket organization\n- Views cannot be created or modified via API; they are managed in the HelpDesk UI\n\n### 3. Use Canned Responses\n\n**When to use**: User wants to list available canned (template) responses for tickets\n\n**Tool sequence**:\n1. `HELPDESK_LIST_CANNED_RESPONSES` - Retrieve all predefined reply templates [Required]\n\n**Key parameters**: (none required)\n\n**Pitfalls**:\n- Canned responses are predefined templates for common replies\n- They may include placeholder variables that need to be filled in\n- Canned responses are managed through the HelpDesk UI\n- Response content may include HTML formatting\n\n### 4. Inspect Custom Fields\n\n**When to use**: User wants to view custom field definitions for the account\n\n**Tool sequence**:\n1. `HELPDESK_LIST_CUSTOM_FIELDS` - List all custom field definitions [Required]\n\n**Key parameters**: (none required)\n\n**Pitfalls**:\n- Custom fields extend the default ticket schema with organization-specific data\n- Field definitions include field type, name, and validation rules\n- Custom fields are configured in the HelpDesk admin panel\n- Field values appear on tickets when the field has been populated\n\n## Common Patterns\n\n### Ticket Browsing Pattern\n\n```\n1. Call HELPDESK_LIST_TICKETS with desired silo and sortBy\n2. Process the returned page of tickets\n3. Extract next.value and next.ID from the response\n4. Call HELPDESK_LIST_TICKETS with those cursor values for next page\n5. Continue until no more cursor values are returned\n```\n\n### Ticket Folder Navigation\n\n```\nActive tickets:  silo='tickets'\nArchived:        silo='archive'\nTrashed:         silo='trash'\nSpam:            silo='spam'\n```\n\n### Cursor-Based Pagination\n\n```\nForward pagination:\n  - Use next.value (timestamp) and next.ID from response\n  - Pass as next.value and next.ID parameters in next call\n\nBackward pagination:\n  - Use prev.value (timestamp) and prev.ID from response\n  - Pass as prev.value and prev.ID parameters in next call\n```\n\n## Known Pitfalls\n\n**Cursor Pagination**:\n- Both timestamp and ID are required for cursor navigation\n- Cursor values are timestamps in ISO 8601 date-time format\n- Mixing forward and backward cursors in the same request is undefined behavior\n\n**Silo Filtering**:\n- Tickets are physically separated into silos (folders)\n- Moving tickets between silos is done in the HelpDesk UI\n- Each silo query is independent; there is no cross-silo search\n\n**Read-Only Operations**:\n- Current Composio toolkit provides list\u002Fread operations\n- Ticket creation, update, and reply operations may require additional tools\n- Check RUBE_SEARCH_TOOLS for any newly available tools\n\n**Rate Limits**:\n- HelpDesk API has per-account rate limits\n- Implement backoff on 429 responses\n- Keep page sizes reasonable to avoid timeouts\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 strings\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | HELPDESK_LIST_TICKETS | silo, sortBy, order, pageSize |\n| List views | HELPDESK_LIST_VIEWS | (none) |\n| List canned responses | HELPDESK_LIST_CANNED_RESPONSES | (none) |\n| List custom fields | HELPDESK_LIST_CUSTOM_FIELDS | (none) |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# HelpDesk Automation via Rube MCP\n\nAutomate HelpDesk ticketing operations through Composio's HelpDesk toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active HelpDesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `helpdesk`\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 `helpdesk`\n3. If connection is not ACTIVE, follow the returned auth link to complete HelpDesk authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Browse Tickets\n\n**When to use**: User wants to retrieve, browse, or paginate through support tickets\n\n**Tool sequence**:\n1. `HELPDESK_LIST_TICKETS` - List tickets with sorting and pagination [Required]\n\n**Key parameters**:\n- `silo`: Ticket folder - 'tickets', 'archive', 'trash', or 'spam' (default: 'tickets')\n- `sortBy`: Sort field - 'createdAt', 'updatedAt', or 'lastMessageAt' (default: 'createdAt')\n- `order`: Sort direction - 'asc' or 'desc' (default: 'desc')\n- `pageSize`: Results per page, 1-100 (default: 20)\n- `next.value`: Timestamp cursor for forward pagination\n- `next.ID`: ID cursor for forward pagination\n- `prev.value`: Timestamp cursor for backward pagination\n- `prev.ID`: ID cursor for backward pagination\n\n**Pitfalls**:\n- Pagination uses cursor-based approach with timestamp + ID pairs\n- Forward pagination requires both `next.value` and `next.ID` from previous response\n- Backward pagination requires both `prev.value` and `prev.ID`\n- `silo` determines which folder to list from; default is active tickets\n- `pageSize` max is 100; default is 20\n- Archived and trashed tickets are in separate silos\n\n### 2. Manage Ticket Views\n\n**When to use**: User wants to see saved agent views for organizing tickets\n\n**Tool sequence**:\n1. `HELPDESK_LIST_VIEWS` - List all agent views [Required]\n\n**Key parameters**: (none required)\n\n**Pitfalls**:\n- Views are predefined saved filters configured by agents in the HelpDesk UI\n- View definitions include filter criteria that can be used to understand ticket organization\n- Views cannot be created or modified via API; they are managed in the HelpDesk UI\n\n### 3. Use Canned Responses\n\n**When to use**: User wants to list available canned (template) responses for tickets\n\n**Tool sequence**:\n1. `HELPDESK_LIST_CANNED_RESPONSES` - Retrieve all predefined reply templates [Required]\n\n**Key parameters**: (none required)\n\n**Pitfalls**:\n- Canned responses are predefined templates for common replies\n- They may include placeholder variables that need to be filled in\n- Canned responses are managed through the HelpDesk UI\n- Response content may include HTML formatting\n\n### 4. Inspect Custom Fields\n\n**When to use**: User wants to view custom field definitions for the account\n\n**Tool sequence**:\n1. `HELPDESK_LIST_CUSTOM_FIELDS` - List all custom field definitions [Required]\n\n**Key parameters**: (none required)\n\n**Pitfalls**:\n- Custom fields extend the default ticket schema with organization-specific data\n- Field definitions include field type, name, and validation rules\n- Custom fields are configured in the HelpDesk admin panel\n- Field values appear on tickets when the field has been populated\n\n## Common Patterns\n\n### Ticket Browsing Pattern\n\n```\n1. Call HELPDESK_LIST_TICKETS with desired silo and sortBy\n2. Process the returned page of tickets\n3. Extract next.value and next.ID from the response\n4. Call HELPDESK_LIST_TICKETS with those cursor values for next page\n5. Continue until no more cursor values are returned\n```\n\n### Ticket Folder Navigation\n\n```\nActive tickets:  silo='tickets'\nArchived:        silo='archive'\nTrashed:         silo='trash'\nSpam:            silo='spam'\n```\n\n### Cursor-Based Pagination\n\n```\nForward pagination:\n  - Use next.value (timestamp) and next.ID from response\n  - Pass as next.value and next.ID parameters in next call\n\nBackward pagination:\n  - Use prev.value (timestamp) and prev.ID from response\n  - Pass as prev.value and prev.ID parameters in next call\n```\n\n## Known Pitfalls\n\n**Cursor Pagination**:\n- Both timestamp and ID are required for cursor navigation\n- Cursor values are timestamps in ISO 8601 date-time format\n- Mixing forward and backward cursors in the same request is undefined behavior\n\n**Silo Filtering**:\n- Tickets are physically separated into silos (folders)\n- Moving tickets between silos is done in the HelpDesk UI\n- Each silo query is independent; there is no cross-silo search\n\n**Read-Only Operations**:\n- Current Composio toolkit provides list\u002Fread operations\n- Ticket creation, update, and reply operations may require additional tools\n- Check RUBE_SEARCH_TOOLS for any newly available tools\n\n**Rate Limits**:\n- HelpDesk API has per-account rate limits\n- Implement backoff on 429 responses\n- Keep page sizes reasonable to avoid timeouts\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 strings\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | HELPDESK_LIST_TICKETS | silo, sortBy, order, pageSize |\n| List views | HELPDESK_LIST_VIEWS | (none) |\n| List canned responses | HELPDESK_LIST_CANNED_RESPONSES | (none) |\n| List custom fields | HELPDESK_LIST_CUSTOM_FIELDS | (none) |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":35,"source":43,"date_added":49,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcursor\u002Fhelpdesk-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 helpdesk-automation",{"tool":62,"command":63},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill helpdesk-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill helpdesk-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcursor\u002Fhelpdesk-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"]