cs-ticket-triage

Categorize support tickets, assign P1–P4 priority, and recommend routing.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill cs-ticket-triage-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cs-ticket-triage
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/cs-ticket-triage
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill cs-ticket-triage-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly categorize, prioritize, and route incoming support or customer-issue tickets so they don’t get stuck in inbox triage or sent to the wrong area.

Core Features & Use Cases

  • Structured problem parsing: Extracts the central problem, symptoms, customer context, urgency signals, and emotional state from the ticket text.
  • Priority and routing guidance (P1–P4): Assigns a primary/secondary category, determines impact, and recommends which team or queue should handle it.
  • Duplicate and known-issue checks: Instructs verification against internal sources (e.g., CRM, Notion MCP, Linear/Linear MCP) before creating new work.
  • Ready-to-send triage output: Produces a consistent triage evaluation including internal notes and a suggested initial customer response.

Quick Start

Use the cs-ticket-triage skill by writing: /cs-ticket-triage "Fui cobrado duas vezes na minha assinatura este mês".

Frequently Asked Questions about cs-ticket-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage and prioritize inbound support tickets automatically?

Ticket triage for customer issues works by extracting the central problem, symptoms, and urgency signals from message text, then assigning a priority level and suggesting which internal team should handle the incident.

How do I detect duplicate support tickets before creating new work items?

Duplicate detection during ticket triage involves verifying the inbound issue against internal sources like CRM or issue trackers before creating new tasks, ensuring known incidents are consolidated rather than duplicated.

How do I assign P1 to P4 priority levels to customer support issues?

Assigning P1–P4 priority levels to customer issues requires evaluating the extracted problem context, impact, and urgency signals from the ticket text to justify the severity and determine the correct routing path.

Can I generate a ready-to-send initial customer response during ticket triage?

Yes, ticket triage processing can produce a standardized evaluation that includes internal notes alongside a suggested initial customer response, enabling immediate replies while the issue waits for internal handoff.

Does ticket triage work with issue trackers like Linear or Notion for known-issue verification?

Ticket triage instructs verification against integrated internal sources such as Linear, Notion, or CRM tools to check for known issues before routing, ensuring the triage report reflects existing incident documentation.