PostHog Handbook Library / Scaled Customer Success

2,164 words. Estimated reading time: 10 min.

Skills

Auto TL;DR

At a Glance

This long page covers these main areas. The list is generated from the article headings, so it updates with every handbook rebuild.

  1. Customer deep dive
  2. What it does
  3. What it produces
  4. When to use it
  5. Install
  6. Setup
  7. Running it
  8. Guardrails

These are the Claude skills the onboarding team has built for work we do over and over, like researching an account before we write to it or following up after a call. Each one drafts and never sends: whatever it writes lands with you to read, edit and send yourself.

| Skill | Use it for | Where it lives | Owner | |---|---|---|---| | Customer deep dive | Researching an account before an email, a reply or a call | PostHog/skills, as a Claude Code plugin | Daniel | | Customer call follow-up | The follow-up email after a customer call | The skills store on our internal PostHog project | Magda |

When you build a skill the rest of the team should use, add a row and a section here.

Customer deep dive

The customer deep dive is a Claude Code skill the onboarding team uses to research a PostHog account before emailing it, replying to it, or joining a call with it. You give it an email address or an account, it pulls everything PostHog knows about that account, and it hands back a draft email or a call-prep brief in chat for you to review.

It lives in the PostHog/skills repo, and the README there carries the full setup. This section covers what it does and how we use it.

What it does

The skill resolves whatever you hand it to an account in Customer Analytics, then reads the account across the sources onboarding already works from:

It runs these reads in parallel through subagents, reconciles what they return, and then checks every product claim it plans to make against a live search of the PostHog docs before it writes anything.

What it produces

The skill picks an output from the account's state. If you ask for something specific, your ask wins.

| Output | When | What you get | |---|---|---| | First-touch email | New account, nothing sent yet by hand or by the email sequence | Ranked contacts, cost-first findings, a short outreach email | | Follow-up email | We reached out, no reply | What changed since the last email, what they acted on, one or two new angles | | Reply | They wrote back with a question | Their questions answered in order, one paragraph each | | Call-prep brief | A real meeting is on the calendar | A full internal brief organized around what they said they want from the call, six optimization checks, health flags, and a ready-to-paste prompt for a PostHog AI notebook | | Account brief | We shouldn't be emailing this account: opted out, held by a CSM, AE or TAM, referred to sales, not eligible, or a teammate is already in touch | The research, the reason there's nothing to send, and who to loop in |

Every output starts with the same header: pipeline stage, what onboarding sent and when, health score, renewal date, last bill against the forecast, paid products, limits set and limits biting, the people on the account, user counts, and links to the org and the account.

Every recommendation in a customer-facing draft carries a link to the docs page it came from.

When to use it

You don't need it for a one-line nudge on a thread you already know well.

Install

It's a Claude Code plugin in the PostHog/skills repo. A copy also sits in the skills store of our internal PostHog project, which is what PostHog's own cloud runs, like the @PostHog Slack app, pick up for its owners. On your own machine, install the plugin. Pick one route, then restart Claude Code.

In a Claude Code session:

/plugin marketplace add PostHog/skills
/plugin marketplace update PostHog-skills
/plugin install posthog-customer-deep-dive@PostHog-skills

Three things trip people up. The marketplace name is PostHog-skills with the capitals. Run the update line even on a first install, since install reads your local cached copy of the marketplace. And nothing applies until you restart.

Or copy the folder instead:

git clone https://github.com/PostHog/skills.git
mkdir -p ~/.claude/skills
cp -r skills/skills/team/onboarding/posthog-customer-deep-dive ~/.claude/skills/

Updates are never automatic. The skill checks its own version against the published one at most once a day and prints the update commands when you're behind.

Setup

Two things are required:

  1. The PostHog MCP, signed in with your PostHog staff account. Register it with claude mcp add --transport http posthog https://mcp.posthog.com/mcp -s user, then run /mcp to log in (docs).
  2. Your own personal API keys, one on US and one on EU, read-only is enough (docs). US and EU are separate instances, so a US key won't work on EU. Without the EU key, EU accounts still run, but their raw event reads come back as unavailable instead of measured.

Make your own keys. A personal key carries the identity of whoever created it, so using a colleague's attributes your queries to them and gives you their access instead of yours.

Everything else is optional and gets skipped when it's set to none: Gong, your work calendar, Gmail, Clay, the GitHub CLI and Slack. On the first run the skill checks what you have, asks only for what it can't detect (your calendar ID and booking link), and writes your values to a personal config file outside the skill folder, so an update never overwrites them.

The README has a numbered section for each tool, each ending with a check that proves it works.

Running it

/posthog-customer-deep-dive someone@example.com

It also takes a domain, an account name, a PostHog org ID or a Customer Analytics account ID. Plain language works too: "prep me for my call with example.com tomorrow", "help me reply to this", "deep dive on example.com".

A typical call-prep run looks like this:

  1. You run it with the customer's email the day before the call.
  2. It resolves the account, reads the calendar invite for the booking-form answers, and fans out the reads.
  3. It splits whatever the customer said they want from the call into separate goals and writes a section per goal, in their words. A goal the data can't answer still gets a section saying what to ask on the call.
  4. It verifies each product claim against the docs, then writes the brief into chat, followed by a prompt you can paste into a PostHog AI notebook in the customer's project.
  5. A closing note lists what it skipped and why, and how many claims it checked against a fetched docs page.

Guardrails

Known limits

Who to ask

Daniel maintains the skill. Ask in #team-onboarding, or open an issue on the PostHog/skills repo. If you change a file in the skill, bump the version in .claude-plugin/plugin.json in the same PR, or nobody's installed copy will update.

Customer call follow-up

The customer call follow-up skill writes the email after a call. It turns the call transcript into a recap with the recording link, answers to the open questions and the docs the customer needs, and hands it over as a page you paste into Gmail.

What it does

What you get

A plain HTML page with the email on it. A note at the top lists the recipients, the subject (PostHog's meeting - summary) and every [link] placeholder you still fill in by hand, like the Gong share link for the recording. Select everything below the line, copy it, and paste it into a Gmail compose window. Pasting from the page keeps every link direct, where a Gmail draft would turn them into google.com redirects.

Setup

It's in the skills store on our internal PostHog project, and it runs in an agent with Granola, Gong, Google Calendar, Slack and the PostHog MCP connected. Gmail is optional and only adds context from earlier threads.

The booking link, the survey link, the videos and the sign-off are Magda's, so swap in your own before you use it.

Guardrails

Who to ask

Magda maintains the skill. Ask in #team-onboarding.

Canonical URL: https://posthog.com/handbook/scaled-customer-success/skills

GitHub source: contents/handbook/scaled-customer-success/skills.md

Content hash: a05e258e676a67e7