Zoho desk triage

Skill composio-community/support-skills/zoho-desk-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 zoho-desk-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 [Zoho Desk](https://composio.dev/toolkits/zoho-desk) and triage by priority and department

SKILL.md

1.5 KB, 350 tokens by cl100k_base, as published. Nobody here has run it

Zoho Desk Triage

You are a support triage specialist. Pull open tickets from Zoho Desk, classify them, and present a prioritized view.

Workflow

Step 1: Discover tools

Run composio search "list open tickets from Zoho Desk" "get Zoho Desk ticket details with threads" in Bash.

Step 2: Get tool schemas and fetch tickets

Run composio execute <SLUG> --get-schema in Bash (in parallel) for each of the returned Zoho Desk slugs, then run composio execute <LIST_TICKETS_SLUG> -d '{...open, sort by creation date...}' in Bash to fetch open tickets. If the CLI reports the toolkit is not connected, ask the user to run composio link zoho-desk and retry.

Step 3: Get details and classify

Run composio execute <GET_TICKET_SLUG> -d '{"ticket_id":"<ID>"}' in Bash as parallel calls for the top 15 tickets. Classify each:

Priority: P0 Critical, P1 High, P2 Medium, P3 Low Categories: Bug, Billing, Question, Feature Request, Account, Other

Step 4: Present

## Zoho Desk Triage Dashboard

### P0 - Critical (X tickets)
| # | Ticket ID | Subject | Category | Contact | Department | Age | Summary |
|---|-----------|---------|----------|---------|------------|-----|---------|

### P1 / P2 / P3
...

### Recommended Actions
- [Next steps for urgent tickets]

Gives 0 of the 12 instructions most debug triage skills give in 350 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-06

investigate root cause before proposing any fixin 102 of 839, across 65 files
read error messages completelyin 90 of 839, across 48 files
create a failing test case before fixingin 84 of 839, across 44 files
reproduce the issue consistentlyin 82 of 839, across 40 files
change one variable at a timein 82 of 839, across 42 files
check recent changesin 74 of 839, across 35 files
write the regression test before fixingin 74 of 839, across 36 files
fix the root cause not the symptomin 60 of 839, across 43 files
implement a single fix at a timein 59 of 839, across 20 files
trace data flow backward to the sourcein 50 of 839, across 20 files
remove all debug instrumentationin 49 of 839, across 13 files
form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

run composio search for Zoho Desk ticket tools
run composio execute to get tool schemas
run composio execute to fetch open tickets
ask the user to link the toolkit if disconnected
classify tickets by priority and category
present a prioritized ticket triage dashboard

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.