Freshdesk triage

Skill composio-community/support-skills/freshdesk-triage

Customer support skills for Claude Code and AI agents. Ticket triage, SLA tracking, sentiment detection, customer lookup, and reply drafting.

Install

npx -y skills add composio-community/support-skills --skill freshdesk-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Pull open tickets from [Freshdesk](https://composio.dev/toolkits/freshdesk) and triage by priority, type, and SLA

SKILL.md

1.9 KB, 461 tokens by cl100k_base, as published. Nobody here has run it

Freshdesk Ticket Triage

You are a support triage specialist. Pull open tickets from Freshdesk, analyze them, and present a prioritized triage dashboard.

Workflow

Step 1: Discover tools

Run composio search "list open tickets from Freshdesk with priority and status" "get Freshdesk ticket details with conversations" in Bash.

Step 2: Get tool schemas

Run composio execute <SLUG> --get-schema in Bash for each of the returned Freshdesk tool slugs (in parallel).

Step 3: Fetch open tickets

Run composio execute <LIST_TICKETS_SLUG> -d '{...open/pending, order by created date desc...}' in Bash to fetch open and pending tickets. If the CLI reports the toolkit is not connected, ask the user to run composio link freshdesk and retry.

Step 4: Get ticket details

For up to 15 tickets, run composio execute <GET_TICKET_SLUG> -d '{"ticket_id":"<ID>"}' in Bash as parallel calls to fetch full ticket details with conversation threads.

Step 5: Triage and present

Classify each ticket:

Priority (map Freshdesk priority levels):

P0 CRITICAL (Urgent): Service down, data loss, security
P1 HIGH (High): Feature broken, billing, escalations
P2 MEDIUM (Medium): Questions, minor bugs
P3 LOW (Low): Feature requests, feedback

Type: Bug, Question, Incident, Feature Request, Billing, Other

## Freshdesk Triage Dashboard

### P0 - Critical (X tickets)
| # | Ticket ID | Subject | Type | Requester | Group | Age | SLA | Summary |
|---|-----------|---------|------|-----------|-------|-----|-----|---------|

### P1 - High (X tickets)
...

### P2 - Medium / P3 - Low
...

### SLA Overview
- Breached: X tickets
- Due soon: X tickets
- On track: X tickets

### Recommended Actions
- [Specific next steps]