Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill freshdesk-automation78
Quality
72%
Does it follow best practices?
Impact
82%
1.41xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/freshdesk-automation/SKILL.mdTicket creation with ID resolution and correct parameter types
RUBE_SEARCH_TOOLS first
0%
0%
Connection check
0%
100%
Requester ID resolution
66%
100%
Contact search query format
0%
100%
Integer priority values
100%
100%
Integer status values
0%
100%
cf_ prefix for custom fields
0%
100%
HTML description support
100%
100%
Requester identifier present
100%
100%
Correct tool for creation
100%
100%
Without context: $0.5419 · 2m 36s · 23 turns · 27 in / 9,319 out tokens
With context: $0.4419 · 1m 39s · 19 turns · 181 in / 5,920 out tokens
Advanced ticket search query syntax and filtering
GET_SEARCH for advanced query
100%
100%
Double-quoted query string
100%
100%
Date format YYYY-MM-DD
100%
100%
null keyword for unassigned
0%
100%
Integer status/priority in query
100%
100%
Pagination awareness
100%
100%
Correct search limits noted
0%
100%
RUBE_SEARCH_TOOLS first
0%
100%
AND operator for compound query
100%
100%
Does not use LIST_ALL_TICKETS for filtering
100%
100%
Without context: $0.2285 · 1m 5s · 10 turns · 15 in / 3,880 out tokens
With context: $0.4211 · 1m 30s · 20 turns · 306 in / 5,455 out tokens
Company onboarding, notes visibility, and company vs ticket custom field prefixes
Valid account_tier value
100%
100%
Valid health_score value
100%
100%
domains field for auto-association
100%
100%
No cf_ prefix on company fields
100%
100%
cf_ prefix on ticket custom fields
100%
100%
Public note uses private: false
0%
0%
Internal note uses private: true
75%
100%
Contact search before ticket creation
0%
0%
Contact search query format
0%
0%
RUBE connection setup
0%
0%
Without context: $0.2183 · 1m 21s · 11 turns · 16 in / 4,659 out tokens
With context: $0.3829 · 1m 52s · 13 turns · 16 in / 6,888 out tokens
Table of Contents
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.