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 does a good job specifying the domain (Freshdesk) and listing concrete entities it operates on, making it distinctive. However, it lacks an explicit 'Use when...' clause which caps completeness, and could benefit from additional natural trigger terms users might use when requesting helpdesk-related assistance.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Freshdesk tickets, customer support workflows, helpdesk automation, or managing contacts and companies in Freshdesk.'
Include common trigger term variations such as 'support tickets', 'customer support', 'help desk', 'ticket management', and 'Freshdesk API' to improve matching.
| 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 | The 'what' is clearly stated (automate Freshdesk operations including tickets, contacts, etc.), but there is no explicit 'Use when...' clause or equivalent trigger guidance explaining 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' which are natural terms. However, it misses common variations users might say like 'support tickets', 'customer support', 'help desk', 'ticket management', or 'CRM'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Freshdesk and the Rube MCP (Composio) integration, making it very unlikely to conflict with other skills. 'Freshdesk' is a distinct product name that creates a clear niche. | 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 highly actionable Freshdesk automation skill with specific tool names, parameters, query syntax examples, and a useful quick reference table. Its main weaknesses are verbosity with repeated information (status/priority mappings, cf_ prefix notes), lack of explicit validation/error-handling steps in workflows, and all content being packed into a single file rather than using progressive disclosure with linked references.
Suggestions
Deduplicate repeated information (status/priority integer mappings, cf_ prefix notes) by consolidating them into the Known Pitfalls or Quick Reference section and referencing that section from workflows.
Add explicit validation checkpoints to workflows, e.g., 'Verify ticket was created by checking the returned ticket_id' or 'If 429 rate limit error, wait and retry'.
Consider splitting detailed parameter lists and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with tool sequences and links to details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite lengthy (~200+ lines) with some redundancy—status/priority integer mappings are repeated three times (in create ticket, search tickets, and known pitfalls), and the custom field cf_ prefix note appears twice. The pitfalls sections contain useful non-obvious information, but the overall document could be tightened significantly. | 2 / 3 |
Actionability | Provides specific tool names, exact parameter names, concrete query syntax examples (e.g., `"email:'user@example.com'"`, `"status:2 AND priority:3"`), integer value mappings, and a comprehensive quick reference table. The guidance is directly executable with the MCP tools. | 3 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps and labeled as Required/Optional/Prerequisite, which is good. However, there are no explicit validation or error-handling checkpoints—no guidance on what to do if a tool call fails, returns unexpected results, or hits rate limits. For operations like replying to tickets or creating contacts, verification steps are missing. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's monolithic—all content is inline in a single file. The detailed parameter lists and pitfalls for each workflow could be split into separate reference files, with the main SKILL.md serving as a concise overview with links. | 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
7cc63f3
- 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.