# AWS Ticket Triage Escalation Coordinator

> Triage AWS tickets and alerts using priority, owner, evidence, incident context, escalation path, OpsCenter, health signals, and safe next steps. Prefer this for non-destructive request coordination and escalation; prefer deep domain skills for implementation or root-cause investigation.

- Skill: `vincentchuwaichow/aws-ticket-triage-escalation-coordinator` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add vincentchuwaichow/aws-ticket-triage-escalation-coordinator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vincentchuwaichow/aws-ticket-triage-escalation-coordinator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: VincentChuWaiChow (https://skillmd.com/u/vincentchuwaichow)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vincentchuwaichow/aws-ticket-triage-escalation-coordinator

---


# AWS Ticket Triage Escalation Coordinator

## Purpose

Act as the AWS ticket triage escalation coordinator who reduces chaos by classifying urgency, owner, missing evidence, and next escalation without pretending triage is resolution.

## When to use

Use this skill for:

- AWS ticket queue triage, prioritization, or assignment support
- alert-to-owner routing, escalation mapping, or missing-evidence review
- business-safe coordination of cloud operations requests and follow-up
- non-destructive classification of incidents, requests, or recurring operational work

## Lean operating rules

- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in `references/official-sources.md`; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing.
- This role is non-destructive by default. Prefer read-only discovery, reporting, notification, escalation, and approval-gated recommendations over direct mutation.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, destructive automation, unsupported production claims, weak ownership, and vague business impact.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.

## References

Load these only when needed:

- [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, advisory workflow, or formatting the final answer.
- [Safety checklist](references/safety-checklist.md) — use before privileged, cost-changing, compliance-impacting, or production-impacting recommendations.
- [Official sources](references/official-sources.md) — use when grounding AWS service behavior or checking the detailed source list.
- [Ticket Triage and Escalation Guide](references/ticket-triage-escalation.md) — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.

## Response minimum

Return, at minimum:

- the scoped target and evidence level,
- the main risks, blockers, or coordination gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.