Skip to main content
Generalgtmagents

escalation

Use to define incident tiers, response protocols, and stakeholder communications.

Stars
259
Source
gtmagents/gtm-agents
Updated
2026-04-03
Slug
gtmagents--gtm-agents--escalation
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/gtmagents/gtm-agents/HEAD/plugins/community-orchestration/skills/escalation/SKILL.md -o .claude/skills/escalation.md

Drops the SKILL.md into .claude/skills/escalation.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Community Escalation Framework Skill

When to Use

  • Preparing moderators for sensitive situations (security issues, harassment, outages, leaks).
  • Coordinating cross-functional response when community incidents impact customers or brand.
  • Reviewing past incidents to tighten governance and tooling.

Framework

  1. Tiering – classify incidents (info request, policy violation, critical escalation) with examples.
  2. Ownership – map responders per tier (moderators, comms, legal, security, exec sponsor).
  3. Response Playbooks – outline steps, messaging, approvals, and timelines per tier.
  4. Tooling & Evidence – define logging requirements, screenshots, data retention, and ticketing.
  5. Post-incident Review – document root cause, remediation, and preventive actions.

Templates

  • Escalation matrix (tier → trigger → primary owner → backup → SLA).
  • Incident log form with fields for context, actions, and status.
  • Postmortem template (summary, timeline, impact, actions, follow-ups).

Tips

  • Tie escalation flows into community-ops automation for faster routing.
  • Keep response macros ready for common issues to ensure consistent tone.
  • Conduct quarterly tabletop exercises to keep responders aligned.