Agent skill · posthog
creating-box-plot-insights
Creates product analytics or SQL-backed box plot insights in PostHog. Use when a user asks to create, build, or save a box plot, visualize a numeric distribution, compare quartiles or medians across dates or groups, or turn SQL results into a box plot. Chooses between a standard Trends box plot and a SQL insight, validates the distribution data, saves the insight, and verifies it.
What it needs
About 3k tokens when loaded.
What this skill does
Creating box plot insights Box plots need distribution data, not an already-aggregated average or total. Choose the simplest query type that can express the user's question. Choose the query type Use a standard product analytics box plot when all of these are true: The source is an event, action, or warehouse table supported by Trends. One numeric property contains the values to distribute. The user wants the distribution over a normal time interval. Use a SQL box plot when the user needs custom grouping, joins, derived values, or bespoke SQL. Read querying-posthog-data before writing HogQL, then use references/sql-examples.md as a starting point. Do not use SQL only to reproduce a standard Trends query. Standard product analytics box plot 1. Identify the event or action and its numeric property. Confirm the property is numeric before saving. 2. Build an InsightVizNode whose source is a TrendsQuery: Set the series event or action. Set mathproperty to the numeric property. Set trendsFilter.display to BoxPlot. Choose the date range and interval that match the question. 3. Run the query with posthog:query-trends. 4. If it returns distribution rows, save it with posthog:insight-create. 5. Read it back with posthog:insight-get and confirm the property, interval, and display. A box plot without a numeric mathproperty is invalid. Do not substitute event counts unless counts are the values the user wants to distribute. SQL box plot The SQL must return one pre-aggregated row for each X-axis and series pair. Calculate the summary in the database. Never calculate percentiles from the limited result rows in the client. Required numeric roles: minimum 25th percentile median mean 75th percentile maximum The easiest result shape uses these aliases: x and series are optional: Set xAxisColumn to null for one overall distribution or one box per series. Set seriesColumn to null for one series. Validate the HogQL with posthog:execute-sql before saving. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills posthog/creating-box-plot-insights