PostHog

Overview

This skill provides a structured workflow for working with PostHog from ChatGPT and Codex. It assumes the bundled PostHog app is connected so the PostHog tools are available for analytics, feature flags, experiments, error tracking, and more.

PostHog is an all-in-one product platform. The same project's data backs every surface below, so most questions can be answered by querying analytics or running HogQL, and most product changes (flags, experiments, surveys) can be made directly.

Prefer live tools over pre-trained knowledge. Your baked-in knowledge of PostHog's API, HogQL functions, and tool shapes may be outdated. The connected PostHog app advertises its own skills and tools at runtime and asks clients to prioritize its skills over raw tools — discover and follow those rather than guessing. When in doubt about syntax, limits, or product behavior, use the documentation-search tool.

Prerequisites

• The PostHog app must be connected and accessible via OAuth.
• Confirm which PostHog organization and project the request targets before reading or writing.
• Self-hosted users connect against their own instance during the app's OAuth flow.

Required Workflow

Follow these steps in order. Do not skip steps.

Step 0: Connect the PostHog app (if not already configured)

If PostHog tools are unavailable, pause and ask the user to connect the PostHog app:

1. Enable the bundled PostHog app for this plugin or session.
2. Complete the PostHog OAuth flow if prompted, and select the correct organization/project.
3. Restart Codex or the current session if the tools still do not appear.

After the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.

Step 1

Clarify the user's goal and scope (e.g., a metric over a time range, a funnel, a new feature flag, an experiment readout, an error investigation). Confirm the target project, date range, event/property names, and any filters or cohorts.

Step 2

Discover the available PostHog skills/tools the connected app exposes and pick the right one for the task. Resolve identifiers (project ID, flag key, experiment ID, insight/dashboard ID, error issue ID) before calling tools. For anything involving syntax, function names, or product behavior, search the docs first.

Step 3

Execute PostHog tool calls in logical batches:

• Read first — list/get/query (insights, events, HogQL/SQL, error issues) to build context.
• Write next — create or update flags, experiments, surveys, dashboards, or insights with all required fields.
• For destructive or broad changes (e.g., toggling a flag in production, ending an experiment), state the impact and confirm before applying.

Step 4

Summarize results with concrete numbers and links to the PostHog UI where available, call out caveats (sampling, person-on-events timing, date ranges), and propose next actions.

Capability Map

Use this to route a request to the right PostHog surface, then discover the exact tool the app exposes for it.

HogQL & Querying Tips

• HogQL is PostHog's SQL dialect over the events/persons schema. Read the data schema before writing queries, and confirm event and property names exist.
• With person-on-events enabled, person.properties.* on the events table reflect the value at ingestion time, not the person's current value — the same person can show different values across events. Don't build workarounds for "query-time" person properties.
• Respect the project timezone when bucketing by day.
• Start narrow (small date range, limited rows), validate, then widen.

Tips for Maximum Productivity

• Batch related reads before writes; confirm identifiers up front.
• Use natural-language asks where the app supports them ("signups by week this quarter").
• Reference prior insights/dashboards instead of rebuilding from scratch.
• For experiments and flags, double-check rollout conditions and targeting before enabling.

Troubleshooting

• Tools missing: re-run the app connection/OAuth flow (Step 0); verify org/project access.
• Empty or surprising results: re-check event/property names, date range, filters, and timezone; confirm the events exist via a small query.
• Permission errors: confirm the connected account has access to the target project and the action (some changes require elevated roles).
• Unsure about syntax or limits: search the PostHog docs rather than guessing.