support-ticket-triage
Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.
npx skills add composio-community/awesome-codex-skills --skill support-ticket-triage --agent codex
Same command for any agent — swap --agent for claude-code, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Support Ticket Triage Standardize how to classify and respond to incoming tickets. ## Inputs to gather - Ticket text (include attachments/links), product area, customer plan/tier if known. - Desired outputs: category taxonomy, priority levels, SLA hints, tone/brand voice, whether to draft a reply. ## Workflow 1) Parse context: identify issue type, product surface, severity, customer impact, reproduction hints, and blockers. 2) Categorize: assign category and subcategory; set priority (e.g., P0–P3) with short justification. 3) Draft response (if asked): concise acknowledgment, empathy, restate issue, next steps, and ask for missing info; include reproduction checklist when uncertain. 4) Internal notes: suspected root cause, logs to pull, teams to loop, and tracking IDs to create/attach. 5) Output: tabular or bullet summary with `Category`, `Priority`, `Summary`, `Proposed Fix/Next Steps`, `Reply Draft`. ## Quality checks - Avoid promises; give ranges not exact ETAs unless provided. - Mask PII if copying to public channels. - If signal is weak, present 2–3 likely categories and what evidence would disambiguate.
- Inputs to gather
- Workflow
- Quality checks
What does the support-ticket-triage skill do?
Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.
How do I install it?
Run `npx skills add composio-community/awesome-codex-skills --skill support-ticket-triage --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From composio-community/awesome-codex-skills, a repository with 15,591 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.