signals-scout-customer-analytics — Claude Code skill
The signals-scout-customer-analytics skill tracks account-level engagement in PostHog and spots churn-risk or expansion patterns. Use it for recurring customer-health checks.
no license 203 installs ★ 101 updated 2026-10-24
npx skills add PostHog/ai-plugin --skill signals-scout-customer-analytics -a claude-codeWhat signals-scout-customer-analytics does
The skill reviews PostHog Accounts data for changes in engagement at the organization level. It looks for a sharp activity drop, prolonged dormancy, a departing champion, and the reverse pattern that points to expansion. Each account is compared with its own recent baseline rather than with an aggregate number.
It works with system.accounts, group-keyed events, trend and stickiness queries, schema reads, and saved insights. A watchlist keeps account context between runs, while scratchpad entries hold working notes and confirmed findings go to the report channel. The account-to-event join is essential: if external_id does not match an event group key, the skill cannot score account engagement.
The setup targets the PostHog Signals agent in a Claude sandbox. Analytics are read-only, with write access used for the scratchpad and report channel. The skill also checks whether Customer analytics is in use before it evaluates the account roster.
What it helps with
- spot accounts whose engagement is falling
- find customers that have gone dormant
- detect the departure of an account champion
- surface accounts with rising product engagement
- verify account-to-event group-key matches
Example prompts for the agent
- Review account engagement for churn-risk patterns and report confirmed findings.
- Find dormant accounts or accounts that lost a key user.
- Compare each account with its recent baseline and refresh the watchlist.
How to install signals-scout-customer-analytics
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-customer-analytics -a claude-code2Manually: put the files in place
~/.claude/skills/signals-scout-customer-analytics/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/signals-scout-customer-analytics/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-customer-analytics -a codex2Manually: put the files in place
.agents/skills/signals-scout-customer-analytics/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-customer-analytics -a cursor2Manually: put the files in place
.cursor/skills/signals-scout-customer-analytics/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/ai-plugin skills/signals-scout-customer-analytics2Manually: put the files in place
.github/skills/signals-scout-customer-analytics/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-customer-analytics -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/ai-plugin --path skills/signals-scout-customer-analyticsManually: put the files in place
.devin/skills/signals-scout-customer-analytics/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-customer-analytics -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 signals-scout-customer-analytics
How do I install signals-scout-customer-analytics in Claude Code?
Run npx skills add PostHog/ai-plugin --skill signals-scout-customer-analytics -a claude-code, then check ~/.claude/skills/signals-scout-customer-analytics/SKILL.md.
What does signals-scout-customer-analytics do?
It monitors engagement for individual customer accounts and identifies activity cliffs, dormancy, champion departure, and expansion signals. Confirmed account-level findings are sent to the report channel.
What does the skill need to score an account?
It needs the PostHog Signals agent in a Claude sandbox and the Customer analytics tools. An account’s external_id must match a group key in the event stream for engagement scoring to work.