Siftrank
noperator/siftrank
Find needles in haystacks with SiftRank. An agent skill from noperator/siftrank.
Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses.
Install Ticket Triage
$ npx skills add seb1n/awesome-ai-agent-skills --skill ticket-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills ticket-triage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/customer-success/ticket-triage .claude/skills/ticket-triage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ticket-triage" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/ticket-triage into .claude/skills/ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-triage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/ticket-triageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add seb1n/awesome-ai-agent-skills --skill ticket-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills ticket-triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/customer-success/ticket-triage .agents/skills/ticket-triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ticket-triage" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/ticket-triage into .agents/skills/ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-triage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seb1n/awesome-ai-agent-skills --skill ticket-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills ticket-triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/customer-success/ticket-triage .cursor/skills/ticket-triage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ticket-triage" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/ticket-triage into .cursor/skills/ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-triage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/seb1n/awesome-ai-agent-skills.git --path customer-success/ticket-triage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add seb1n/awesome-ai-agent-skills --skill ticket-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills ticket-triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/customer-success/ticket-triage .gemini/skills/ticket-triage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ticket-triage" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/ticket-triage into .gemini/skills/ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-triage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install seb1n/awesome-ai-agent-skills ticket-triageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add seb1n/awesome-ai-agent-skills --skill ticket-triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/customer-success/ticket-triage .github/skills/ticket-triage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ticket-triage" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/ticket-triage into .github/skills/ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-triage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seb1n/awesome-ai-agent-skills --skill ticket-triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills ticket-triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/customer-success/ticket-triage .opencode/skills/ticket-triage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ticket-triage" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/customer-success/ticket-triage into .opencode/skills/ticket-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ticket-triage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ticket-triage- GitHub stars
- 206
- Token cost
- ~1.9k tokens
- SKILL.md length
- 991 words
- Files
- 1
- Skills in repo
- 101
- Repo updated
- First seen
- Licence
- MIT
At a glance
Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses.
- Works in 6 steps: Receive and parse the ticket — Ingest… → Extract intent and entities — Analyze… → Classify into category — Map the… → …
- The user requests ticket triage
- SKILL.md covers Workflow, Usage, Examples and Best Practices, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ticket Triage is an agent skill from seb1n/awesome-ai-agent-skills. Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses. Use when the user requests ticket triage or provides relevant inputs for this workflow.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Customer support. The repository describes itself as: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.
When your agent uses it
- The user requests ticket triage
- Provides relevant inputs for this workflow
Example prompts
- “/ticket-triage”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Receive and parse the ticket — Ingest the raw ticket including subject, body, customer metadata (account tier, plan, tenure), and any…
- Extract intent and entities — Analyze the cleaned ticket text to determine the customer's primary intent (reporting a bug, asking a…
- Classify into category — Map the extracted intent to one of the standard categories: billing (charges, invoices, refunds, plan changes)…
- Assign priority using impact and urgency — Score priority from P0 to P3 using a matrix. P0: production outage or data loss affecting…
- Route to the appropriate team — Map the category and priority to a team: billing tickets go to the Finance Support queue, bugs route to…
- Generate initial response — Draft a first reply that acknowledges the issue, sets expectations on response time based on priority…
What it can do on your machine
Read from SKILL.md and the folder at commit 75865a5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ticket Triage loads about 1.9k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 991 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 991 words, ~1,857 tokens.
Download SKILL.mdSave it as
.claude/skills/ticket-triage/SKILL.md (or your agent's skills folder).- name
- ticket-triage
- description
- Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses. Use when the user requests ticket triage or provides relevant inputs for this workflow.
- license
- MIT
- metadata.author
- community
- metadata.version
- 1.0
Ticket Triage
Automatically classify, prioritize, and route incoming customer support tickets to the right team with a suggested first response. This skill processes raw ticket text, identifies the customer's intent and key entities (product area, account tier, error codes), assigns a category and priority level, then routes to the appropriate team while drafting an empathetic initial reply.
Workflow
Receive and parse the ticket — Ingest the raw ticket including subject, body, customer metadata (account tier, plan, tenure), and any attachments or screenshots. Normalize the text by stripping signatures, quoted replies, and boilerplate. Extract structured fields like order IDs, error codes, and URLs.
Extract intent and entities — Analyze the cleaned ticket text to determine the customer's primary intent (reporting a bug, asking a question, requesting a feature, disputing a charge). Identify named entities such as product names, feature areas, API endpoints, and specific error messages. Tag sentiment as positive, neutral, negative, or urgent.
Classify into category — Map the extracted intent to one of the standard categories:
billing(charges, invoices, refunds, plan changes),bug(errors, crashes, unexpected behavior),feature-request(new functionality, integrations, enhancements), orhow-to(setup, configuration, usage questions). If a ticket spans multiple categories, assign the primary and note secondaries.Assign priority using impact and urgency — Score priority from P0 to P3 using a matrix. P0: production outage or data loss affecting multiple customers. P1: major functionality broken for a single enterprise account. P2: degraded experience with a workaround available. P3: general questions or minor cosmetic issues. Factor in account tier — enterprise accounts get a one-level priority bump.
Route to the appropriate team — Map the category and priority to a team: billing tickets go to the Finance Support queue, bugs route to Engineering Triage (P0/P1) or Product Support (P2/P3), feature requests go to Product Management, and how-to tickets go to Customer Education. Attach relevant context and internal notes.
Generate initial response — Draft a first reply that acknowledges the issue, sets expectations on response time based on priority, includes any immediate self-serve resources (KB articles, status page links), and asks clarifying questions if the ticket is ambiguous. Match tone to sentiment — empathetic for frustrated customers, concise for technical users.
Usage
Provide a support ticket (or batch of tickets) and ask the agent to triage them. Include customer metadata when available for better priority assignment.
Triage these support tickets and output a classification table with category,
priority, assigned team, and a draft first response for each.Examples
Example 1: Batch triage of 5 tickets
Input: 5 support tickets from the past hour.
Output:
| # | Subject | Category | Priority | Team | Suggested Response |
|---|---|---|---|---|---|
| 1 | "Can't login since this morning" | bug | P1 | Engineering Triage | "Hi Sarah, I'm sorry you're locked out. I've escalated this to our engineering team and they're investigating now. As a workaround, try clearing your browser cache or using an incognito window. We'll update you within 2 hours." |
| 2 | "How do I export data to CSV?" | how-to | P3 | Customer Education | "Hi James, great question! You can export to CSV from Settings → Data → Export. Here's our step-by-step guide: [link]. Let me know if you hit any snags." |
| 3 | "Charged twice for March" | billing | P2 | Finance Support | "Hi Priya, I apologize for the duplicate charge. I've flagged your account for review and our billing team will process the refund within 3-5 business days. You'll receive a confirmation email." |
| 4 | "Would love Slack integration" | feature-request | P3 | Product Management | "Hi Tom, thanks for the suggestion! A Slack integration is something we're hearing a lot about. I've added your vote to our feature tracker and will notify you if it moves to our roadmap." |
| 5 | "Dashboard is down for our entire org" | bug | P0 | Engineering Triage | "Hi Alex, this is our top priority right now. Our on-call engineering team has been paged and is actively investigating. Check status.example.com for live updates. I'll follow up within 30 minutes with a status." |
Show full SKILL.md (367 more words)Show less
Example 2: Urgent production outage escalation
Input: "URGENT: All API requests returning 500 errors since 14:32 UTC. Affecting our production environment. 50,000+ end users impacted. Enterprise plan."
Output:
- Category: bug
- Priority: P0 (production outage, multiple end users, enterprise account)
- Team: Engineering Triage → Immediate page to on-call SRE
- Escalation path: Auto-notify VP Engineering, assigned CSM, and account executive
- SLA clock: 15-minute first response, 1-hour status update cadence
- Draft response: "Hi — this is marked as our highest priority. Our SRE team has been paged and is investigating the 500 errors starting at 14:32 UTC. We'll provide our first status update within 15 minutes. For real-time updates, monitor status.example.com. I'm your point of contact until this is resolved."
Best Practices
- Always extract customer account tier before assigning priority — enterprise customers with production impact should never be lower than P1.
- Use the secondary category tag for tickets that span billing and bug (e.g., "I was charged for a feature that doesn't work") to ensure both teams have visibility.
- Pre-populate the initial response with relevant KB article links by matching extracted entities against your knowledge base index.
- Re-triage tickets that receive a customer reply within 1 hour, as additional context often changes the category or priority.
- Log triage decisions with reasoning so the model can be fine-tuned on corrections from human reviewers.
- Set up auto-escalation rules: any P0 not acknowledged within 15 minutes should page the on-call manager.
Edge Cases
- Multi-intent tickets — A single ticket contains both a bug report and a billing dispute. Classify under the higher-priority intent and create a linked ticket for the secondary issue.
- Spam or vendor outreach — Tickets that are marketing emails or vendor pitches routed through support. Classify as
spam, auto-close, and exclude from SLA metrics. - Non-English tickets — Detect the language, translate for triage, and route to the appropriate language-specific support queue if one exists. Note the original language in internal metadata.
- Repeat tickets from the same customer — Detect duplicate or follow-up tickets within a 24-hour window. Merge into the existing thread rather than creating a new triage entry.
- Tickets with only attachments — When the body is empty but a screenshot or log file is attached, flag for manual review rather than auto-classifying with low confidence.
© seb1n, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in customer-success/ticket-triage of seb1n/awesome-ai-agent-skills.
Open the folder on GitHubat commit 75865a5
Compare with similar skills
Ticket Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ticket Triage this skillseb1n/awesome-ai-agent-skills | 206 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Siftranknoperator/siftrank | 225 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Supporthaacked/dotfiles | 134 | — | ~2.9k | Automated safety check: Pass | None | |
| Customer Support Agentmastra-ai/mastra | 29k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Add Agent Adaptersafedep/gryph | 172 | — | ~679 | Automated safety check: Pass | Apache-2.0 | |
| Agent Support Matrixjazzyalex/agent-sessions | 895 | — | ~587 | Automated safety check: Pass | MIT |
Similar skills
Support
haacked/dotfiles
Support hero workflow — start a ticket investigation with auto-organized notes, find existing notes, or generate the weekly highlights log.
Customer Support Agent
mastra-ai/mastra
Authoring playbook for building agents that triage and reply to customer messages — support tickets, email inquiries, chat questions, refund requests, or product issues.
Add Agent Adapter
safedep/gryph
A skill your agent uses when adding support for a new AI coding agent to Gryph, or when changing how an existing agent adapter is wired.
Agent Support Matrix
jazzyalex/agent-sessions
Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility.
Company Brain Company QA
topoteretes/cognee
Build one company memory from a SQL database, a support ticket export and a folder of documents, linked into one graph by cognee, then answer questions that need several of those sources together.
More from seb1n/awesome-ai-agent-skills
All 101 skills in this repoAgent Red Teaming
seb1n/awesome-ai-agent-skills
Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.
Eu AI Act Readiness
seb1n/awesome-ai-agent-skills
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…
Human In The Loop
seb1n/awesome-ai-agent-skills
Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.
MCP Server Building
seb1n/awesome-ai-agent-skills
Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.
PDF Processing
seb1n/awesome-ai-agent-skills
Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.
Skill Supply Chain Audit
seb1n/awesome-ai-agent-skills
Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.
Related
Categories
Questions about Ticket Triage
What does Ticket Triage do?
Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses. Ticket Triage is an agent skill from seb1n/awesome-ai-agent-skills. Classify, prioritize, and route incoming support tickets by extracting intent and entities, assigning severity, and generating initial responses.
When should I use Ticket Triage?
Ticket Triage fits situations like: the user requests ticket triage; provides relevant inputs for this workflow.
How do I install Ticket Triage in Claude Code?
Run `npx skills add seb1n/awesome-ai-agent-skills --skill ticket-triage -a claude-code`. Or copy the skill folder (customer-success/ticket-triage in seb1n/awesome-ai-agent-skills) into .claude/skills/ticket-triage in your project. Claude Code loads it when a task matches its description.
How do I install Ticket Triage in Codex?
Run `npx skills add seb1n/awesome-ai-agent-skills --skill ticket-triage -a codex`. Or copy the skill folder (customer-success/ticket-triage in seb1n/awesome-ai-agent-skills) into .agents/skills/ticket-triage in your project. Codex loads it when a task matches its description.
Can I use Ticket Triage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seb1n/awesome-ai-agent-skills --skill ticket-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ticket-triage, .gemini/skills/ticket-triage, .github/skills/ticket-triage and .opencode/skills/ticket-triage in your project.
What does Ticket Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Ticket Triage is instructions for the agent only.
Does Ticket Triage access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ticket Triage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ticket Triage use?
Ticket Triage is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ticket Triage use?
About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ticket Triage?
Skills that share tags, products or a category with Ticket Triage: Siftrank (noperator/siftrank, 225 stars), Support (haacked/dotfiles, 134 stars), Customer Support Agent (mastra-ai/mastra, 29k stars) and Add Agent Adapter (safedep/gryph, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ticket Triage?
seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 101 skills in this directory. The repository was last updated on August 9, 2026.
Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.