OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add posthog/skills --skill user-deep-dive
Deep dive on a PostHog user by email address. Analyze what they do, where they spend time, and what products they use.
npx skills add posthog/skills --skill user-deep-dive
Deep dive on a PostHog user by email address. Analyse what they do, where they spend time, and what products they use.
Input: $ARGUMENTS (email address, e.g. artis.conka@enlabs.com)
Before running any queries, ask the user:
"What time window would you like to analyse? (default: last 14 days)"
If they don't respond or say "default", use 14 days. Use their answer to set {days} in all queries below.
Run all of the following queries simultaneously via the query-run MCP tool.
1. Activity overview — event breakdown (excluding PostHog internals):
2. Page views — where they spend their time:
3. Insight details — which insights/dashboards they view:
4. Session replay views — replays they've watched:
5. Error tracking usage — how they interact with error tracking in PostHog:
6. PostHog AI usage — Max and insight analysis counts:
7. Where they open Max — which pages/contexts they use Max on:
Use Vitally tools to look up the user by email — get their role, title, account name, and any CRM data available.
2–3 sentences capturing who this person is, what they primarily use PostHog for, and the single most interesting or actionable thing about their usage. Write it as if briefing someone before a call with this user.
https://us.posthog.com/replay?filters={"type":"AND","values":[{"type":"AND","values":[{"key":"email","value":["{email}"],"operator":"exact","type":"person"}]}]}$conversations_loaded count) and make AI calls ($ai_generation count)?insight analyzed)?/dashboard/ → "dashboards", /sql → "SQL editor", /insights/ → "insights", /persons/ → "person profiles") and list the top contexts with counts. This tells us what they're trying to get help with.query-run tool, NOT curl. Fall back to curl only if MCP is unavailable.lastSeenTimestamp data is stale — do NOT rely on it for activity. Always use PostHog event data.SELECT properties.$current_url as url, count() as cnt
FROM events
WHERE person.properties.email = '{email}'
AND event = '$pageview'
AND timestamp >= now() - interval {days} day
GROUP BY url
ORDER BY cnt DESC
LIMIT 25SELECT properties.insight as insight_type, properties.insight_name as name, count() as views
FROM events
WHERE person.properties.email = '{email}'
AND event = 'insight viewed'
AND timestamp >= now() - interval {days} day
GROUP BY insight_type, name
ORDER BY views DESC
LIMIT 20SELECT
properties.session_id as session_id,
properties.$current_url as url,
timestamp
FROM events
WHERE person.properties.email = '{email}'
AND event = '$recording_viewed'
AND timestamp >= now() - interval {days} day
ORDER BY timestamp DESC
LIMIT 20SELECT event, properties.issue_id as issue_id, properties.issue_name as issue_name, count() as cnt
FROM events
WHERE person.properties.email = '{email}'
AND event IN ('error tracking issue viewed', 'error tracking issue resolved', 'error tracking issue assigned', 'error tracking issue suppressed', 'error tracking list viewed')
AND timestamp >= now() - interval {days} day
GROUP BY event, issue_id, issue_name
ORDER BY cnt DESC
LIMIT 20SELECT event, count() as cnt
FROM events
WHERE person.properties.email = '{email}'
AND event IN ('$ai_generation', '$conversations_loaded', 'insight analyzed', 'chat with data opened')
AND timestamp >= now() - interval {days} day
GROUP BY event
ORDER BY cnt DESCSELECT
properties.$current_url as url,
count() as cnt
FROM events
WHERE person.properties.email = '{email}'
AND event = '$conversations_loaded'
AND timestamp >= now() - interval {days} day
AND properties.$current_url LIKE '%posthog.com/project%'
GROUP BY url
ORDER BY cnt DESC
LIMIT 20