zendesk-triage

Ranks Zendesk ticket batches by priority with per-ticket rationales and drafted next actions.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/JYeswak/grok_bot_playground --skill zendesk-triage-jyeswak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zendesk-triage
Source: https://github.com/JYeswak/grok_bot_playground/tree/main/plugin/skills/zendesk-triage
Command: npx skills add https://github.com/JYeswak/grok_bot_playground --skill zendesk-triage-jyeswak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Support teams facing an untriaged Zendesk queue need a defensible priority order and a next step for every ticket, without risking premature replies or status changes. This Skill turns a raw ticket batch into a ranked triage with a written rationale per ticket and draft-only next actions. ## Core Features & Use Cases - Priority ranking with rationale: Scores each ticket on urgency, impact, age, and SLA risk, writing the reasoning for every rank. - Draft-only next actions: Produces draft replies, suggested assignees, and suggested macros, each labeled as awaiting owner approval — never sends or modifies tickets. - Batch reconciliation: Compares two triage batches ticket by ticket, resolving conflicts and orphans with stated reasons. - Use Case: A support lead pastes a morning queue of 40 tickets and receives a ranked list with rationales, a delegate/escalate lane, and drafts ready for review before anything is sent. ## Quick Start Triage this Zendesk ticket batch, rank each ticket by priority with a rationale, and draft the next action for anything that needs one.

Frequently Asked Questions about zendesk-triage

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

FAQPage Schema
How do I triage a Zendesk ticket queue by priority?▼

Provide the ticket batch with ids, subjects, requester types, dates, statuses, and priorities. The Skill scores each ticket on urgency, impact, age, and SLA risk, then returns a ranked list with a written rationale and a drafted next action per ticket.

Can this skill send replies or change Zendesk ticket statuses?▼

No. It is read-only plus drafts: it never sends replies, assigns, merges, closes, or edits any ticket field. Any write requires the owner's explicit approval of the exact message or change and happens outside this skill.

What Zendesk credentials and inputs does ticket triage need?▼

It needs a ticket batch with id, subject, requester type, created date, status, and priority, plus queue context like the source view and applicable SLA clocks. Access uses environment variables ZENDESK_SUBDOMAIN, ZENDESK_USER, and ZENDESK_TOKEN, never pasted values.

How does re-triage compare two Zendesk ticket batches?▼

It diffs batch A and batch B ticket by ticket, listing agreements, priority conflicts, and tickets missing from either ranking. Every conflict and orphan is resolved with a stated reason before the final triage is produced.

When should I not use automated Zendesk triage?▼

Do not use it for bulk automation design, SLA policy changes, or systems beyond the batch you were given. It also cannot triage tickets that are unreachable or missing required fields; those are flagged as untriaged instead.