skills.rest
mongo-ai
mongo-aiCOMMUNITY
Explore all skills by this author →
GitHub

posthog-event-diagnosis

Diagnose missing, delayed, duplicated, filtered, or malformed PostHog events.

Updated Aug 27, 2026
Search Tags:#documentation#github#troubleshoot#sql#diagnosis#posthog#event
One-click install
npx skills add https://github.com/mongo-ai/posthog-triage-agent --skill posthog-event-diagnosis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: posthog-event-diagnosis
Source: https://github.com/mongo-ai/posthog-triage-agent/tree/main/.claude/skills/posthog-event-diagnosis
Command: npx skills add https://github.com/mongo-ai/posthog-triage-agent --skill posthog-event-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers and support staff pinpoint why PostHog events are missing, delayed, duplicated, filtered, or malformed, turning vague ticket symptoms into concrete causes.

Core Features & Use Cases

  • Guides a step‑by‑step diagnostic workflow that queries recent events, examines library metadata, checks for ad‑blocker or reverse‑proxy issues, looks for ingestion warnings, investigates duplicates, verifies destination pipelines, and searches known GitHub issues.
  • Leverages live documentation searches to provide up‑to‑date guidance alongside the diagnostic steps.
  • Ideal for troubleshooting support tickets where a user reports that an event is not captured or appears incorrectly.

Quick Start

Ask the skill to diagnose the PostHog event issue for a given distinct ID and event name.

Frequently Asked Questions about posthog-event-diagnosis

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

FAQPage Schema
How do I troubleshoot missing or delayed PostHog events?▼

To troubleshoot missing or delayed PostHog events, query recent event data using SQL, examine library metadata, and check for ad-blocker or reverse-proxy issues. This diagnostic workflow pinpoints concrete causes from vague symptoms.

What causes malformed or duplicated PostHog event data?▼

Malformed or duplicated PostHog event data often stems from ingestion warnings, library metadata issues, or destination pipeline errors. Investigating duplicate records and checking live documentation against known GitHub issues identifies the root cause.

How do I diagnose filtered PostHog events for a specific user?▼

To diagnose filtered PostHog events, apply a diagnostic workflow to a given distinct ID and event name. This queries event data, checks library details, and verifies destination pipelines to locate where events were dropped.

Do I need SQL access to investigate PostHog event ingestion issues?▼

Yes, you need access to PostHog SQL queries to investigate event ingestion issues effectively. The diagnostic workflow requires querying recent events, checking duplicate records, and searching live documentation alongside GitHub issues.

Why are PostHog events not captured even though the tracking code is installed?▼

PostHog events may not be captured due to ad-blocker interference, reverse-proxy misconfiguration, or ingestion warnings. Searching known GitHub issues and examining library metadata helps isolate the specific capture failure.

Related Skills

Explore More Software Engineering Skills→
PostHogPostHog
37.6k

survey-sdk-audit

Audit PostHog survey SDK feature parity across supported platforms.

Official
Advanced
wgordon17wgordon17

bug-investigation

Dispatch background agents to investigate reported bugs and update BUGS.md.

Community
Advanced
omerakbenomerakben
1

nextjs-app-router

Instrument Next.js App Router apps with PostHog analytics for client and server events.

Community
Advanced
Vero-VenturesVero-Ventures

posthog

Query PostHog analytics data via REST API for events, flags, sessions, and trends.

Official
Intermediate