Skip to main content
skill CX Codex

modeling-activation-metrics — Claude Code skill: activation models

modeling-activation-metrics builds an activation model: a per-user or per-account activated flag plus an activation-rate metric. Useful while the “aha moment” is still a guess.

no license 178 installs ★ 101 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add PostHog/ai-plugin --skill modeling-activation-metrics -a claude-code
Open on GitHub

What modeling-activation-metrics does

Activation here is a model, not one event that someone labelled the aha moment. The skill walks the event taxonomy, lists early actions a new user could take, then tests each one against retention: do the people who did it early stick around more often than those who did not? What wins is the definition that keeps reach wide enough and still separates retained users from the rest, often a combination of actions or a count threshold.

Output depends on the stack. On PostHog you get a view that marks each unit as activated or not within N days of its first event, records time-to-activate, and rolls the rate up by signup cohort on a daily sync_frequency. On dbt there are dim_activation_criteria (the definition stored as data), fct_user_activation with the flag and activated_at, and tests.

Pin the N-day window, because it is part of the definition. B2C counts people, B2B counts accounts through $group_0, where any user can trigger it. Event names arrive from ingestion, so the skill treats them as quoted data and asks you to confirm the candidate list before a view-create that writes a persistent view. Two companions are prerequisites: modeling-warehouse-foundations for the mechanics, and modeling-product-usage-metrics for the retention check.

What it helps with

  • test whether an assumed activation event actually predicts retention
  • choose a count threshold that keeps reach without losing signal
  • model account-level activation for B2B with $group_0
  • publish an activation rate by signup cohort in PostHog
  • keep the activation definition in dbt as a table instead of a hard-coded query

Example prompts for the agent

  • Check which early actions predict retention in our PostHog data and propose an activation definition.
  • Build a HogQL view that flags activation and time-to-activate, then roll up the rate by signup cohort.
  • Set up fct_user_activation in our dbt project with an account-level flag for the first days after signup.

How to install modeling-activation-metrics

1Skills CLI (Vercel)

npx skills add PostHog/ai-plugin --skill modeling-activation-metrics -a claude-code

2Manually: put the files in place

~/.claude/skills/modeling-activation-metrics/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/modeling-activation-metrics/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about modeling-activation-metrics

How do I install modeling-activation-metrics in Claude Code?

Run npx skills add PostHog/ai-plugin --skill modeling-activation-metrics -a claude-code. The skill file then sits at ~/.claude/skills/modeling-activation-metrics/SKILL.md.

What does modeling-activation-metrics do?

It turns activation into a reusable model: an activated flag per user or account plus an activation-rate metric, built on HogQL views or in a dbt project.

What does the skill need to work?

Read modeling-warehouse-foundations first for the mechanics; the retention validation comes from modeling-product-usage-metrics. The definition itself is derived from your own event data rather than taken as given.

Similar skills

All skills for Data and databases →

From the same set82

The whole set →
signals-scout-conversations The signals-scout-conversations skill checks PostHog Conversations analytics for SLA breaches, slow first replies, and support-queue imbalances. Use it to spot operational changes across tickets. CX Codex +1 183installs setting-up-data-catalog setting-up-data-catalog fills a project's data catalog: canonical metric definitions, trust marks on warehouse tables, and reviewed join proposals. CX Codex +1 182installs signals-scout-tasks signals-scout-tasks — a scout skill for PostHog Tasks: it tracks how task runs get delivered and, on a slower pass, looks for the same request coming up again in tasks people wrote. CX Codex +1 179installs managing-streamlit-apps managing-streamlit-apps controls Streamlit apps in PostHog sandboxes using MCP tools, handling everything from provisioning to safe code patching. CX Codex +1 179installs modeling-conversion-metrics modeling-conversion-metrics builds a reusable conversion model: funnel steps, a conversion window, drop-off and time to convert. Works on PostHog warehouse views in HogQL or in a dbt project. CX Codex +1 178installs writing-streamlit-apps The writing-streamlit-apps skill guides Python code for Streamlit apps that read PostHog data inside a sandbox. Use it when building or debugging dashboards with tables and charts. CX Codex +1 177installs modeling-revenue-metrics modeling-revenue-metrics builds reusable revenue models for MRR, ARR, churn, ARPU and LTV from PostHog views or dbt. Use it for revenue analysis by customer, product or period. CX Codex +1 175installs modeling-product-usage-metrics modeling-product-usage-metrics builds retention, frequency, and lifecycle models using PostHog HogQL views or dbt data marts with built-in tests. CX Codex +1 175installs

Project sponsors

Companies that keep this analytics open