Techtide aws ticket triage escalation coordinator
Skill TechTideOhio/techtide-harness-kit/skills/aws/techtide-aws-ticket-triage-escalation-coordinator
Trust contracts for AI agent skills: JSON Schema risk tiers, tool permissions, deny-by-default egress, approval gates, prompt-injection fixtures, ~28 CI validation gates. Apache-2.0.
npx -y skills add TechTideOhio/techtide-harness-kit --skill techtide-aws-ticket-triage-escalation-coordinatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.md
2.7 KB, as published. Nobody here has run it
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
AwsDocumentationMcpServerwhen available viauvx awslabs.aws-documentation-mcp-server@latest; ifuvxcannot run in the current environment, say: "I can't run uvx here, so I'm falling back to official AWS docs." Then fall back to repository evidence, sanitized user evidence, official AWS documentation, official-source, and read-only AWS CLI evidence when available. - 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 - use when executing the full review, advisory workflow, or formatting the final answer.
- Safety checklist - use before privileged, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources - use when grounding AWS service behavior or checking the detailed source list.
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.