Repository navigation
feat(skills): add instrument-reverse-proxy skill - #512
Merged
Merged
Conversation
Agents that install PostHog had no skill for a reverse proxy. In a trial of `hog setup`, `hog skills search reverse proxy` matched nothing useful, so the agent fetched posthog.com docs with curl and never found the managed proxy's API tools (`proxy-create` and friends). The new omnibus skill picks between a self-hosted proxy and PostHog's managed proxy. It prefers self-hosted where the platform makes it a small change (Next.js, Nuxt, SvelteKit, Remix, Cloudflare, Vercel, Netlify, or an nginx/Caddy/ingress config already in the repo), and the managed proxy elsewhere, with a trade-offs table from the proxy docs. It runs only when the user asks for a proxy or agrees to one. - The managed path uses the proxy-* API tools, which work through the MCP server and `hog api call`. It confirms the subdomain first, and doesn't switch `api_host` until the proxy is `valid` - Verification uses `/array/<token>/config.js` and `/flags`, which write no events - New `reverse-proxy` commandments: region routing, `ui_host`, the self-hosted header checklist, and the managed proxy rules - instrument-integration, instrument-product-analytics and instrument-error-tracking name the skill where they suggest a proxy Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Test against a wizard branch:
Add Results will be posted here when complete. |
gewenyu99
approved these changes
Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Agents that install PostHog had no skill for a reverse proxy. In a trial of
hog setupwith Claude Code, the user asked for a proxy afterwards.hog skills search reverse proxyreturned only replay-debugging skills, so the agent fetched posthog.com docs with curl and wrote a Cloudflare Worker by hand. It never found the managed proxy's API tools (proxy-create,proxy-get,proxy-diagnose, …), whichhog apiand the MCP server already expose.Changes
New omnibus skill
instrument-reverse-proxy(context/skills/omnibus/instrument-reverse-proxy/), with the proxy overview and every platform page from posthog.com/docs/advanced/proxy as references.proxy-*API tools, which work through the MCPexectool andhog api call. It checksproxy-listfirst, confirms the subdomain with the user beforeproxy-create, gives the exact CNAME, and usesproxy-diagnose/proxy-retrywhen provisioning fails. It doesn't switchapi_hostuntil the status isvalid. Until then it makes the host configurable and leaves the default pointing at PostHog.posthog.json, or the currentapi_host, and otherwise asks. It never assumes US./array/<token>/config.jsand/flags, which write no events. It warns that posthog-js's bot filter drops captures in automated browsers.New
reverse-proxycommandments: region routing,ui_host, the self-hosted header and body-size checklist from the proxy reference, and the two managed proxy rules. The skill also carriesjavascript_web.Links from the install skills.
instrument-integration,instrument-product-analyticsandinstrument-error-trackingnow name the new skill where they already suggest a proxy in the final message.How I tested it
npm test: 321 tests pass.npm run build: emitsomnibus-instrument-reverse-proxy.zip(SKILL.md, COMMANDMENTS.md, 17 references) and puts it inskills-mcp-resources.zip.POSTHOG_MCP_LOCAL_SKILLS_URL).hog skills listshowsinstrument-reverse-proxyunder implementation, it is the top result forhog skills search reverse proxy, andhog skills read instrument-reverse-proxy --file references/cloudflare.mdworks.Not in this PR
evals/install-skills.instrument-integrationstill says to set up a proxy during install when the framework reference documents one. I left that unchanged because it is existing wizard behavior.🤖 Generated with Claude Code