smithery/gtmagents

escalation

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

Installation

$ npx skills add smithery/gtmagents --skill escalation

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,387 B
  • docs SUMMARY.md 99 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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.