posthog
194 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
posthogsignals-scout-experiments
Signals scout for PostHog A/B experiments. Watches running experiments for validity threats — sample ratio mismatch, contamination, exposure stalls, mid-run flag mutations — and lifecycle drift.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogsignals-scout-health-checks
Signals scout over PostHog's own health checks. Bundles the project's active health issues by kind, weights them by blast radius, and surfaces the ones worth acting on.
- installs
- 1
- GitHub stars
- 81
- Updated
- Sep 10
posthogsignals-scout-inbox-validation
Follow-up Signals scout for the inbox itself. Re-measures the problems behind recently resolved reports after a soak window and reports when a fix didn't hold, plus a gated escalation check on dismissed reports.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogsignals-scout-insight-alerts
Signals scout over the project's configured insight alerts. Reads each alert's recent firing history and surfaces the firings a human likely missed.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogsignals-scout-mcp-tool-calls
Signals scout for PostHog MCP tool calls. Watches $mcptoolcall telemetry for tools that need improvement — broad-reach failure rates, retry hammering, slow or context-bloating responses — grouped by owning product category, each with a fix suggestion.
- installs
- 1
- GitHub stars
- 81
- Updated
- Sep 10
posthogsignals-scout-replay-vision
Signals scout for PostHog Replay Vision scanners. Watches that enabled scanners keep observing (throughput and quota cliffs) and that aggregate score shifts and recurring themes get surfaced.
- installs
- 1
- GitHub stars
- 81
- Updated
- Sep 10
posthogsignals-scout-skills-store
Skill-hygiene scout for the team's PostHog skills store. Watches recently-changed and most- used skills for authoring violations — vague descriptions, bloated bodies, dead file links, kitchen-sink scope, committed secrets.
- installs
- 1
- GitHub stars
- 81
- Updated
- Sep 10
posthogsignals-scout-tasks
Signals scout for PostHog Tasks. Watches delivery health — failing runs clustered by repository and error class, retry storms — and, on a slower rotation, recurring demand across human-authored tasks. Skips the scout fleet's own runs.
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogsuggesting-data-imports
Use when the user asks about revenue, payments, subscriptions, billing, CRM deals, support tickets, ad spend, production database tables, or other data PostHog does not collect natively — or wants to join or correlate PostHog product events with that external business data. Also use when a query fails because a table does not exist or returns no results for expected external data. The data warehouse can import from SaaS tools (Stripe, Hubspot, Zendesk, etc.), ad platforms, production databases (
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogsuppressing-noisy-errors
Create PostHog error tracking suppression rules to drop high-volume, low-value errors at ingestion. Use when the user asks "stop capturing this error", "drop browser extension errors", "ignore ResizeObserver loops", "suppress bot-driven errors", or wants to reduce ingestion cost from noisy unactionable errors. Identifies suppression candidates, scopes the filter tightly, decides between full suppression and sampling, and confirms the rule before creating it. Suppressed errors are dropped permane
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogtriaging-error-issues
Triage PostHog error tracking issues during a daily or on-call review. Use when the user asks "what's broken?", "what new errors do we have?", "show me top errors today", "what should I look at this morning", or wants a prioritized list of active issues to work on. Surfaces new and high-impact issues, ranks by users affected and recency, points at linked replays, and proposes next actions (investigate, assign, suppress, merge).
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogturning-engineering-analytics-into-insights
Converts engineering analytics (PR / CI) data into saved PostHog insights, dashboards, and subscriptions, and explains how to query the product data directly with SQL. Covers discovering per-team GitHub warehouse tables via engineering-analytics-sources, replicating curated column semantics in HogQL, reading exposed engineeringanalytics warehouse views where product logic is involved (CI cost, fingerprinted failure lines, commit attribution), saving queries with insight-create, and scheduling de
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogunderstanding-billing-usage
Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exception
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogvalidating-and-publishing-canvases
Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expectedcurrentversionid, staging a draft build and promoting it, waiting out the queued build, and recovering from a 409 versionconflict or a 429 capacity limit without overwriting concurrent work. Use whenever a canvas edit is ready to save, a draft build is wanted, a canvas publish or build retur
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogwriting-simplified-technical-english
Write English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard written for aircraft maintenance manuals. Use it for any prose an agent produces that someone else acts on. That covers reports and findings, PR descriptions and commit messages, instructions handed to another agent, tool descriptions, error messages, status summaries, and prompt
- installs
- 1
- GitHub stars
- 80
- Updated
- Sep 4
posthogwriting-streamlit-apps
Write Streamlit app source code that runs well in a PostHog sandbox — the posthogapps.query() bridge for reading PostHog data, the packages baked into the sandbox image, caching and session state across Streamlit reruns, layout and chart patterns, and the app.py entry point with any helper modules and data files bundled beside it. Use when authoring or debugging the Python source of a PostHog Streamlit app, when a query inside an app fails, or when asked to "write a streamlit app that shows Post
- installs
- 1
- GitHub stars
- 81
- Updated
- Sep 10
posthogadding-personhog-rpc
Guide for adding a new RPC to personhog-replica and personhog-router. Covers eligibility checks, proto definition, code generation for Python and Node.js clients, Rust implementation (storage trait, postgres queries, service handler, router wiring), and index compatibility validation. Use when adding a new gRPC endpoint to personhog, migrating a Django ORM query to personhog, or extending the personhog service API.
- installs
- 1
- GitHub stars
- 40.2K
- Updated
- Oct 8
posthogadding-project-secret-api-key-auth
How to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential. Use when adding PSAK support to a viewset action, allowing a new scope for PSAKs, handling synthetic users (ProjectSecretAPIKeyUser), or choosing PSAK-aware rate throttles. Trigger terms: PSAK, ProjectSecretAPIKey, project secret API key, phs token, service auth, programmatic endpoint auth.
- installs
- 1
- GitHub stars
- 40.2K
- Updated
- Oct 8
posthogadopting-generated-api-types
Use when migrating frontend code from manual API client calls (api.get, api.create, api.surveys.get, api.dashboards.list, new ApiRequest()) and handwritten TypeScript interfaces to generated API functions and types. Triggers on files importing from lib/api, files with api.get . , manual interface definitions that duplicate backend serializers, or any frontend file that constructs API URLs by hand. Covers the full replacement workflow — finding the generated equivalent, swapping imports, adapting
- installs
- 1
- GitHub stars
- 40.2K
- Updated
- Oct 8
posthogdepot-container-builds
Configures and runs Depot remote container builds using depot build and depot bake. Use when building Docker images, creating Dockerfiles with Depot, pushing images to registries, building multi-platform/multi-arch images (linux/amd64, linux/arm64), debugging container build failures, optimizing Dockerfile layer caching, using docker-bake.hcl or docker-compose builds, or migrating from docker build / docker buildx build to Depot. Also use when the user mentions depot build, depot bake, container
- installs
- 1
- GitHub stars
- 40.2K
- Updated
- Oct 8
posthogdepot-github-runners
Configures Depot-managed GitHub Actions runners as a drop-in replacement for GitHub-hosted runners. Use when setting up or migrating GitHub Actions workflows to use Depot runners, choosing runner sizes (CPU/RAM), configuring runs-on labels, setting up ARM or Windows or macOS runners, troubleshooting GitHub Actions runner issues, configuring egress filtering, using Depot Cache with GitHub Actions, or running Dagger/Dependabot on Depot runners. Also use when the user mentions depot-ubuntu, depot-w
- installs
- 1
- GitHub stars
- 40.2K
- Updated
- Oct 8
posthogdjango-migrations
Django migration patterns and safety workflow for PostHog. Use when creating, adjusting, or reviewing Django/Postgres migrations, including non-blocking index/constraint changes, multi-phase schema changes, data backfills, migration conflict rebasing, and product model moves that require SeparateDatabaseAndState. Also use for any deletion or removal of a model, table, column, product, or app — including deleting migration files or retiring a feature — even when no migration is written.
- installs
- 1
- GitHub stars
- 40.2K
- Updated
- Oct 8
posthogdjango-startup-time
Keep heavy imports off the django.setup() path that every process (web, celery, temporal, migrate, shell, CI) pays for. Use when touching AppConfig.ready(), wiring signal receivers, editing the lazy API router (posthog/api/restrouter.py or its init.py shim), deferring a heavy import or profiling import time (importtime, hothog), when the startup-import-budget guard fails, or when merging master into a long-lived branch that made the router lazy.
- installs
- 1
- GitHub stars
- 40.2K
- Updated
- Oct 8
posthogdocumenting-warehouse-sources
Write or update the user-facing posthog.com documentation for a PostHog Data warehouse import source. Use when adding a new source doc, fixing an inconsistent or stub source doc, or standardizing the docs at contents/docs/cdp/sources. Covers the canonical template, shared snippets, the auto-rendered and components, frontmatter, and the docsUrl/slug rule that prevents 404s.
- installs
- 1
- GitHub stars
- 40.2K
- Updated
- Oct 8