Zendesk triage

Skill composio-community/support-skills/zendesk-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 zendesk-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 [Zendesk](https://composio.dev/toolkits/zendesk) and triage by priority, category, and SLA status

SKILL.md

1.9 KB, as published. Nobody here has run it

Zendesk Ticket Triage

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

Workflow

Step 1: Discover tools

Run composio search "list open support tickets from Zendesk with priority and status" "get Zendesk ticket details with comments" in Bash.

Step 2: Get tool schemas

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

Step 3: Fetch open tickets

Run composio execute <LIST_TICKETS_SLUG> -d '{...open/pending, newest first...}' in Bash to fetch recent open/pending tickets. Paginate if needed. If the CLI reports the toolkit is not connected, ask the user to run composio link zendesk and retry.

Step 4: Get ticket details

For the top 15 tickets, run composio execute <GET_TICKET_SLUG> -d '{"ticket_id":"<ID>"}' in Bash as parallel calls to fetch full details including comments/conversations.

Step 5: Triage and present

Classify each ticket:

Priority:

P0 CRITICAL: Service outage, data loss, security, VIP escalations
P1 HIGH: Feature broken, billing disputes, repeated contacts
P2 MEDIUM: General questions, minor bugs, how-to requests
P3 LOW: Feature requests, feedback, non-urgent inquiries

Categories: BUG, BILLING, HOWTO, FEATURE, ACCOUNT, INTEGRATION, OTHER

## Zendesk Triage Dashboard

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

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

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

### Recommended Actions
- [Specific next steps for urgent tickets]