Agent skill · posthog
understanding-billing-usage
Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey responses, synced rows, logs, AI events, AI credits, or Inbox credits. Starts from Billing usage/spend tools, then routes to customer-visible product MCP surfaces for deeper investigation.
What it needs
About 7k tokens when loaded.
What this skill does
Understanding billing usage Use this skill for customer-facing "what am I using and why?" Billing usage workflows. The question may come from the Billing usage dashboard, a usage alert email, an AI chat prompt, or a user who noticed high usage, spend, a spike, or a drop. The core rule: Billing tools explain what changed, when, and which project drove it. Product tools explain why it happened. If a prompt sounds like "why are my events high?" or "why did recordings/logs/AI credits increase?" and Billing tools are available, start here rather than jumping straight to the product-specific metric skill. Once the billable usage type, project, and window are known, hand off to the relevant product tools or skill for the root-cause drilldown. This skill is not meant for broad invoice, plan, refund, contractual credit, subscription, or contract questions. Keep it focused on usage and spend behavior. Available tools Tool Purpose ------------------------------ ----------------------------------------------------------------------- posthog:billing-overview-get Org billing context, subscribed products, team names, and usage summary posthog:billing-usage-get Time-series usage by day, usage type, and team posthog:billing-spend-get Optional spend context when the user asks about dollars Product-specific MCP tools Follow-up investigation inside the affected product/project Only use this skill when the Billing read tools above are available. If the user asks about Billing usage and those tools are not available, do not continue with this workflow; briefly say that Billing usage investigation is not enabled for this organization or MCP session. If a Billing tool is available but returns a permission error, explain that the MCP session needs Billing access from an org admin or owner rather than saying the feature is unavailable. Some clients expose PostHog MCP tools through mcpposthogexec instead of direct posthog: tool names. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills posthog/understanding-billing-usage