
Normalize an incoming support ticket into structured investigation inputs: product area, identifiers, scope clues, URLs, timeframe, and likely first diagnostic path.
Diagnose session replay issues including missing recordings, broken or blank replays, CSP/CORS failures, asset loading issues, browser-side recorder problems, and mobile SDK performance/OOM/masking issues.
Draft professional, empathetic customer-facing responses for PostHog support tickets. Adapts tone to situation type, urgency, and customer relationship. Use when generating the Draft Customer Response section of a triage report or when drafting any customer-facing reply.
Draft a PostHog docs update or internal KB article from a resolved support issue. Use when a ticket reveals a docs gap, a recurring issue without documentation, or a workaround worth publishing.
Diagnose PostHog error tracking issues including missing exceptions, bad stack traces, unresolved/minified frames, release/source-map mismatches, and issue grouping confusion.
Diagnose PostHog data warehouse issues including failed external source syncs, query errors, schema mismatches, join configuration problems, slow queries, and missing or stale data from linked sources.
Diagnose PostHog billing, plan tier, and account access issues including feature entitlement mismatches, payment failures, upgrade/downgrade problems, and plan confusion. Determines when to handle in support vs escalate to the billing team.
Diagnose feature flag and experiment issues including false/empty evaluations, flicker, stale properties, exposure problems, and server-side latency.
Diagnose missing, delayed, duplicated, filtered, or malformed events using PostHog project evidence, live docs, and known-issue search.
Structure and package PostHog support escalations for engineering with full context, reproduction evidence, business impact, and clear asks. Use when the triage report recommends escalation or when evidence points to an upstream bug, data issue, or infrastructure problem.
Diagnose PostHog self-hosted deployment issues including Docker Compose and Helm/Kubernetes problems, ClickHouse and Postgres failures, resource limits, reverse proxy misconfigurations, and data ingestion gaps. Clearly distinguishes PostHog bugs from customer infrastructure issues.
Diagnose PostHog data pipeline and CDP function issues including destination delivery failures, transformation errors, function execution problems, and filter/routing misconfigurations.
Diagnose PostHog survey issues including surveys not appearing, targeting mismatches, response collection failures, display timing problems, and API-mode survey integration issues.
Format and post triage reports to Slack using optimized mrkdwn layout. Use after generating a triage report to post it to the #support-triage channel or any specified channel.
Escalation-only browser inspection skill for public sites using Playwright CLI. Checks PostHog presence, config, replay, flags, network requests, debug console output, bundled implementations, custom proxy detection, and competing analytics.
When a triage report identifies a docs gap or simple fix opportunity, this skill finds the exact file in the PostHog repos, drafts the change, and produces a PR-ready brief. Embodies PostHog's "ship fixes, not just log bugs" culture.
Diagnose PostHog web analytics issues including missing pageviews, incorrect bounce rates, broken channel attribution, missing UTM data, reverse proxy problems, and discrepancies with other analytics tools.
Final synthesis skill. Produce a structured, evidence-graded triage report with a clear root-cause assessment, honest confidence, and a ready-to-send customer response.