ticket-triage
Triages and prioritizes a support ticket or customer issue as it comes in.
- Kind
- Skill
- Works with
- Claude Code
- Source
- Claude knowledge-work plugins @ 2574e29377c7
- Path
- customer-support/skills/ticket-triage/SKILL.md
- Jobs
- Planning
- Topics
- Customer support
Credit
- Made by
- anthropics
- Original
- github.com/anthropics/knowledge-work-plugins/blob/2574e29377c…
- License
- Apache-2.0
Listed by Skill Manifest; not made by us.
InstallInstall it from a plugin marketplace.
claude plugin install customer-support@knowledge-work-plugins
Install factsScanned 2 Nov 2026
- Adds
- .claude/skills/ticket-triage/ (the skill folder)
- 1 file(s) the skill refers to
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- 2574e29377c7
- Licence
- Apache-2.0
- Last activity
- 1 Nov 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- Only the main file is read; other files in the folder are not scanned
# /ticket-triage > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Categorize, prioritize, and route an incoming support ticket or customer issue. Produces a structured triage assessment with a suggested initial response. ## Usage ``` /ticket-triage <ticket text, customer message, or issue description> ``` Examples: - `/ticket-triage Customer says their dashboard has been showing a blank page since this morning` - `/ticket-triage "I was charged twice for my subscription this month"` - `/ticket-triage User can't connect their SSO — getting a 403 error on the callback URL` - `/ticket-triage Feature request: they want to export reports as PDF` ## Workflow ### 1. Parse the Issue Read the input and extract: - **Core problem**: What is the customer actually experiencing? - **Symptoms**: What specific behavior or error are they seeing? - **Customer context**: Who is this? Any account details, plan level, or history available? - **Urgency signals**: Are they blocked? Is this production? How many users affected? - **Emotional state**: Frustrated, confused, matter-of-fact, escalating? …