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.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill helpdesk-automation71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
60%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively communicates specific capabilities for HelpDesk automation with concrete actions. However, it lacks an explicit 'Use when...' clause that would help Claude know when to select this skill, and the trigger terms could be expanded to include more natural user language variations.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about support tickets, help desk automation, ticket management, or Composio HelpDesk tasks.'
Expand trigger terms to include common variations: 'support tickets', 'customer support', 'ticket management', 'help desk' (two words), 'ticketing system'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'list tickets, manage views, use canned responses, and configure custom fields.' These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific actions, but lacks an explicit 'Use when...' clause. The instruction 'Always search tools first' is operational guidance, not trigger guidance for when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'HelpDesk', 'tickets', 'canned responses', 'custom fields', but missing common variations users might say like 'support tickets', 'ticket system', 'customer support', or 'help desk' (two words). | 2 / 3 |
Distinctiveness Conflict Risk | Mentions specific platform 'Rube MCP (Composio)' and HelpDesk-specific terms, but 'tickets' and 'views' could overlap with other ticketing or project management skills. The niche is somewhat clear but not fully distinct. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid workflow structure and organization for HelpDesk automation, with clear setup steps and validation checkpoints. However, it suffers from redundant information across sections and lacks concrete executable examples - the patterns are described in prose rather than shown with actual tool call syntax and expected responses.
Suggestions
Add a concrete tool call example with actual JSON parameters and a sample response structure for HELPDESK_LIST_TICKETS
Consolidate pagination documentation into a single location instead of repeating across Key parameters, Common Patterns, and Known Pitfalls
Remove the duplicate silo listing (appears in both Key parameters and Ticket Folder Navigation pattern)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the pagination explanation appears in multiple places (Key parameters, Common Patterns, Known Pitfalls), and some pitfalls repeat information already stated. The silo options are listed twice. | 2 / 3 |
Actionability | Provides tool names and parameter lists, but lacks executable code examples. The 'Common Patterns' section uses pseudocode-style descriptions rather than actual tool call syntax. No concrete input/output examples showing what responses look like. | 2 / 3 |
Workflow Clarity | Clear numbered sequences for setup and each workflow. The setup section has explicit validation steps (verify connection, confirm ACTIVE status before proceeding). Tool sequences are marked as [Required] and ordered logically. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections: Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference table. Links to external toolkit docs. Content is appropriately structured for a single SKILL.md file without needing external references. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.