PostHog Skills

Why it's ranked here

The collection is unusually broad and operationally concrete. It covers more than integration setup, extending into experiments, replay, error tracking, signals, warehouses, and sales workflows. Automated discovery and synchronization reduce catalog drift. Its value is narrower for teams outside Claude Code or without the required PostHog access.

What's good

Skills can encode critical query rules, deduplication patterns, performance bounds, and safe mutation policies instead of offering vague prompting advice. The format separates agent instructions from optional documentation, executable helpers, and assets. Official material spans more than 30 frameworks and languages, while team and community tiers leave room for specialized workflows.

Tradeoffs

The documented installation surface centers on Claude Code, so portability to other agents is not established. Some workflows depend on PostHog MCP tools, customer project access, or external systems such as Salesforce. Much of the official and omnibus content is generated or synchronized automatically, meaning direct edits can be overwritten.

How to use it well

Use this when a team repeatedly asks Claude Code to implement, inspect, or operate PostHog and wants those procedures encoded consistently. Install focused plugins for bounded jobs, or the omnibus pack for broad product work. It does not replace PostHog credentials, MCP connectivity, human approval for mutations, or general analytics infrastructure.

Observed

License

MIT License

Install surface

Claude Code plugin marketplace or manual copying into a project skill directory

Content format

Markdown instructions with required YAML frontmatter

Interfaces

Claude Code plugins; some skills direct agents to PostHog MCP tools

Automation

Bash generation script and GitHub Actions workflows maintain the marketplace and omnibus collection

Library structure

System, official PostHog, team, community, and omnibus skill tiers are documented