PostHog

PostHog captures events from browser, server and mobile SDKs and builds everything else on them: persons, feature flags, experiments, surveys, session replay, error tracking, logs, metrics, LLM traces, the warehouse and HogQL over all of it. An integration can look complete while zero events arrive (a missing Content Security Policy entry, an ad blocker, a host in the wrong region, a short-lived process that never flushed), so most outcomes come down to three things: the SDK initializes once, early, from environment variables; every event lands on the right person because the same distinct ID is used everywhere; and arrival is confirmed in PostHog, not assumed. Vendor-neutral OpenTelemetry is the observability skill. Tool-agnostic test design (hypothesis, sample size, reading the result, templates) is ab-testing SKILL.md; attribution models, reconciling channels and the first-party stitch to a booking or checkout are marketing-attribution SKILL.md.

Apply only the routes and checks for the selected job. Read a linked skill's named file from its installed folder when available, or from the linked source. Report an unavailable required reference instead of inventing it. [skill-authoring, DISTRIBUTION.md#composing-skills]