What problem does it solve?
When creating or updating PostHog insights, agents often misuse formulas and literal postfixes to fake units (e.g. dividing seconds by 60 to show minutes, or appending "%" to ratios), which freezes the unit at one scale and produces broken labels like "50%%". This Skill guides correct use of PostHog's built-in axis formatter so values stay numerically correct while labels render in friendly units.
Core Features & Use Cases
- TrendsQuery formatting: Set
trendsFilter.aggregationAxisFormat to duration, duration_ms, percentage, percentage_scaled, currency, or short, with companion fields aggregationAxisPrefix, aggregationAxisPostfix, and decimalPlaces.
- SQL insight formatting: Configure per-column
chartSettings.yAxis[].settings.formatting on DataVisualizationNode with styles none, number, short, or percent, avoiding double-scaling pitfalls.
- Anti-pattern detection: Recognize and fix formula/postfix hacks (e.g.
A / 60 with " mins") during posthog:insight-update calls.
- Use Case: When graphing p95 page load time stored in milliseconds, set
aggregationAxisFormat: "duration_ms" so values render as 850ms, 1.5s, or 1m 4s automatically instead of raw numbers.
Quick Start
Ask the agent to create a PostHog trend insight of average session duration with the y-axis formatted as a duration.