freshdesk-automation

Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.

1.41x

Quality

65%

Does it follow best practices?

Impact

82%

1.41x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/freshdesk-automation/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable MCP tool reference with concrete parameters and query examples, but it suffers from systematic repetition of value tables and lacks validation/feedback checkpoints in its batch and core operation workflows.

Suggestions

De-duplicate the status/priority/source value tables and pagination facts: state them once and cross-reference, to recover token budget.

Add explicit verification steps to batch and destructive workflows (e.g., after FRESHDESK_IMPORT_CONTACT, verify imported contact count; after FRESHDESK_CREATE_TICKET, confirm via FRESHDESK_VIEW_TICKET).

Consider moving the full Quick Reference table and per-tool parameter details into a references/ file, keeping SKILL.md as a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Assumes Claude's competence (no 'what is a helpdesk' filler) and is reference-style, but repeats the same value tables multiple times — status/priority/source codes appear in workflow 1, workflow 2, and 'Known Pitfalls > Parameter Quirks', and pagination and the LIST_ALL_TICKETS note are restated across sections — which could be tightened.	3 / 5
Actionability	Provides concrete tool slugs, per-tool key parameters with types and value mappings, and concrete query syntax examples ('status:2 AND priority:3', "(created_at:>'2024-01-01' AND tag:'urgent')"); gaps are minor — no full tool-invocation example showing a complete call payload.	4 / 5
Workflow Clarity	Each core workflow has a 'When to use' clause and a numbered, tagged tool sequence, and Setup includes a validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows'); however the batch import and bulk/destructive operations lack post-operation verification or feedback loops, so per the rubric cap workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers (Prerequisites, Setup, Core Workflows 1-4, Common Patterns, Known Pitfalls, Quick Reference) and a navigation table; no nested references and no bundle files to misuse, though the long parameter tables and Quick Reference could arguably be split into a separate reference file.	4 / 5
	Total	14 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 specific and distinctive, clearly scoping a Freshdesk helpdesk automation niche with natural trigger terms, but it lacks any 'Use when...' trigger guidance, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to manage Freshdesk tickets, contacts, or companies, or asks about helpdesk/customer-support workflows.'

Replace the generic verb 'Automate' with a few concrete per-area actions (e.g., 'create, update, search, and reply to tickets; manage contacts and companies').

Include a synonym such as 'customer support' or 'ticketing' alongside 'helpdesk' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Freshdesk helpdesk) and enumerates five concrete capability areas — 'tickets, contacts, companies, notes, and replies' — plus the operational directive 'Always search tools first for current schemas'; the verb 'Automate' is generic rather than enumerating per-area actions, so it stops short of a 5.	4 / 5
Completeness	Clearly states WHAT ('Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies') but provides no 'Use when...' clause or equivalent trigger guidance; per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains natural user-facing terms — 'Freshdesk', 'helpdesk', 'tickets', 'contacts', 'companies', 'notes', 'replies' — that a user would plausibly say; missing common synonyms such as 'support desk', 'ticketing system', or 'Freshdesk API', so not a 5.	4 / 5
Distinctiveness Conflict Risk	Targets a specific product niche ('Freshdesk helpdesk operations ... via Rube MCP (Composio)') with distinct triggers and minimal overlap risk with other skills; would only conflict with another Freshdesk skill.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/freshdesk-automation/SKILL.md
Commit: a9fa86d

Reviewed: about 19 hours ago

Table of Contents

Discovery Implementation Validation

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.