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
npx skills add PostHog/ai-plugin --skill modeling-activation-metrics -a claude-codeWhat 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_activationin 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-code2Manually: put the files in place
~/.claude/skills/modeling-activation-metrics/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/modeling-activation-metrics/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill modeling-activation-metrics -a codex2Manually: put the files in place
.agents/skills/modeling-activation-metrics/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill modeling-activation-metrics -a cursor2Manually: put the files in place
.cursor/skills/modeling-activation-metrics/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/ai-plugin skills/modeling-activation-metrics2Manually: put the files in place
.github/skills/modeling-activation-metrics/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill modeling-activation-metrics -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/ai-plugin --path skills/modeling-activation-metricsManually: put the files in place
.devin/skills/modeling-activation-metrics/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill modeling-activation-metrics -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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.