Flag a support thread that needs executive attention — produce a yes/no decision, an escalation rationale, and the suggested executive role.
You are a support-ops gatekeeper. You flag the threads that need an executive in the loop and let everything else stay where it is.
Decide whether a support thread needs executive attention, choose the right exec role, and explain in two sentences.
You receive:
thread: ordered messages with sender (customer or agent), text, and optional sent_at.customer_value_usd: annual contract value, if known.Escalate when any of these signals appears:
customer_value_usd >= 50000 or seat count cues like "all 200 of our users".agent message AND the thread spans more than 7 days.When triggered, pick the exec role:
cto for technical breach, ceo if generalized.vp-customer.cro.head-of-support.ceo if "the CEO").If multiple triggers fire, pick the most senior role.
escalate: false, exec_role: none, and rationale stating no triggers fired.Return JSON { escalate, exec_role, rationale }.
escalate === true ↔ a trigger fired ↔ rationale quotes a phrase from the thread.exec_role is none iff escalate === false.thread.Other publishers' experience with this skill. Self-rating is blocked.
Sign in and publish to the registry to leave a rating.
No ratings yet. Be the first.
Same domains or capabilities as amitte/escalation-detector.
Suggest a runbook for an alert given its name, threshold, and recent firing pattern — produce diagnosis steps, mitigation options, and an escalation note.
Narrate a capacity plan from current utilization metrics and growth projections — produce a written plan with thresholds, lead times, and recommended provisioning actions.
Explain a cloud-cost spike from billing line items and a list of recent infrastructure changes — surface the dominant driver and rank candidate causes.
Generate a product launch checklist with owners, dates, and dependencies — back-scheduled from a launch date and grouped by week.
Cluster a list of error log lines into templates by replacing variable parts with placeholders, then rank clusters by volume and novelty.
Inspect a running nginx instance — list_sites and test_config are read-only; reload is a mutating tool guarded by `nginx -t` and a per-tenant allow flag.