Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill freshdesk-automation78
Quality
72%
Does it follow best practices?
Impact
82%
1.41xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/freshdesk-automation/SKILL.mdDiscovery
67%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 identifies the specific platform (Freshdesk) and lists concrete operations (tickets, contacts, companies, notes, replies), making it distinctive and specific. However, it lacks an explicit 'Use when...' clause which limits its completeness score, and could benefit from more natural trigger term variations that users might actually say.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Freshdesk, support tickets, customer helpdesk, or managing customer contacts and companies.'
Include common trigger term variations like 'support tickets', 'customer support', 'help desk', 'ticket management', or 'customer service platform'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'tickets, contacts, companies, notes, and replies' along with the automation context and tool search guidance. These are concrete domain objects and operations. | 3 / 3 |
Completeness | Clearly answers 'what' (automate Freshdesk operations with specific entities), but lacks an explicit 'Use when...' clause. The when is only implied by mentioning Freshdesk and helpdesk operations. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Freshdesk', 'helpdesk', 'tickets', 'contacts' which users might say, but missing common variations like 'support tickets', 'customer support', 'help desk' (two words), or 'ticket management'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific to Freshdesk platform with distinct triggers. Mentions specific integration (Rube MCP/Composio) and Freshdesk-specific entities. Unlikely to conflict with other helpdesk or CRM skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill for Freshdesk automation with clear workflows and excellent parameter documentation. The main weaknesses are moderate verbosity from repeated information (status/priority values appear 3+ times) and the monolithic structure that could benefit from splitting reference material into separate files. The pitfalls sections are valuable but contribute to overall length.
Suggestions
Consolidate repeated parameter values (status codes, priority values) into a single 'Constants' section and reference it from workflows instead of repeating
Consider moving the detailed 'Known Pitfalls' and 'Quick Reference' sections to separate reference files (e.g., PITFALLS.md, REFERENCE.md) with links from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., status/priority values repeated multiple times across sections). The Quick Reference table duplicates information already covered in workflows. Could be tightened by consolidating repeated parameter definitions. | 2 / 3 |
Actionability | Provides concrete tool names, specific parameter names with exact values (status integers, priority integers), query syntax examples with proper quoting, and clear tool sequences. The Quick Reference table makes it copy-paste ready for common operations. | 3 / 3 |
Workflow Clarity | Each workflow has clear numbered sequences with [Required], [Optional], and [Prerequisite] annotations. The Setup section includes explicit verification steps (confirm ACTIVE status before proceeding). Tool sequences are well-ordered with clear dependencies. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document that could benefit from splitting detailed parameter references and pitfalls into separate files. The external toolkit docs link is good, but inline content is quite dense at ~300 lines. | 2 / 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 | |
Table of Contents
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.