posthog-instrumentation

Adds PostHog event tracking, feature flags, and user identification code to your app, using the right pattern for your language or framework.

WHEN TO USE

SCOPE

USE FOR

Add tracking for user actions like signups, clicks, or purchases as PostHog events.
Check a PostHog feature flag before rolling out a new feature to users.
Identify a logged-in user to PostHog with their ID and email.
Add PostHog event tracking and feature flags to a Python backend.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (5)

PostHog Instrumentation Skill

Help users add PostHog analytics, event tracking, and feature flags to their code.

When to Use

User asks to "add PostHog" or "add analytics"
User wants to track events or user actions
User needs to implement feature flags
User asks about instrumenting their code

Workflow

Identify the framework (React, Next.js, Python, Node.js, etc.)
Check for existing PostHog setup
Add appropriate instrumentation

Code Patterns

JavaScript/TypeScript

// Event tracking
posthog.capture('button_clicked', { button_name: 'signup' })

// Feature flags
if (posthog.isFeatureEnabled('new-feature')) {
  // Show new feature
}

// User identification
posthog.identify(userId, { email: user.email })

Python

from posthog import Posthog
posthog = Posthog(api_key='<ph_project_api_key>')

# Event tracking
posthog.capture(distinct_id='user_123', event='purchase_completed')

# Feature flags
if posthog.feature_enabled('new-feature', 'user_123'):
    # Show new feature

React

import { usePostHog } from 'posthog-js/react'

function MyComponent() {
  const posthog = usePostHog()

  const handleClick = () => {
    posthog.capture('button_clicked')
  }
}

Best Practices

Use consistent event naming (snake_case recommended)
Include relevant properties with events
Identify users early in their session
Use feature flags for gradual rollouts

Account or credentials required

1 FOR YOU

01
Get your PostHog project API key
Create or use an existing PostHog project and copy its project API key -- the tracking code initializes the client with it (e.g. Posthog(api_key='<ph_project_api_key>') in Python), so events have a project to send to.

Listed as free: Connected services may require an account or charge fees.

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add posthog/posthog-for-claude --skill "posthog-instrumentation" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

What's inside

Files included with this skill.

View on GitHub

PostHog Instrumentation Skill

When to Use

Workflow

Code Patterns

JavaScript/TypeScript

Python

React

Best Practices

Account or credentials required

What's inside

MCP keyword matches

YouTube MCP

Search Console & Analytics MCP

Microsoft Fabric Analytics

OP.GG