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.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/freshdesk-automation/SKILL.md

The canonical home for this skill is freshdesk-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 thorough, highly actionable body with concrete tool sequences and pitfalls, weakened by duplicated reference content and absent validation feedback loops on batch/destructive operations. Splitting the quick reference into a bundled file and adding post-op verification steps would notably improve it.

Suggestions

Add explicit post-operation verification steps for batch/destructive actions (e.g., after FRESHDESK_IMPORT_CONTACT or FRESHDESK_UPDATE_TICKET, re-fetch and confirm the result; handle 429 retries) to lift workflow_clarity above 3.

Move the consolidated quick-reference table and "Known Pitfalls" section into a bundled reference file (e.g., references/quick-reference.md) and link to it from SKILL.md to improve progressive disclosure and reduce duplication.

De-duplicate the status/priority/source value tables that appear in both the workflow sections and the Known Pitfalls section, keeping a single canonical source.

DimensionReasoningScore

Conciseness

Mostly efficient reference material, but status/priority value tables and several pitfalls are repeated across the workflow sections and the "Known Pitfalls" section, which could be consolidated.

4 / 5

Actionability

Provides concrete tool slugs, exact parameter names, integer value mappings, and copy-ready query syntax (e.g., "status:2 AND priority:3") covering the common cases.

5 / 5

Workflow Clarity

Sequences are clearly numbered with "When to use" and prerequisites, but destructive/batch operations (ticket updates, bulk contact import) lack post-operation validation or feedback loops, capping this at 3 per the rubric.

3 / 5

Progressive Disclosure

A single well-organized file with clear headers, but no bundle files exist and substantial content (the full quick-reference table and consolidated pitfalls) is inlined that could be split into reference files for easier navigation.

3 / 5

Total

15

/

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 clear, third-person description that names a distinct niche and concrete operations, but it omits an explicit "Use when..." trigger clause, leaving the activation guidance implicit. Adding concrete trigger phrases would lift completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause naming user-side triggers (e.g., "Use when managing Freshdesk support tickets, contacts, or companies, or when the user asks to automate helpdesk workflows").

Include natural synonyms like "support tickets" or "customer support" to broaden trigger-term coverage.

Consider stating the audience/condition (e.g., when Rube MCP / Composio is available) to sharpen the "when".

DimensionReasoningScore

Specificity

Names the Freshdesk domain and enumerates several concrete operations ("tickets, contacts, companies, notes, and replies via Rube MCP"), with only minor gaps in per-operation detail.

4 / 5

Completeness

Has a clear "what" but no explicit "Use when..." trigger clause; the "when" is only weakly implied, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("Freshdesk helpdesk operations", "tickets", "contacts", "companies", "replies") but lacks synonyms like "support" or "customer service".

4 / 5

Distinctiveness Conflict Risk

The Freshdesk-specific niche and Rube MCP framing give it distinct triggers with minimal overlap risk against other skills.

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.

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.