Agent skill · operations · aiskillstore
helpdesk-automation
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.
Why this skill is useful
Adds specific commands and workflows for automating HelpDesk tasks that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
HelpDesk Automation via Rube MCP Automate HelpDesk ticketing operations through Composio's HelpDesk toolkit via Rube MCP. Prerequisites Rube MCP must be connected (RUBESEARCHTOOLS available) Active HelpDesk connection via RUBEMANAGECONNECTIONS with toolkit helpdesk Always call RUBESEARCHTOOLS first to get current tool schemas Setup Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds 2. Call RUBEMANAGECONNECTIONS with toolkit helpdesk 3. If connection is not ACTIVE, follow the returned auth link to complete HelpDesk authentication 4. Confirm connection status shows ACTIVE before running any workflows Core Workflows 1. List and Browse Tickets When to use: User wants to retrieve, browse, or paginate through support tickets Tool sequence: 1. HELPDESKLISTTICKETS - List tickets with sorting and pagination [Required] Key parameters: silo: Ticket folder - 'tickets', 'archive', 'trash', or 'spam' (default: 'tickets') sortBy: Sort field - 'createdAt', 'updatedAt', or 'lastMessageAt' (default: 'createdAt') order: Sort direction - 'asc' or 'desc' (default: 'desc') pageSize: Results per page, 1-100 (default: 20) next.value: Timestamp cursor for forward pagination next.ID: ID cursor for forward pagination prev.value: Timestamp cursor for backward pagination prev.ID: ID cursor for backward pagination Pitfalls: Pagination uses cursor-based approach with timestamp + ID pairs Forward pagination requires both next.value and next.ID from previous response Backward pagination requires both prev.value and prev.ID silo determines which folder to list from; default is active tickets pageSize max is 100; default is 20 Archived and trashed tickets are in separate silos 2. Manage Ticket Views When to use: User wants to see saved agent views for organizing tickets Tool sequence: 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/helpdesk-automation