A registry of agent skills with test results.

Triage support tickets by pulling helpdesk context, searching issue trackers and knowledge bases in parallel, classifying the issue, and giving reps a recommended next action.

Triage one inbound support ticket end to end: classify it, draft a reply, run an escalation check, then send or escalate. Use when the user wants a structured, multi-step process to triage a single support ticket from raw inbound to a sent reply or a clean escalation. Do NOT use for a one-line canned answer or a quick classification that one atomic skill can answer.

Triage incoming support tickets by categorizing issues, assigning priority (P1-P4), and recommending routing. Use when a new ticket or customer issue comes in, when assessing severity, or when deciding which team should handle an issue.

고객 지원 티켓을 신속하게 분류하고 우선순위를 배정합니다. "이 문의를 어떻게 분류해야 하나요", "티켓 우선순위 정해줘", "고객 문의 긴급도 판단해줘"라고 요청할 때 사용하세요. 유형 분류(기술/결제/배송/불만), 긴급도 등급(P1~P4), 담당팀 배정, 에스컬레이션 판단을 지원합니다.

Triage incoming support tickets by categorizing issues, assigning priority (P1-P4), and recommending routing. Use when a new ticket or customer issue comes in, when assessing severity, or when deciding which team should handle an issue.

Triagem e priorização de ticket ou problema de suporte. Use ao receber um novo ticket que precisa de categorização, atribuição de prioridade P1-P4, decisão sobre qual time deve tratar, ou verificação de duplicidade antes de encaminhar. / 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.

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.

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.

First-response playbook for an inbound customer message — classifies the ticket, restates the issue, gathers missing context, and routes the reply.

고객 지원 티켓을 신속하게 분류하고 우선순위를 배정합니다. "이 문의를 어떻게 분류해야 하나요", "티켓 우선순위 정해줘", "고객 문의 긴급도 판단해줘"라고 요청할 때 사용하세요. 유형 분류(기술/결제/배송/불만), 긴급도 등급(P1~P4), 담당팀 배정, 에스컬레이션 판단을 지원합니다.

Pull open [Gorgias](https://composio.dev/toolkits/gorgias) support tickets and triage them by urgency, category, and sentiment

Triage support tickets with evidence and human-approved replies.

Use when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or escalation with a handoff packet. NOT the help-center article it links to (that is `technical-writing`), a win-back program (`retention`), or the auto-answer bot (`chatbot`).

Triage an order or account that tripped a risk check into one of hold, verify, release, or block, then pick the lowest-friction verification step and word any customer message so it never accuses them of fraud. Use when a suspected-fraud order needs a disposition and a customer-facing verification message. Do NOT use for routing a normal support ticket, writing a refund policy, or scoring risk from scratch.

Use when triaging an inbound abuse or terms-of-service report — turns the reported behavior into one severity tier and one bounded enforcement action (no-action, warn, restrict, suspend, ban, or escalate to Trust & Safety/Legal), applying proportionality and the mandatory-escalation carve-outs a model does not reach for on its own. Do NOT use for writing the notice sent to a user, routing a general support ticket, or drafting community guidelines.

Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.

Becomes a seasoned customer support specialist who triages issues, crafts empathetic responses, manages escalation workflows, and builds knowledge base articles for recurring problems. Use when the user needs help writing customer responses, classifying support tickets, designing escalation procedures, or creating FAQ content. Use for SLA-aware issue management and support team documentation. Do NOT use when the user needs engineering debugging, infrastructure troubleshooting, or direct code fix

[omh] Turn a support case into a clear customer reply, severity path, and owned next step. Use when the user says: support escalation, customer support reply, ticket triage, 고객 지원 에스컬레이션, 고객 답변 초안, 지원 티켓 분류.

Use when an issue, bug report, support thread, or user complaint arrives and needs triage before anyone fixes it - "triage this issue", "is this a duplicate", "can you reproduce this", "should we open an issue for this", "someone reported X". Not for fixing a confirmed bug (use refire).

Use when a deal closed or a user signed up and the first 30 days need an activation plan: sales→delivery handoff, one verifiable activation event, kickoff, and a 30/60/90 or day-0→14 plan with owners, dates and a measurable exit. NOT reactive ticket triage (that is `customer-support`), NOT renewals/churn past the onboarded gate (that is `retention`).