posthog-escalation

Name: posthog-escalation
Availability: InStock
Author: mongo-ai

Generate markdown escalation briefs for PostHog support tickets.

Updated Aug 27, 2026

Search Tags:#markdown #support #triage #escalation #posthog #incident-report

Ready to run

npx skills add https://github.com/mongo-ai/posthog-triage-agent --skill posthog-escalation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: posthog-escalation
Source: https://github.com/mongo-ai/posthog-triage-agent/tree/main/.claude/skills/posthog-escalation
Command: npx skills add https://github.com/mongo-ai/posthog-triage-agent --skill posthog-escalation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Support agents need a consistent way to turn detailed triage investigations into complete, well‑structured escalation packages for engineering, ensuring all context, evidence, impact, and next steps are communicated clearly.

Core Features & Use Cases

Standardized escalation format with sections for severity, impact, evidence, reproduction steps, and follow‑up cadence.
Impact assessment tables to quantify breadth, depth, duration, revenue signal, and data risk.
Routing matrix that maps issue types to the appropriate PostHog engineering team.
De‑escalation criteria and follow‑up cadence guidance to keep stakeholders aligned.
Use case: When a triage report flags a bug, data integrity issue, or infrastructure problem, the skill generates a ready‑to‑share markdown brief for the engineering team.

Quick Start

Generate an escalation brief for the ticket about posthog.displaySurvey() failure using the posthog‑escalation skill.

Frequently Asked Questions about posthog-escalation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a structured escalation brief for engineering from a support triage report?▼

To create an escalation brief, package the triage report findings into a structured markdown document. The brief includes severity, impact assessment, reproduction steps, and follow-up cadence to communicate context clearly to engineering.

What is the standard format for escalating a PostHog support ticket to engineering?▼

The standard escalation format is a markdown document featuring sections for severity, impact assessment tables, evidence, reproduction steps, routing information, and follow-up cadence guidance to ensure complete context transfer.

How do I assess and document the impact of a bug before escalating it to the engineering team?▼

Assess bug impact by generating an impact assessment table within the escalation brief. This table quantifies the breadth, depth, duration, revenue signal, and data risk associated with the support case.

Can I use this to route a data integrity issue to the correct PostHog engineering team?▼

Yes, you can route data integrity issues using the built-in routing matrix. The matrix maps specific issue types from the triage report to the appropriate PostHog engineering team for targeted resolution.

What should I include in a markdown incident report for escalating infrastructure problems?▼

A markdown incident report for infrastructure problems should include triage evidence, impact assessment, reproduction steps, routing information, and de-escalation criteria to align stakeholders on the resolution cadence.

When do I need to generate a formal escalation brief instead of just forwarding a support ticket?▼

You need a formal escalation brief when a triage report recommends escalation for a bug, data issue, or infrastructure problem. It standardizes context, evidence, and next steps so engineering receives a complete package.