Agent skill · marketing growth · jeremylongshore
posthog-core-workflow-a
Design and implement a governed PostHog event taxonomy with capture, identity, group, and property contracts. Use when instrumenting a product workflow or repairing inconsistent analytics events. Trigger with "PostHog analytics", "capture events", or "PostHog identify".
Why this skill is useful
Provides specific implementation patterns and event taxonomy for PostHog analytics that the AI wouldn't reliably generate on its own.
What it needs
Requires posthog-js, posthog-node installed locally. Requires posthog account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
PostHog Core Workflow A — Product Analytics Overview Primary PostHog workflow covering event capture, user identification, group analytics, and person properties. This is the foundation for all PostHog analytics: capturing what users do, linking events to identified users, and grouping users by company/team for B2B analytics. Prerequisites Completed posthog-install-auth setup posthog-js (browser) and/or posthog-node (server) installed Project API key (phc...) configured Instructions Tool discipline Use Read to inspect the relevant configuration and implementation before proposing changes. Use Grep to locate initialization, capture, flag, and credential boundaries. Use Write only for a new, explicitly requested artifact inside the target project. Use Edit for minimal changes to existing project files after the evidence pass. Step 1: Define Event Taxonomy Step 2: Capture Events (Browser) Step 3: Identify Users and Set Properties Step 4: Group Analytics (B2B Company Tracking) Step 5: Server-Side Event Capture (posthog-node) Step 6: Create Annotations for Context Error Handling Error Cause Solution ------- ------- ---------- Events not appearing posthog.init not called Ensure init runs before any capture Anonymous/identified split Different distinctid across platforms Use consistent user ID from your auth system Group data missing posthog.group() not called Call group() before capture for group attribution Server events lost No flush() in serverless Always call await posthog.flush() before response Properties not updating Using $setonce for mutable data Use posthog.people.set() for values that change Output Typed event taxonomy for consistent tracking Browser event capture with user identification B2B group analytics linking users to companies Server-side event capture with proper flushing Annotations marking deployments and product changes Examples For a B2B checkout flow, define stable event names and properties, identify only after authentication, attach the company …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/posthog-core-workflow-a