skills.rest
PostHog
PostHogOFFICIAL
Explore all skills by this author →
Website𝕏@PostHogGitHub

understanding-billing-usage

Diagnose PostHog billing usage and spend changes using Billing MCP tools and product drilldowns.

713|118|Updated Aug 11, 2020
Search Tags:#usage analysis#Billing#PostHog#MCP Tools#spike alerts#usage reduction#spend attribution
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill understanding-billing-usage
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: understanding-billing-usage
Source: https://github.com/PostHog/posthog-foss/tree/main/products/billing/skills/understanding-billing-usage
Command: npx skills add https://github.com/PostHog/posthog-foss --skill understanding-billing-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When PostHog customers see unexpectedly high usage, a spend spike, or receive a usage alert email, they need to know which product, project, and time window is responsible before they can act. This Skill turns Billing MCP usage and spend data into a clear attribution of what changed, then routes to the right product surface for root-cause investigation.

Core Features & Use Cases

  • Usage attribution: Breaks down billing usage by type and team to identify which product and project drives usage or spend.
  • Alert validation: Reconstructs spike/drop alert days from dashboard URLs and compares them against same-class weekday or weekend baselines.
  • Product drilldown routing: Maps each billing usage type (events, recordings, feature flag requests, exceptions, logs, AI credits, synced rows, and more) to the correct customer-visible product tools and downstream skills.
  • Use Case: A user receives a "usage spike" email for events. The Skill recreates the Billing usage view from the alert link, identifies the responsible project, compares the alert day to prior weekdays, and drills into top billable event names to find the driver.

Quick Start

Ask why your PostHog event usage spiked on a specific date and have the assistant investigate with the Billing usage tools.

Frequently Asked Questions about understanding-billing-usage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find out why my PostHog usage is high?▼

Start with the Billing usage tools to break down usage by type and team over the last 30 days. This identifies the responsible product and project, after which product-specific tools drill into the root cause, such as top billable event names.

How do I investigate a PostHog usage spike alert email?▼

Use the alert link's usage_types, date_from, and date_to parameters to recreate the Billing usage view. Compare the alert day against prior days in the same weekday or weekend class rather than only against yesterday.

Why did my PostHog spend spike when usage stayed flat?▼

Spend can move independently of usage near the start of a new billing period because pricing tiers reset each period. Check the product tiers and free allocation in the billing overview before treating the movement as a real usage change.

Can I reduce feature flag usage by disabling $feature_flag_called events?▼

No. The billable feature flag metric is /flags API request volume, not $feature_flag_called events. Reducing flag evaluation requests requires changes to how your application polls or evaluates flags.

What happens if Billing MCP tools are not available in my session?▼

The investigation cannot proceed without the Billing read tools. The assistant should state that Billing usage investigation is not enabled, or that the MCP session needs Billing access from an org admin or owner if a permission error occurs.

Does this skill answer invoice, plan, or refund questions?▼

No. It is scoped to usage and spend behavior only. Broad invoice, subscription, contractual credit, refund, or plan questions are explicitly out of scope.

Related Skills

Explore More Data & Analytics Skills→
sudarshan-krishnansudarshan-krishnan

clerk-billing

Implement Clerk Billing subscription management in Next.js applications.

Community
Advanced
mitsuhikomitsuhiko
3.0k

sentry

Fetch and analyze Sentry issues, events, transactions, and logs via the Sentry API.

Community
Intermediate
marquesfelipmarquesfelip

usage-based-billing

Centralize per-tenant usage tracking and metered billing via Stripe meters.

Community
Advanced
PostHogPostHog
75

querying-posthog-data

Query PostHog analytics data using HogQL and SQL foundations.

Official
Intermediate