Agent skill · software engineering · jeremylongshore
posthog-prod-checklist
Run a fail-safe production-readiness review for PostHog instrumentation, flags, secrets, privacy, delivery, and rollback. Use when enabling a new production integration or major SDK change. Trigger with "PostHog production checklist", "PostHog go-live", or "review PostHog launch".
Why this skill is useful
Provides specific PostHog integration patterns and production readiness procedures that the AI wouldn't reliably generate on its own.
What it needs
Requires bash, curl, grep, kubectl installed locally. Requires posthog account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
PostHog Production Checklist Overview Production readiness verification for PostHog integrations. Covers SDK configuration hardening, graceful degradation when PostHog is unavailable, health check endpoints, proper shutdown hooks for serverless, and rollback procedures. Prerequisites PostHog integration tested in staging Production PostHog project with phc key Least-privilege private API credential only for the private operations the integration actually performs Deployment pipeline configured Instructions Tool discipline Use Read to inspect the relevant configuration and implementation before proposing changes. Use Grep to locate initialization, capture, flag, and credential boundaries. Pre-Deployment Checklist SDK Configuration: [ ] apihost set to correct region (us.i.posthog.com or eu.i.posthog.com) [ ] capturepageview: false if using SPA with manual pageview tracking [ ] capturepageleave: true for session duration accuracy [ ] Reverse proxy configured to bypass ad blockers (see posthog-sdk-patterns) [ ] posthog.debug() disabled in production (guarded by NODEENV) [ ] autocapture configured to exclude noisy elements Server-Side: [ ] posthog.shutdown() called in SIGTERM handler and serverless function cleanup [ ] Feature flags secure API key is passed through personalApiKey for server-side local evaluation [ ] flushAt and flushInterval tuned (default 20/10s is fine for most apps) Security: [ ] Personal API key (phx) never in client bundles or NEXTPUBLIC vars [ ] .env files in .gitignore [ ] Separate PostHog project per environment Step 1: Production SDK Configuration Step 2: Graceful Degradation Step 3: Health Check Endpoint Step 4: Serverless Function Pattern Step 5: Pre-Flight Verification Verify event delivery in a dedicated test project or with an explicitly approved synthetic production event. A 200 response confirms receipt and payload shape, not final ingestion; inspect quotalimited, ingestion warnings, and the resulting named event. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/posthog-prod-checklist