freshdesk-automation
Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.
74
66%
Does it follow best practices?
Impact
82%
1.41xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/freshdesk-automation/SKILL.mdQuality
Discovery
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 is reasonably strong in specificity and distinctiveness, clearly naming the Freshdesk platform and the specific entities it manages. However, it lacks an explicit 'Use when...' clause, which caps completeness, and could benefit from additional natural trigger terms that users might say when needing helpdesk support automation.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Freshdesk, managing support tickets, customer contacts, or helpdesk automation.'
Include additional natural trigger terms like 'support tickets', 'customer support', 'help desk', 'ticket management', or 'customer service' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete entities and actions: 'tickets, contacts, companies, notes, and replies' along with the automation context via 'Rube MCP (Composio)'. Also includes the operational guidance to 'search tools first for current schemas.' | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Freshdesk operations including tickets, contacts, etc.), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied by the domain. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Freshdesk', 'helpdesk', 'tickets', 'contacts', 'companies', 'notes', 'replies', but misses common user variations like 'support tickets', 'customer support', 'help desk', 'ticket management', or 'CRM'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clearly scoped to 'Freshdesk' and 'Rube MCP (Composio)', which are highly specific identifiers. Unlikely to conflict with other helpdesk or CRM skills due to the explicit platform naming. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and actionable Freshdesk automation skill with specific tool names, parameter details, and practical query examples. Its main weaknesses are significant content repetition (status/priority mappings, pitfalls duplicated across sections) that inflates token cost, and a lack of validation/error-handling steps in workflows. The monolithic structure could benefit from splitting detailed parameter references into a separate file.
Suggestions
Deduplicate repeated content: define status/priority integer mappings once (e.g., in Known Pitfalls or a reference section) and reference that single location instead of repeating in each workflow.
Add validation and error recovery steps to workflows — e.g., 'If FRESHDESK_CREATE_TICKET returns an error, check that requester_id or email is valid' or 'If rate-limited (429), wait and retry'.
Consider splitting detailed parameter documentation and the quick reference table into a separate REFERENCE.md file, keeping SKILL.md as a concise workflow guide with pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite lengthy (~200+ lines) with significant repetition — status/priority integer mappings are repeated 3+ times across sections, and pitfalls are duplicated between workflow-specific sections and the 'Known Pitfalls' section. The quick reference table adds value but much of the parameter documentation could be tightened. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides specific tool names, exact parameter names and types, concrete query syntax examples (e.g., `"email:'user@example.com'"`, `"status:2 AND priority:3"`), integer mappings for enums, and clear tool sequences. The guidance is directly executable through the MCP tools described. | 3 / 3 |
Workflow Clarity | Tool sequences are clearly listed with step ordering and optional/required annotations, which is good. However, there are no explicit validation checkpoints or error recovery steps — e.g., no guidance on what to do if ticket creation fails, if search returns no results, or if rate limits are hit. For operations like bulk imports or replies, feedback loops are missing. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's monolithic — all content is in a single file with no references to supporting files. The repeated parameter details and pitfalls across sections could be split into a reference document. The external link to Composio docs is helpful but the skill itself would benefit from splitting detailed parameter docs into a separate reference. | 2 / 3 |
Total | 9 / 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- 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.