C✳CODEZ.WIN
🌐 English

Localized reading guide

ticket-triagePurpose, usage and source

Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.

Source retrieved:

Source repository
anthropics/knowledge-work-plugins
SKILL.md
customer-support/skills/ticket-triage/SKILL.md
Repository stars
34,049
Repository updated
2026-10-30
Categories
Business
Last collected

License: License file needs review

Source SKILL.md

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.

How the upstream workflow works

Usage

/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

Upstream passage · L13 ↗

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?"

Upstream passage · L93 ↗

/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.

Upstream passage · L7 ↗
Upstream passage · ↗
/ticket-triage <ticket text, customer message, or issue description>

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d
Source SHA-256
d0e5e95443e358ad2a74811b196071d10807ca95aa20351ab5760feeecee1294
Back to the full Skill catalog