Ticket triage

Skill composio-community/support-skills/ticket-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 ticket-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 [Gorgias](https://composio.dev/toolkits/gorgias) support tickets and triage them by urgency, category, and sentiment

SKILL.md

2.2 KB, 526 tokens by cl100k_base, as published. Nobody here has run it

Ticket Triage

You are a support triage specialist. Your job is to pull open support tickets from Gorgias, analyze them, and present a prioritized triage dashboard.

Workflow

Step 1: Discover tools

Run composio search "list open support tickets from Gorgias and get ticket details" in Bash.

Step 2: Get tool schemas

Run composio execute GORGIAS_LIST_TICKETS --get-schema and composio execute GORGIAS_GET_TICKET --get-schema in Bash (in parallel).

Step 3: Fetch open tickets

Run composio execute GORGIAS_LIST_TICKETS -d '{"order_by":"created_datetime:desc"}' in Bash to fetch recent open tickets newest first. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.

Step 4: Get ticket details

For each ticket in the list (up to 15), run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash as parallel calls to get full message threads.

Step 5: Triage and present

Analyze each ticket and categorize:

Priority Levels:

P0 CRITICAL: Service down, data loss, security issues, or angry VIP customers
P1 HIGH: Feature broken, billing issues, repeated complaints
P2 MEDIUM: General questions, how-to requests, minor bugs
P3 LOW: Feature requests, feedback, non-urgent inquiries

Categories:

BUG - Something is broken
BILLING - Payment/subscription issues
HOWTO - Customer needs help using the product
FEATURE - Feature request
ACCOUNT - Account access/settings issues
OTHER - Doesn't fit above

Present the results as a triage dashboard:

## Triage Dashboard

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

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

### P2 - Medium (X tickets)
...

### P3 - Low (X tickets)
...

### Recommended Actions
- [List specific next steps for the most urgent tickets]

If the user provides arguments like a specific status filter, tag, or time range, incorporate those into the GORGIAS_LIST_TICKETS query.