[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CKBB8TZCTH0CEXNJEQHE4Z":3,"skill-same:01M7CKBB8TZCTH0CEXNJEQHE4Z":50},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CKBB8TZCTH0CEXNJEQHE4Z","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.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fhelpdesk-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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: critical\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fhelpdesk-automation",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill helpdesk-automation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill helpdesk-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill helpdesk-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fhelpdesk-automation\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"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":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]