What problem does it solve?
Setting up error notifications in PostHog requires choosing the right lifecycle trigger event, avoiding duplicate alerts, and wiring a destination correctly β mistakes here cause alert fatigue or silent failures. This Skill guides the full authoring workflow so alerts fire on the right conditions and reach a channel the team actually monitors.
Core Features & Use Cases
- Trigger selection: Picks exactly one of the three lifecycle events (
$error_tracking_issue_created, $error_tracking_issue_reopened, $error_tracking_issue_spiking) based on project noise level and urgency needs.
- Dedup and integration wiring: Lists existing alerts to prevent duplicate deliveries, resolves Slack workspace and channel ids, and validates webhook URLs before creating anything.
- Canonical message templates: Ships alerts with block-kit bodies matching the in-product alert wizard, including per-issue property scoping and spike-baseline guards.
- Use Case: A user pastes an issue link and asks to be notified when it happens again β the Skill creates a
_reopened alert scoped to that issue's $exception_issue_id, delivered to their chosen Slack channel.
Quick Start
Set up a PostHog alert that posts to my #oncall Slack channel whenever an error issue starts spiking.
