Agent skill · marketing growth · mvanhorn
pp-posthog
Every PostHog resource in one CLI — with offline search, agent-native output, and cross-resource analytics no... Trigger phrases: `check my PostHog feature flags`, `query PostHog events`, `show experiment results in PostHog`, `what errors are spiking in PostHog`, `LLM costs in PostHog`, `is it safe to ramp this flag`, `use posthog`.
Why this skill is useful
Adds multiple executable commands for PostHog analytics that provide unique insights not available through standard APIs.
What it needs
Requires posthog-pp-cli installed locally. About 7k tokens when loaded. Last updated 2026-08-06. 1,890 stars on the source repository.
What this skill does
PostHog — Printing Press CLI Prerequisites: Install the CLI This skill drives the posthog-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows: 2. Verify: posthog-pp-cli --version 3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill. If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer): If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds. When to Use This CLI Use posthog-pp-cli when an agent task requires querying, diffing, or combining PostHog data across more than one resource type — flag state vs error events, LLM costs vs variant performance, experiment exposure vs significance. It is faster than the web UI for bulk reads and produces structured JSON that agents can consume directly without parsing HTML. Unique Capabilities These capabilities aren't available in any other tool for this API. Flag safety flags blast-radius — Find every insight, dashboard, experiment, and survey that references a flag before you archive or rename it. Use before archiving or renaming a flag to prevent breaking dashboards and experiments silently. flags rollout-health — Go/no-go confidence for a flag ramp — error rate and key metric movement correlated with flag exposure. Use before ramping a flag to 100% to catch regressions that aren't visible in overall metrics. flags stale — List flags that haven't been evaluated in N days — cleanup candidates before they accumulate. Use in quarterly flag cleanup sprints to identify dead code paths safely. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mvanhorn/posthog