CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

1.41x
Quality

73%

Does it follow best practices?

Impact

82%

1.41x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

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

A highly actionable, well-organized reference whose Freshdesk-specific parameter details are genuinely non-obvious, but it pays twice for them: the pitfalls are duplicated between workflow sections and the global 'Known Pitfalls' section, and the full tool reference is inlined rather than split into a separate reference file. Validation/feedback steps are present for setup but missing for batch import and rate-limited bulk operations.

Suggestions

Consolidate the duplicated pitfall content: keep the global 'Known Pitfalls' section as the single source for enum mappings, cf_ prefix rules, and search caps, and trim their repetition from each workflow's 'Pitfalls' block (or vice versa).

Add validation and feedback loops for batch/destructive operations: verify connection ACTIVE and a row-count/sample check after FRESHDESK_IMPORT_CONTACT, and a retry-on-429 pacing loop for bulk operations.

Move the per-tool parameter details and the 20-row Quick Reference table to a references/ file (e.g. references/tool-reference.md) and keep SKILL.md as a workflow-level overview with clearly signaled links.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious Freshdesk specifics and explains nothing Claude already knows, but the global 'Known Pitfalls' section restates the per-workflow 'Pitfalls' (status/priority enum mappings, the cf_ prefix rule, the 300-result search cap, and double-quote query syntax each appear two to three times), which goes beyond the 'minor instances' of anchor 4.

3 / 5

Actionability

Exact tool slugs, parameter names with required/optional status, integer enum mappings (e.g. 'status: 2=Open, 3=Pending'), and concrete query examples like '"status:2 AND priority:3"' make the guidance copy-paste actionable — fully matching the top anchor for an instruction-only skill.

5 / 5

Workflow Clarity

The four workflows have clear 'When to use' framing, numbered tool sequences with Required/Optional markers, and some checkpoints (confirm connection ACTIVE; VIEW_TICKET as prerequisite before replying), but batch and potentially destructive operations lack validation — FRESHDESK_IMPORT_CONTACT has no verify step and the 429/rate-limit guidance offers no retry feedback loop, so the batch-operation cap of 3 applies.

3 / 5

Progressive Disclosure

Sections are well-organized with headers and a Quick Reference table, but the entire per-tool parameter reference (~200 lines including the 20-row table) is inlined in SKILL.md with no one-level-deep reference files — content that belongs in a separate reference is inline, fitting between anchors 2 and 3.

3 / 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.

A specific, distinctive description with good natural keyword coverage, but it answers only 'what' and lacks any 'when to use this skill' trigger guidance. Adding a 'Use when...' clause naming concrete trigger scenarios would raise completeness substantially.

Suggestions

Append a trigger clause such as 'Use when the user mentions Freshdesk, support tickets, helpdesk requests, or asks to reply to, note, or search customer tickets.'

Replace the generic verb 'Automate ... operations' with the concrete actions per object, e.g. 'Create, update, and search tickets; reply to customers; add notes; manage contacts and companies'.

Drop the behavioral instruction 'Always search tools first for current schemas' from the description — it belongs in the body — and keep the description purely capability-and-trigger focused.

DimensionReasoningScore

Specificity

"Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies" names the domain and enumerates five concrete capability areas, matching the 'several specific actions; minor gaps' anchor — above anchor 3 because the object coverage is broad, below anchor 5 because the only verb is the generic 'automate' and no per-object actions (create, update, search) are stated.

4 / 5

Completeness

The description clearly answers 'what' (automate Freshdesk tickets, contacts, companies, notes, replies) but contains no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

"Freshdesk", "helpdesk", "tickets", "contacts", "companies", "notes", and "replies" are natural phrases users would say, giving good keyword coverage; a few common variants ("support tickets", "customer support") are missing and "Rube MCP (Composio)" is jargon users would not naturally utter, so not anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Freshdesk helpdesk operations ... via Rube MCP (Composio)" occupies a clear niche with product-specific triggers, minimal overlap risk with other skills — matches the 'clear niche with distinct triggers' anchor.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.