escalationPackage support investigations into engineering-ready escalation briefs.
kb-articleTurn a resolved or well-understood triage report into a draft knowledge-base article (how-to, troubleshooting, known issue or FAQ). Use after triage when the same question is likely to come up again.
known-issue-searchSearch bug trackers, release notes, and source history before concluding misconfiguration or expected behavior on any bug-shaped ticket. Use this skill any time a ticket reports something that worked once and now does not, an upload/build that logs success but the product cannot use, UI state that d
log-evidenceRead customer-supplied logs, stack traces, HAR files and browser console output as evidence. Use when a ticket includes or needs log artifacts, to extract timestamps, error signatures and request outcomes without running anything.
redactionStrip secrets, tokens, raw person properties, private URLs, and internal admin links before saving any triage output to disk or copying into customer-facing text. Use this skill before Phase 3 of the triage workflow, before posting to any channel, and before sharing any saved report outside the imme
reproduction-stepsWrite a minimal, numbered reproduction for a support ticket, with environment, expected and actual results, so an engineer can confirm a suspected bug. Use for bug-shaped tickets and before escalating.
response-draftingDraft customer-facing support responses from verified triage findings.
support-triageRun the read-only support triage workflow on a ticket and save an evidence-graded triage report plus a draft customer response under reports/. Use when the user pastes a support ticket, points at a ticket file, or asks to triage a bug report or escalation. Entry point for hosts without custom agents
ticket-intakeNormalize a raw support ticket into structured investigation inputs.
triage-reportProduce a structured, evidence-graded support triage report.