CtrlK
BlogDocsLog inGet started
Tessl Logo

freshdesk-automation

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

78

1.41x
Quality

Does it follow best practices?

Impact

82%

1.41x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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-structured reference with exact tool/parameter details, but it carries redundancy across sections, lacks validation feedback loops for batch/destructive operations, and keeps all detailed content inline rather than splitting it into reference files.

Suggestions

Add explicit verify/validate checkpoints for batch and destructive operations (e.g., confirm connection ACTIVE, verify a contact exists before bulk import, confirm update results) to lift workflow clarity.

De-duplicate the status/priority/source enum mappings — define them once and reference that location from the per-workflow sections.

Move the full parameter reference and Quick Reference table into a separate REFERENCE.md to improve progressive disclosure and keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Avoids explaining concepts Claude already knows, but status/priority enum mappings appear in three places (ticket creation, search pitfalls, and 'Known Pitfalls') and the Quick Reference table largely restates earlier content, so it could be tightened.

2 / 3

Actionability

Provides exact tool names, parameter names, enum values, and concrete query syntax examples like '"status:2 AND priority:3"' — fully actionable guidance for an instruction-only MCP skill.

3 / 3

Workflow Clarity

Tool sequences are clearly numbered and the Setup section has a checkpoint ('Confirm connection status shows ACTIVE'), but batch/destructive operations such as FRESHDESK_IMPORT_CONTACT and the update tools lack explicit validate-then-proceed feedback loops, capping this at 2.

2 / 3

Progressive Disclosure

Sections are well-organized (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) but the file is a single monolithic ~217-line document with substantial inline reference content and no one-level-deep external references.

2 / 3

Total

9

/

12

Passed

Description

82%

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 that names concrete capabilities and uses natural trigger terms, but it omits an explicit 'Use when...' trigger clause, which caps its completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to manage Freshdesk tickets, contacts, companies, or replies.'

Include common natural variations users might say, such as 'support tickets' or 'helpdesk tickets', to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'tickets, contacts, companies, notes, and replies' — matching the 'lists multiple specific concrete actions' anchor rather than the score-2 single-domain example.

3 / 3

Completeness

Clearly states what the skill does, but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Uses natural terms a user would say ('Freshdesk helpdesk operations', 'tickets', 'contacts', 'companies', 'notes', 'replies') with good coverage, not just technical jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a clearly distinct niche (Freshdesk helpdesk automation via Rube MCP) with specific triggers unlikely to collide with other skills.

3 / 3

Total

11

/

12

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.

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