Name: freshdesk
Rating: 62.4 (1 reviews)
Author: membranedev

freshdesk

Freshdesk integration. Manage Tickets, Contacts, Companies, Agents, Groups, Forums and more. Use when the user wants to interact with Freshdesk data.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/freshdesk/SKILL.md

Quality

Content

68%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 highly actionable with executable commands and a clear connection workflow including state-based checkpoints. Its weaknesses are mild over-explanation of Freshdesk basics Claude already knows, and the absence of validation/confirmation guidance for destructive delete operations, which caps workflow clarity.

Suggestions

Trim or remove the introductory paragraph explaining what Freshdesk is and who uses it; Claude already knows this and it costs context tokens.

Add explicit validation or confirmation guidance for destructive actions — e.g. 'Before delete-ticket, confirm the ticket ID with the user or verify via get-ticket; deletes move to Trash but other deletes are irreversible.'

Consider moving the full popular-actions table to a references file and keeping only the highest-value examples inline to improve progressive disclosure and reduce token load.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command examples and a compact actions table, but the opening paragraph explains what Freshdesk is and who uses it — concepts Claude already knows — and a few prose sections could be tightened.	3 / 5
Actionability	Provides copy-paste-ready executable commands throughout (install, login, connection ensure/get --wait, action list/run with --input JSON, request proxy with a full flag table), covering the common cases concretely.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling loop, but destructive operations (delete-ticket, delete-contact, delete-company) appear in the actions table with no validation or confirmation guidance, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Single well-organized SKILL.md with clear section headers and a popular-actions table; no bundle files exist, and the inline content is appropriately structured with only minor reference-organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

78%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.

A solid, third-person description that names concrete Freshdesk entities and includes an explicit 'Use when' trigger, giving it strong distinctiveness and completeness. The main weakness is relying on one generic verb ('Manage') across many nouns rather than distinct action verbs, and slightly generic trigger phrasing.

Suggestions

Replace the single generic verb 'Manage ... and more' with a few distinct concrete actions (e.g., 'list, create, update, and delete Tickets, Contacts, Companies, Agents, Groups, and Forums').

Sharpen the 'when' trigger with more specific natural phrases users say, e.g. 'Use when the user wants to list, create, or update Freshdesk tickets, contacts, or companies.'

Add a couple of trigger synonyms or surface-level phrasings (e.g. 'support tickets', 'helpdesk') to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete entities to manage (Tickets, Contacts, Companies, Agents, Groups, Forums), though the single generic verb 'Manage ... and more' applied across nouns leaves minor gaps versus distinct per-action verbs.	4 / 5
Completeness	Explicit 'what' (manage Tickets, Contacts, Companies, Agents, Groups, Forums) and an explicit 'when' ('Use when the user wants to interact with Freshdesk data') are both present, though the 'when' trigger could be more specific.	4 / 5
Trigger Term Quality	'interact with Freshdesk data' plus entity names (Tickets, Contacts) are natural user phrases, but it misses common synonyms and variations a user might say.	4 / 5
Distinctiveness Conflict Risk	'Freshdesk integration' scoped to named Freshdesk entities carves a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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: membranedev/application-skills
Path: skills/freshdesk/SKILL.md
Commit: f484c82

Reviewed: ~17 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.