freshservice-automation

Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.

Install with Tessl CLI

npx tessl i github:Lingjie-chen/MT5 --skill freshservice-automation

What are skills?

1.43x

Quality

65%

Does it follow best practices?

Impact

92%

1.43x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/freshservice-automation/SKILL.md

SKILL.md

Review

Evals

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description effectively communicates specific capabilities for Freshservice automation with concrete actions and clear tooling context. Its main weakness is the absence of an explicit 'Use when...' clause and limited trigger term coverage for how users naturally describe IT service management needs.

Suggestions

Add a 'Use when...' clause with trigger terms like 'when users mention Freshservice, helpdesk tickets, IT support requests, or incident management'

Include common user-facing synonyms such as 'helpdesk', 'support tickets', 'IT incidents', 'service desk' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'create/update tickets, bulk operations, service requests, and outbound emails'. Also includes the actionable guidance to 'search tools first for current schemas'.	3 / 3
Completeness	Clearly answers 'what' (automate Freshservice tasks with specific actions listed), but lacks an explicit 'Use when...' clause. The 'when' is only implied through the domain context.	2 / 3
Trigger Term Quality	Includes relevant terms like 'Freshservice', 'ITSM', 'tickets', 'service requests', but missing common variations users might say like 'helpdesk', 'IT support', 'incident', 'ticket system', or 'support ticket'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with specific product names (Freshservice, Rube MCP, Composio) and ITSM domain focus. Unlikely to conflict with other skills due to the specific tooling and platform references.	3 / 3
	Total	10 / 12 Passed

Implementation

62%

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

This skill provides comprehensive coverage of Freshservice operations with well-structured workflows and helpful pitfall documentation. However, it suffers from redundancy (duplicate reference tables), lacks concrete executable examples of MCP tool invocations, and could benefit from splitting detailed reference material into separate files to improve the overview-to-detail ratio.

Suggestions

Add concrete, copy-paste ready examples showing actual MCP tool call syntax with realistic payloads (e.g., JSON for RUBE_SEARCH_TOOLS and FRESHSERVICE_CREATE_TICKET calls)

Consolidate the status/priority code references into a single location and remove duplicates from individual workflow sections

Move detailed parameter documentation and reference tables to a separate REFERENCE.md file, keeping only essential quick-start info in the main skill

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy (status/priority codes appear in both workflow sections AND as separate reference tables, pitfalls are repeated across sections). The Quick Reference table at the end duplicates information already covered in detail above.	2 / 3
Actionability	Provides clear tool names and parameter lists, but lacks executable code examples showing actual MCP tool calls with concrete payloads. The 'Finding Tickets by Date Range' example uses pseudocode-style numbered steps rather than actual invocation syntax.	2 / 3
Workflow Clarity	Each workflow has clear tool sequences marked as [Required]/[Optional]/[Prerequisite], explicit parameter documentation, and detailed pitfalls sections. The bulk update workflow correctly shows the prerequisite step of listing tickets first.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is in a single monolithic file. The extensive parameter documentation and reference tables could be split into separate files (e.g., REFERENCE.md for codes, WORKFLOWS.md for detailed workflows) with the main skill providing a concise overview.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Reviewed: 1 day 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.