[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSKN8MB1H4GEWRV51ZWZPJ":3,"skill-same:01M6FSKN8MB1H4GEWRV51ZWZPJ":71},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":14,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6FSKN8MB1H4GEWRV51ZWZPJ","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.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\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],"automation","helpdesk automation","MCP","tasks","search","Tools","first","configure","automate","list","use","manage","community","composio","via","tickets","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.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\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":45,"source":36,"requires":46,"description":7},"unknown",{"mcp":47},[48],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fhelpdesk-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add reikiplanet\u002Fdaoskills --skill helpdesk-automation",{"tool":63,"command":64},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill helpdesk-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill helpdesk-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fhelpdesk-automation\u002FSKILL.md",true,[],[72,98,110,124,144,167],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":40},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[79,80,81,82,83,84,36,85,86,87,88,89,90,91,92,93,94,95,96,97],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":40},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[105,106,96,107,108,36,86,87,88,82,109,83],"ar","vr ar","interaction","requirements","performance",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":40},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[112,117,118,119,120,121,36,34,88,122,123,82],"project scaffolding","From Scratch","tech","project","scaffolding","projects","applications",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":40},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[131,132,133,134,135,36,136,137,138,139,34,140,141,142,143],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":40},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[151,152,153,154,155,156,157,158,36,88,82,159,83,160,161,162,163,164,165,166],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":40},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[174,175,176,177,178,179,180,181,164,34,182,183,184,36,185,186,187,161,188,189],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]