Agent skill · software engineering · jeremylongshore
posthog-deploy-integration
Deploy a PostHog application integration with correct regional hosts, reverse-proxy coverage, server lifecycle, and rollback checks. Use when shipping PostHog instrumentation to a hosted application. Trigger with "deploy PostHog", "PostHog Vercel", or "PostHog reverse proxy".
Why this skill is useful
Adds deployment scripts and configuration patterns for PostHog on multiple platforms, which the AI wouldn't generate reliably on its own.
What it needs
Requires docker, gcloud, vercel 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 Deploy Integration Overview Ship an application's PostHog integration with regional routing, a supported reverse proxy, server-side flushing, validation evidence, and an instrumentation rollback. This workflow deploys the application integration; it does not present open-source self-hosting as a supported production PostHog service. Prerequisites PostHog project API key (phc...) A feature flags secure API key only when server-side local evaluation is required A scoped private-API credential only when deployment annotations are required Platform CLI installed (vercel, fly, or gcloud) Instructions Tool discipline Use Read to inspect the relevant configuration and implementation before proposing changes. Use Write only for a new, explicitly requested artifact inside the target project. Use Edit for minimal changes to existing project files after the evidence pass. Use the vercel, fly, or gcloud Bash allowance only for the deployment platform actually selected by the user. Step 1: Next.js + Vercel Deployment Step 2: Server-Side Capture in Vercel Edge Functions Step 3: Validate the Proxy and Rollback Boundary The rollback must disable the new SDK initialization or restore the previous proxy mapping without blocking the application. PostHog's open-source self-hosted distribution is explicitly a hobbyist, single-machine option with limited support and no recovery guarantee; evaluate it as a separate infrastructure project, not as a step in this application-deployment workflow. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/posthog-deploy-integration