Ticket Triage
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The ticket-triage skill provides a structured framework for processing incoming customer support requests. It guides the agent through parsing the issue, identifying core problems and urgency, checking for duplicates or known issues, and determining the appropriate routing. The output is a standardized assessment that includes a summary, priority level, routing recommendation, and a draft initial response, ensuring consistent and efficient support operations.
What it does
- Parses raw customer messages to extract core problems and symptoms.
- Assigns a primary and secondary category based on a defined taxonomy.
- Determines ticket priority (P1-P4) based on impact and urgency.
- Checks for duplicates and known issues to prevent redundant work.
- Recommends the appropriate team or queue for routing.
- Generates a draft initial response and internal notes for the support agent.
When to use it
- When a new support ticket or customer issue arrives.
- When you need to ensure consistent categorization and prioritization across a support team.
- When you want to quickly identify if an issue is a known bug or a duplicate.
- When you need to draft a professional, context-aware initial response to a customer.
Advantages
- Reduces manual effort in assessing and routing support tickets.
- Ensures consistent SLA adherence through standardized priority frameworks.
- Prevents duplicate investigations by checking known issues.
- Provides clear, actionable internal notes for the next agent in the workflow.
Usage examples
- “ticket-triage Customer says their dashboard has been showing a blank page since this morning”
- The agent receives a triage report identifying this as a P2/P3 performance or bug issue, with a suggested response acknowledging the disruption and a recommendation to route to Tier 2 support.
- “ticket-triage I was charged twice for my subscription this month”
- The agent receives a triage report categorized as Billing, with a high-priority recommendation and a draft response template for financial inquiries.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/ticket-triage/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip ticket-triage.zip -d .agents/skills
Documentation by Anthropic
/ticket-triage
If you see unfamiliar placeholders or need to check which tools are connected, see 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?
2. Categorize and Prioritize
Using the category taxonomy and priority framework below:
Assign a primary category (bug, how-to, feature request, billing, account, integration, security, data, performance) and an optional secondary category
Assign a priority (P1–P4) based on impact and urgency
Identify the product area the issue maps to
3. Check for Duplicates and Known Issues
Before routing, check available sources:
~~support platform: Search for similar open or recently resolved tickets
~~knowledge base: Check for known issues or existing documentation
~~project tracker: Check if there's an existing bug report or feature request
Apply the duplicate detection process below.
4. Determine Routing
Using the routing rules below, recommend which team or queue should handle this based on category and complexity.
5. Generate Triage Output
## Triage: [One-line issue summary]
**Category:** [Primary] / [Secondary if applicable]
**Priority:** [P1-P4] — [Brief justification]
**Product area:** [Area/team]
### Issue Summary
[2-3 sentence summary of what the customer is experiencing]
### Key Details
- **Customer:** [Name/account if known]
- **Impact:** [Who and what is affected]
- **Workaround:** [Available / Not available / Unknown]
- **Related tickets:** [Links to similar issues if found]
- **Known issue:** [Yes — link / No / Checking]
### Routing Recommendation
**Route to:** [Team or queue]
**Why:** [Brief reasoning]
### Suggested Initial Response
[Draft first response to the customer — acknowledge the issue,
set expectations, provide workaround if available.
Use the auto-response templates below as a starting point.]
### Internal Notes
- [Any additional context for the agent picking this up]
- [Reproduction hints if it's a bug]
- [Escalation triggers to watch for]6. Offer Next Steps
After presenting the triage:
"Want me to draft a full response to the customer?"
"Should I search for more context on this issue?"
"Want me to check if this is a known bug in the tracker?"
"Should I escalate this? I can package it with /customer-escalation."
Category Taxonomy
Assign every ticket a primary category and optionally a secondary category:
| Category | Description | Signal Words |
|---|---|---|
| Bug | Product is behaving incorrectly or unexpectedly | Error, broken, crash, not working, unexpected, wrong, failing |
| How-to | Customer needs guidance on using the product | How do I, can I, where is, setting up, configure, help with |
| Feature request | Customer wants a capability that doesn't exist | Would be great if, wish I could, any plans to, requesting |
| Billing | Payment, subscription, invoice, or pricing issues | Charge, invoice, payment, subscription, refund, upgrade, downgrade |
| Account | Account access, permissions, settings, or user management | Login, password, access, permission, SSO, locked out, can't sign in |
| Integration | Issues connecting to third-party tools or APIs | API, webhook, integration, connect, OAuth, sync, third-party |
| Security | Security concerns, data access, or compliance questions | Data breach, unauthorized, compliance, GDPR, SOC 2, vulnerability |
| Data | Data quality, migration, import/export issues | Missing data, export, import, migration, incorrect data, duplicates |
| Performance | Speed, reliability, or availability issues | Slow, timeout, latency, down, unavailable, degraded |
Category Determination Tips
If the customer reports both a bug and a feature request, the bug is primary
If they can't log in due to a bug, category is Bug (not Account) — root cause drives the category
"It used to work and now it doesn't" = Bug
"I want it to work differently" = Feature request
"How do I make it work?" = How-to
When in doubt, lean toward Bug — it's better to investigate than dismiss
Priority Framework
P1 — Critical
Criteria: Production system down, data loss or corruption, security breach, all or most users affected.
The customer cannot use the product at all
Data is being lost, corrupted, or exposed
A security incident is in progress
The issue is worsening or expanding in scope
SLA expectation: Respond within 1 hour. Continuous work until resolved or mitigated. Updates every 1-2 hours.
P2 — High
Criteria: Major feature broken, significant workflow blocked, many users affected, no workaround.
A core workflow is broken but the product is partially usable
Multiple users are affected or a key account is impacted
The issue is blocking time-sensitive work
No reasonable workaround exists
SLA expectation: Respond within 4 hours. Active investigation same day. Updates every 4 hours.
P3 — Medium
Criteria: Feature partially broken, workaround available, single user or small team affected.
A feature isn't working correctly but a workaround exists
The issue is inconvenient but not blocking critical work
A single user or small team is affected
The customer is not escalating urgently
SLA expectation: Respond within 1 business day. Resolution or update within 3 business days.
P4 — Low
Criteria: Minor inconvenience, cosmetic issue, general question, feature request.
Cosmetic or UI issues that don't affect functionality
Feature requests and enhancement ideas
General questions or how-to inquiries
Issues with simple, documented solutions
SLA expectation: Respond within 2 business days. Resolution at normal pace.
Priority Escalation Triggers
Automatically bump priority up when:
Customer has been waiting longer than the SLA allows
Multiple customers report the same issue (pattern detected)
The customer explicitly escalates or mentions executive involvement
A workaround that was in place stops working
The issue expands in scope (more users, more data, new symptoms)
Routing Rules
Route tickets based on category and complexity:
| Route to | When |
|---|---|
| Tier 1 (frontline support) | How-to questions, known issues with documented solutions, billing inquiries, password resets |
| Tier 2 (senior support) | Bugs requiring investigation, complex configuration, integration troubleshooting, account issues |
| Engineering | Confirmed bugs needing code fixes, infrastructure issues, performance degradation |
| Product | Feature requests with significant demand, design decisions, workflow gaps |
| Security | Data access concerns, vulnerability reports, compliance questions |
| Billing/Finance | Refund requests, contract disputes, complex billing adjustments |
Duplicate Detection
Before creating a new ticket or routing, check for duplicates:
Search by symptom: Look for tickets with similar error messages or descriptions
Search by customer: Check if this customer has an open ticket for the same issue
Search by product area: Look for recent tickets in the same feature area
Check known issues: Compare against documented known issues
If a duplicate is found:
Link the new ticket to the existing one
Notify the customer that this is a known issue being tracked
Add any new information from the new report to the existing ticket
Bump priority if the new report adds urgency (more customers affected, etc.)
Auto-Response Templates by Category
Bug — Initial Response
Thank you for reporting this. I can see how [specific impact]
would be disruptive for your work.
I've logged this as a [priority] issue and our team is
investigating. [If workaround exists: "In the meantime, you
can [workaround]."]
I'll update you within [SLA timeframe] with what we find.How-to — Initial Response
Great question! [Direct answer or link to documentation]
[If more complex: "Let me walk you through the steps:"]
[Steps or guidance]
Let me know if that helps, or if you have any follow-up
questions.Feature Request — Initial Response
Thank you for this suggestion — I can see why [capability]
would be valuable for your workflow.
I've documented this and shared it with our product team.
While I can't commit to a specific timeline, your feedback
directly informs our roadmap priorities.
[If alternative exists: "In the meantime, you might find
[alternative] helpful for achieving something similar."]Billing — Initial Response
I understand billing issues need prompt attention. Let me
look into this for you.
[If straightforward: resolution details]
[If complex: "I'm reviewing your account now and will have
an answer for you within [timeframe]."]Security — Initial Response
Thank you for flagging this — we take security concerns
seriously and are reviewing this immediately.
I've escalated this to our security team for investigation.
We'll follow up with you within [timeframe] with our findings.
[If action is needed: "In the meantime, we recommend
[protective action]."]Triage Best Practices
Read the full ticket before categorizing — context in later messages often changes the assessment
Categorize by root cause, not just the symptom described
When in doubt on priority, err on the side of higher — it's easier to de-escalate than to recover from a missed SLA
Always check for duplicates and known issues before routing
Write internal notes that help the next person pick up context quickly
Include what you've already checked or ruled out to avoid duplicate investigation
Flag patterns — if you're seeing the same issue repeatedly, escalate the pattern even if individual tickets are low priority
Files
- ATTRIBUTION.mdAdded by AutoGineer954 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md11.0 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Claude Code frontmatter
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · customer-support/skills/ticket-triage · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from customer-support/LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download ticket-triage.zip