Official agent skill

Modeling Revenue Metrics

by PostHog in PostHog/posthog

Build reusable revenue models — MRR, ARR, gross revenue, new/expansion/contraction/churn, ARPU, LTV, and per-customer/per-account revenue — on either PostHog data-warehouse views (HogQL) or an…

OfficialCustom licenceAuto-check passedData & Analytics

Install Modeling Revenue Metrics

skills CLI
$ npx skills add PostHog/posthog --skill modeling-revenue-metrics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PostHog/posthog modeling-revenue-metrics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/data_modeling/skills/modeling-revenue-metrics .claude/skills/modeling-revenue-metrics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
modeling-revenue-metrics
GitHub stars
40k
Token cost
~2.1k tokens
SKILL.md length
678 words
Files
10 (incl. references)
Skills in repo
254
Repo updated
First seen
Licence
Custom licence

At a glance

Build reusable revenue models — MRR, ARR, gross revenue, new/expansion/contraction/churn, ARPU, LTV, and per-customer/per-account revenue — on either PostHog data-warehouse views (HogQL) or an…

  • Works in 3 steps: find where revenue lives → model on the managed views, not raw tables → build the model
  • The user wants to model
  • SKILL.md covers Step 1 — find where revenue…, Step 2 — model on the managed…, Rules before you model… and Step 3 — build the model, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Modeling Revenue Metrics is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Build reusable revenue models — MRR, ARR, gross revenue, new/expansion/contraction/churn, ARPU, LTV, and per-customer/per-account revenue — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model, define, or compute recurring revenue, monthly/annual recurring revenue, churn or retention of revenue, lifetime value, average revenue per user, or revenue by customer, cohort, product, or currency. On PostHog, build on the managed revenueview views (revenueitem, mrr…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/dbt/_sources_stripe.yml`, `references/dbt/schema.yml` and `references/revenue-metric-definitions.md`).

It sits in Data & Analytics, covering Data pipelines and ETL, Data warehousing and Financial modeling. It works with PostHog, dbt and Stripe. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…

When your agent uses it

  • The user wants to model
  • Compute recurring revenue
  • Monthly/annual recurring revenue
  • Retention of revenue

Example prompts

  • “/modeling-revenue-metrics”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. find where revenue lives
  2. model on the managed views, not raw tables
  3. build the model

What it can do on your machine

Read from SKILL.md and the folder at commit c012c8d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are sql).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Modeling Revenue Metrics loads about 2.1k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 255 tokens; SKILL.md has 678 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~255
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 678 words (~2,111 tokens).

“Turn payment/subscription data into durable revenue models. Read modeling-warehouse-foundations first for the view-vs-dbt decision, the view-* workflow, and convertCurrency(); this skill is the revenue-specific layer on top. Metric definitions live in references/revenue-metric-definitions.md; copy-paste recipes in references/posthog/ and references/dbt/.”

— opening of SKILL.md by PostHog, Custom licence
name
modeling-revenue-metrics

Read the full SKILL.md on GitHub

Files

SKILL.md and 9 other files (references) in products/data_modeling/skills/modeling-revenue-metrics of PostHog/posthog.

  • SKILL.md
  • references/dbt/_sources_stripe.yml
  • references/dbt/dim_customer.sql
  • references/dbt/fct_mrr.sql
  • references/dbt/fct_revenue_item.sql
  • references/dbt/schema.yml
  • references/posthog/gross_revenue_by_month.sql
  • references/posthog/mrr_and_arr.sql
  • references/posthog/revenue_by_customer.sql
  • references/revenue-metric-definitions.md

Open the folder on GitHubat commit c012c8d

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Modeling Revenue Metrics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Modeling Revenue Metrics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Modeling Revenue Metrics this skillPostHog/posthog40k—~2.1kAutomated safety check: PassCustom licence
Erd Studio Setupliam-machine/erd-studio165—~8.6kAutomated safety check: PassCustom licence
dbt Incremental ModelsAltimateAI/data-engineering-skills128—~2.3kAutomated safety check: PassMIT
Analytics Engineerborghei/Claude-Skills891—~3.4kAutomated safety check: PassMIT
Airflow State Storeastronomer/agents451—~6.1kAutomated safety check: PassApache-2.0
Migrating Dbt Project Across PlatformsKilo-Org/kilo-marketplace190—~3.9kAutomated safety check: PassApache-2.0

Similar skills

  • Erd Studio Setup

    liam-machine/erd-studio

    Friendly, step-by-step setup for ERD Studio in an existing dbt project, for people who may be new to dbt or data modelling.

    165 GitHub stars~8.6k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed
  • dbt Incremental Models

    AltimateAI/data-engineering-skills

    Helps choose an incremental strategy, design a reliable unique_key and debug failing dbt incremental models, and says when a plain table is the better choice.

    128 GitHub stars~2.3k tokensUpdated 3 days ago
    Data & AnalyticsAuto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    891 GitHub stars~3.4k tokensUpdated 4 days ago
    Data & AnalyticsAuto-check passed
  • Airflow State Store

    astronomer/agents

    Persists task and asset state across retries and DAG runs using Airflow 3.3's AIP-103 key/value stores (taskstatestore, assetstatestore) and the crash-safe ResumableJobMixin.

    451 GitHub stars~6.1k tokensUpdated 3 days ago
    Data & AnalyticsAuto-check passed
  • A skill your agent uses when migrating a dbt project from one data platform or data warehouse to another (e.g., Snowflake to Databricks, Databricks to Snowflake) using dbt Fusion's real-time…

    190 GitHub stars~3.9k tokensUpdated 12 days ago
    Data & AnalyticsAuto-check passed
  • Snowflake Snowpark Dbt

    Mindrally/skills

    Best practices for Snowpark Python (DataFrames, UDFs, UDTFs, stored procedures) and dbt with the dbt-snowflake adapter.

    271 GitHub stars~2.5k tokensUpdated 2 days ago
    Data & AnalyticsAuto-check passed

More from PostHog/posthog

All 254 skills in this repo
  • Authoring Log Alerts

    PostHog/posthog

    Official

    Author useful, low-noise log alerts on services in a PostHog project.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    40k GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • Official

    Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).

    40k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Exploring Apm Traces

    PostHog/posthog

    Official

    Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.

    40k GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Exploring LLM Traces

    PostHog/posthog

    Official

    Debug and inspect LLM/AI agent traces using PostHog's MCP tools.

    40k GitHub stars~4.4k tokensUpdated today
    Auto-check passed
  • Investigate Metric

    PostHog/posthog

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

    40k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Questions about Modeling Revenue Metrics

What does Modeling Revenue Metrics do?

Build reusable revenue models — MRR, ARR, gross revenue, new/expansion/contraction/churn, ARPU, LTV, and per-customer/per-account revenue — on either PostHog data-warehouse views (HogQL) or an…. Modeling Revenue Metrics is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Build reusable revenue models — MRR, ARR, gross revenue, new/expansion/contraction/churn, ARPU, LTV, and per-customer/per-account revenue — on either PostHog data-warehouse views (HogQL) or an external dbt project.

When should I use Modeling Revenue Metrics?

Modeling Revenue Metrics fits situations like: the user wants to model; compute recurring revenue; monthly/annual recurring revenue; retention of revenue.

How do I install Modeling Revenue Metrics in Claude Code?

Run `npx skills add PostHog/posthog --skill modeling-revenue-metrics -a claude-code`. Or copy the skill folder (products/data_modeling/skills/modeling-revenue-metrics in PostHog/posthog) into .claude/skills/modeling-revenue-metrics in your project. Claude Code loads it when a task matches its description.

How do I install Modeling Revenue Metrics in Codex?

Run `npx skills add PostHog/posthog --skill modeling-revenue-metrics -a codex`. Or copy the skill folder (products/data_modeling/skills/modeling-revenue-metrics in PostHog/posthog) into .agents/skills/modeling-revenue-metrics in your project. Codex loads it when a task matches its description.

Can I use Modeling Revenue Metrics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill modeling-revenue-metrics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/modeling-revenue-metrics, .gemini/skills/modeling-revenue-metrics, .github/skills/modeling-revenue-metrics and .opencode/skills/modeling-revenue-metrics in your project.

What does Modeling Revenue Metrics need to run?

SKILL.md names no scripts, command-line tools or credentials: Modeling Revenue Metrics is instructions for the agent only.

Does Modeling Revenue Metrics access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Modeling Revenue Metrics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Modeling Revenue Metrics use?

Modeling Revenue Metrics has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Modeling Revenue Metrics use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.

What are the alternatives to Modeling Revenue Metrics?

Skills that share tags, products or a category with Modeling Revenue Metrics: Erd Studio Setup (liam-machine/erd-studio, 165 stars), dbt Incremental Models (AltimateAI/data-engineering-skills, 128 stars), Analytics Engineer (borghei/Claude-Skills, 891 stars) and Airflow State Store (astronomer/agents, 451 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Modeling Revenue Metrics?

PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 2026.

Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.