[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-verify-posthog-instrumentation":3,"mdc--gtcz1t-key":51,"related-repo-posthog-verify-posthog-instrumentation":384,"related-org-posthog-verify-posthog-instrumentation":485},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":46,"sourceUrl":49,"mdContent":50},"verify-posthog-instrumentation","verify PostHog instrumentation on websites","Use this skill to verify that PostHog instrumentation is firing correctly on a website. Drives a real browser at one or more URLs, observes which PostHog events actually arrive, and reports a pass\u002Ffail summary. Use after installing the PostHog SDK on a site, after a deploy that touches tracking code, or when events appear missing in the PostHog dashboard.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"posthog","PostHog","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fposthog.png",[12,16,17,20,23],{"name":13,"slug":14,"type":15},"Observability","observability","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"QA","qa",{"name":21,"slug":22,"type":15},"Analytics","analytics",{"name":24,"slug":25,"type":15},"Testing","testing",35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-05-07T05:56:18.587913",null,2977,[32,33,22,34,35,36,37,38,39,40,41,42,43,44,45],"ab-testing","ai-analytics","cdp","data-warehouse","experiments","feature-flags","javascript","product-analytics","python","react","session-replay","surveys","typescript","web-analytics",{"repoUrl":27,"stars":26,"forks":30,"topics":47,"description":48},[32,33,22,34,35,36,37,38,39,40,41,42,43,44,45],"🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog\u002Ftree\u002FHEAD\u002Ftools\u002Ftraffic-sim\u002Fskills\u002Fverify-posthog-instrumentation","---\nname: verify-posthog-instrumentation\ndescription: >\n  Use this skill to verify that PostHog instrumentation is firing correctly on\n  a website. Drives a real browser at one or more URLs, observes which PostHog\n  events actually arrive, and reports a pass\u002Ffail summary. Use after installing\n  the PostHog SDK on a site, after a deploy that touches tracking code, or when\n  events appear missing in the PostHog dashboard.\n---\n\n# Verify PostHog instrumentation\n\nEnd-to-end check that the PostHog SDK is loaded and emitting events as expected.\nThis skill orchestrates the three traffic-sim tools to give a complete picture\nof a site's instrumentation health.\n\n## When to use\n\n- After running `npx @posthog\u002Fwizard` to confirm the install actually works.\n- After a deploy that touches analytics, tracking, or layout code.\n- When a customer reports \"I'm not seeing events in PostHog\" — to disambiguate\n  between snippet issues, network issues, or filtering issues.\n- As a smoke test before launching a new site or marketing page.\n\n## Workflow\n\n### Step 1 — Confirm the snippet is loaded everywhere\n\nRun the `check_posthog_loading` MCP tool against the URLs you care about\n(homepage, key product pages, login, checkout, marketing pages). It returns\nwhich pages have PostHog initialized, the load method (head_snippet \u002F snippet\n\u002F array_js_only), and the init config.\n\nLook for:\n\n- Pages where `loaded: false` — PostHog is missing from those pages.\n- Inconsistent `api_key` values across pages — multiple projects in use.\n- Inconsistent `api_host` values across pages — events going to different ingestion endpoints.\n\n### Step 2 — Send synthetic traffic and confirm events arrive\n\nPick one URL where Step 1 confirmed PostHog is loaded. Call:\n\n- `simulate_new_user` — a few fresh-browser visits. Confirms `$pageview`\n  fires for first-time visitors and that an anonymous distinct_id is assigned.\n- `simulate_returning_user` — a few page views in a single session. Confirms\n  cookies persist and `$pageview` keeps firing across navigations.\n\nThe tools return `verified: true` when at least one `$pageview` was captured\nand there were no errors.\n\n### Step 3 — Cross-check in PostHog\n\nIf Steps 1 and 2 pass but events don't show up in the PostHog UI, the issue\nis downstream of the snippet:\n\n- Check for ingestion lag (events can take ~30s to appear).\n- Check that the `api_host` matches the project's ingestion host.\n- Check feature flag and ingestion warnings in the PostHog UI.\n\n## What \"verified\" means in this skill\n\nA site is verified when:\n\n1. `check_posthog_loading` reports `loaded: true` on every URL we expect.\n2. `simulate_new_user` and `simulate_returning_user` both return at least one\n   `$pageview` event per visit, with no errors.\n3. (Optional) The events appear in the PostHog UI within 1-2 minutes.\n\n## What this skill does not check\n\n- Whether your custom events (e.g. `signup_completed`) are being sent —\n  the tool watches for any PostHog event, but you'd need to drive the actual\n  user flow to see custom events fire. Use it as a starting point, then add\n  user-flow simulation on top.\n- Server-side ingestion. The tool only sees what the browser SDK sends.\n- Session recording quality. The tool reports whether recording is enabled\n  in the init config but doesn't validate the recording itself.\n",{"data":52,"body":53},{"name":4,"description":6},{"type":54,"children":55},"root",[56,64,70,77,111,117,124,137,142,183,189,194,234,254,260,265,290,296,301,352,358],{"type":57,"tag":58,"props":59,"children":60},"element","h1",{"id":4},[61],{"type":62,"value":63},"text","Verify PostHog instrumentation",{"type":57,"tag":65,"props":66,"children":67},"p",{},[68],{"type":62,"value":69},"End-to-end check that the PostHog SDK is loaded and emitting events as expected.\nThis skill orchestrates the three traffic-sim tools to give a complete picture\nof a site's instrumentation health.",{"type":57,"tag":71,"props":72,"children":74},"h2",{"id":73},"when-to-use",[75],{"type":62,"value":76},"When to use",{"type":57,"tag":78,"props":79,"children":80},"ul",{},[81,96,101,106],{"type":57,"tag":82,"props":83,"children":84},"li",{},[85,87,94],{"type":62,"value":86},"After running ",{"type":57,"tag":88,"props":89,"children":91},"code",{"className":90},[],[92],{"type":62,"value":93},"npx @posthog\u002Fwizard",{"type":62,"value":95}," to confirm the install actually works.",{"type":57,"tag":82,"props":97,"children":98},{},[99],{"type":62,"value":100},"After a deploy that touches analytics, tracking, or layout code.",{"type":57,"tag":82,"props":102,"children":103},{},[104],{"type":62,"value":105},"When a customer reports \"I'm not seeing events in PostHog\" — to disambiguate\nbetween snippet issues, network issues, or filtering issues.",{"type":57,"tag":82,"props":107,"children":108},{},[109],{"type":62,"value":110},"As a smoke test before launching a new site or marketing page.",{"type":57,"tag":71,"props":112,"children":114},{"id":113},"workflow",[115],{"type":62,"value":116},"Workflow",{"type":57,"tag":118,"props":119,"children":121},"h3",{"id":120},"step-1-confirm-the-snippet-is-loaded-everywhere",[122],{"type":62,"value":123},"Step 1 — Confirm the snippet is loaded everywhere",{"type":57,"tag":65,"props":125,"children":126},{},[127,129,135],{"type":62,"value":128},"Run the ",{"type":57,"tag":88,"props":130,"children":132},{"className":131},[],[133],{"type":62,"value":134},"check_posthog_loading",{"type":62,"value":136}," MCP tool against the URLs you care about\n(homepage, key product pages, login, checkout, marketing pages). It returns\nwhich pages have PostHog initialized, the load method (head_snippet \u002F snippet\n\u002F array_js_only), and the init config.",{"type":57,"tag":65,"props":138,"children":139},{},[140],{"type":62,"value":141},"Look for:",{"type":57,"tag":78,"props":143,"children":144},{},[145,158,171],{"type":57,"tag":82,"props":146,"children":147},{},[148,150,156],{"type":62,"value":149},"Pages where ",{"type":57,"tag":88,"props":151,"children":153},{"className":152},[],[154],{"type":62,"value":155},"loaded: false",{"type":62,"value":157}," — PostHog is missing from those pages.",{"type":57,"tag":82,"props":159,"children":160},{},[161,163,169],{"type":62,"value":162},"Inconsistent ",{"type":57,"tag":88,"props":164,"children":166},{"className":165},[],[167],{"type":62,"value":168},"api_key",{"type":62,"value":170}," values across pages — multiple projects in use.",{"type":57,"tag":82,"props":172,"children":173},{},[174,175,181],{"type":62,"value":162},{"type":57,"tag":88,"props":176,"children":178},{"className":177},[],[179],{"type":62,"value":180},"api_host",{"type":62,"value":182}," values across pages — events going to different ingestion endpoints.",{"type":57,"tag":118,"props":184,"children":186},{"id":185},"step-2-send-synthetic-traffic-and-confirm-events-arrive",[187],{"type":62,"value":188},"Step 2 — Send synthetic traffic and confirm events arrive",{"type":57,"tag":65,"props":190,"children":191},{},[192],{"type":62,"value":193},"Pick one URL where Step 1 confirmed PostHog is loaded. Call:",{"type":57,"tag":78,"props":195,"children":196},{},[197,216],{"type":57,"tag":82,"props":198,"children":199},{},[200,206,208,214],{"type":57,"tag":88,"props":201,"children":203},{"className":202},[],[204],{"type":62,"value":205},"simulate_new_user",{"type":62,"value":207}," — a few fresh-browser visits. Confirms ",{"type":57,"tag":88,"props":209,"children":211},{"className":210},[],[212],{"type":62,"value":213},"$pageview",{"type":62,"value":215},"\nfires for first-time visitors and that an anonymous distinct_id is assigned.",{"type":57,"tag":82,"props":217,"children":218},{},[219,225,227,232],{"type":57,"tag":88,"props":220,"children":222},{"className":221},[],[223],{"type":62,"value":224},"simulate_returning_user",{"type":62,"value":226}," — a few page views in a single session. Confirms\ncookies persist and ",{"type":57,"tag":88,"props":228,"children":230},{"className":229},[],[231],{"type":62,"value":213},{"type":62,"value":233}," keeps firing across navigations.",{"type":57,"tag":65,"props":235,"children":236},{},[237,239,245,247,252],{"type":62,"value":238},"The tools return ",{"type":57,"tag":88,"props":240,"children":242},{"className":241},[],[243],{"type":62,"value":244},"verified: true",{"type":62,"value":246}," when at least one ",{"type":57,"tag":88,"props":248,"children":250},{"className":249},[],[251],{"type":62,"value":213},{"type":62,"value":253}," was captured\nand there were no errors.",{"type":57,"tag":118,"props":255,"children":257},{"id":256},"step-3-cross-check-in-posthog",[258],{"type":62,"value":259},"Step 3 — Cross-check in PostHog",{"type":57,"tag":65,"props":261,"children":262},{},[263],{"type":62,"value":264},"If Steps 1 and 2 pass but events don't show up in the PostHog UI, the issue\nis downstream of the snippet:",{"type":57,"tag":78,"props":266,"children":267},{},[268,273,285],{"type":57,"tag":82,"props":269,"children":270},{},[271],{"type":62,"value":272},"Check for ingestion lag (events can take ~30s to appear).",{"type":57,"tag":82,"props":274,"children":275},{},[276,278,283],{"type":62,"value":277},"Check that the ",{"type":57,"tag":88,"props":279,"children":281},{"className":280},[],[282],{"type":62,"value":180},{"type":62,"value":284}," matches the project's ingestion host.",{"type":57,"tag":82,"props":286,"children":287},{},[288],{"type":62,"value":289},"Check feature flag and ingestion warnings in the PostHog UI.",{"type":57,"tag":71,"props":291,"children":293},{"id":292},"what-verified-means-in-this-skill",[294],{"type":62,"value":295},"What \"verified\" means in this skill",{"type":57,"tag":65,"props":297,"children":298},{},[299],{"type":62,"value":300},"A site is verified when:",{"type":57,"tag":302,"props":303,"children":304},"ol",{},[305,323,347],{"type":57,"tag":82,"props":306,"children":307},{},[308,313,315,321],{"type":57,"tag":88,"props":309,"children":311},{"className":310},[],[312],{"type":62,"value":134},{"type":62,"value":314}," reports ",{"type":57,"tag":88,"props":316,"children":318},{"className":317},[],[319],{"type":62,"value":320},"loaded: true",{"type":62,"value":322}," on every URL we expect.",{"type":57,"tag":82,"props":324,"children":325},{},[326,331,333,338,340,345],{"type":57,"tag":88,"props":327,"children":329},{"className":328},[],[330],{"type":62,"value":205},{"type":62,"value":332}," and ",{"type":57,"tag":88,"props":334,"children":336},{"className":335},[],[337],{"type":62,"value":224},{"type":62,"value":339}," both return at least one\n",{"type":57,"tag":88,"props":341,"children":343},{"className":342},[],[344],{"type":62,"value":213},{"type":62,"value":346}," event per visit, with no errors.",{"type":57,"tag":82,"props":348,"children":349},{},[350],{"type":62,"value":351},"(Optional) The events appear in the PostHog UI within 1-2 minutes.",{"type":57,"tag":71,"props":353,"children":355},{"id":354},"what-this-skill-does-not-check",[356],{"type":62,"value":357},"What this skill does not check",{"type":57,"tag":78,"props":359,"children":360},{},[361,374,379],{"type":57,"tag":82,"props":362,"children":363},{},[364,366,372],{"type":62,"value":365},"Whether your custom events (e.g. ",{"type":57,"tag":88,"props":367,"children":369},{"className":368},[],[370],{"type":62,"value":371},"signup_completed",{"type":62,"value":373},") are being sent —\nthe tool watches for any PostHog event, but you'd need to drive the actual\nuser flow to see custom events fire. Use it as a starting point, then add\nuser-flow simulation on top.",{"type":57,"tag":82,"props":375,"children":376},{},[377],{"type":62,"value":378},"Server-side ingestion. The tool only sees what the browser SDK sends.",{"type":57,"tag":82,"props":380,"children":381},{},[382],{"type":62,"value":383},"Session recording quality. The tool reports whether recording is enabled\nin the init config but doesn't validate the recording itself.",{"items":385,"total":484},[386,399,411,423,436,451,467],{"slug":387,"name":387,"fn":388,"description":389,"org":390,"tags":391,"stars":26,"repoUrl":27,"updatedAt":398},"analyzing-expensive-users","analyze expensive users in AI observability","Analyze the most expensive users in AI observability and explain why they cost so much. Use when the user asks about top spenders, expensive users, per-user LLM cost, user-level cost drivers, or patterns behind high AI observability spend.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[392,393,396,397],{"name":21,"slug":22,"type":15},{"name":394,"slug":395,"type":15},"Cost Optimization","cost-optimization",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-07-28T05:34:11.117757",{"slug":400,"name":400,"fn":401,"description":402,"org":403,"tags":404,"stars":26,"repoUrl":27,"updatedAt":410},"auditing-endpoints","audit PostHog project endpoints","Audit every endpoint in a PostHog project for staleness, failed materialisations, and unused materialised versions. Use when the user asks \"what endpoints can I clean up?\", \"are any of my endpoints broken?\", \"which materialised versions are still being called?\", or wants a one-shot cleanup pass over the Endpoints product. Produces a prioritised report grouped by issue type, with recommended actions but does not modify anything without explicit confirmation.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[405,406,409],{"name":21,"slug":22,"type":15},{"name":407,"slug":408,"type":15},"Audit","audit",{"name":9,"slug":8,"type":15},"2026-06-08T08:08:33.693989",{"slug":412,"name":412,"fn":413,"description":414,"org":415,"tags":416,"stars":26,"repoUrl":27,"updatedAt":422},"auditing-warehouse-source-health","audit PostHog data warehouse source health","Audit the health of a PostHog project's data warehouse sources and syncs — find every broken or degraded source connection, sync schema, and webhook channel. Use when the user asks \"why are my imports failing?\", \"what's broken with my sources?\", \"why is my warehouse data stale?\", or wants a one-shot triage of source\u002Fsync health before deciding where to dig in. Produces a prioritized report grouped by severity, with recommended next steps. For materialized-view health use `auditing-warehouse-view-health`; for a single failing sync use `diagnosing-failed-warehouse-syncs`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[417,418,420,421],{"name":407,"slug":408,"type":15},{"name":419,"slug":35,"type":15},"Data Warehouse",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:22:57.67984",{"slug":424,"name":424,"fn":425,"description":426,"org":427,"tags":428,"stars":26,"repoUrl":27,"updatedAt":435},"auditing-warehouse-view-health","audit PostHog materialized view health","Audit the health of a PostHog project's materialized views (saved queries) — find every failed materialization and flag unused or stale materialized views that cost storage and compute. Use when the user asks \"which of my views are broken?\", \"why is this materialized view failing?\", \"are any of my views wasting compute?\", or wants a one-shot triage of view health. For source\u002Fsync health use `auditing-warehouse-source-health`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[429,430,431,434],{"name":407,"slug":408,"type":15},{"name":419,"slug":35,"type":15},{"name":432,"slug":433,"type":15},"Performance","performance",{"name":9,"slug":8,"type":15},"2026-06-18T08:25:10.936787",{"slug":437,"name":437,"fn":438,"description":439,"org":440,"tags":441,"stars":26,"repoUrl":27,"updatedAt":450},"authoring-error-tracking-alerts","author PostHog error tracking alerts","Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack\u002Fwebhook\u002FLinear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedup against existing alerts, and shipping with the canonical message body shape.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[442,445,448,449],{"name":443,"slug":444,"type":15},"Alerting","alerting",{"name":446,"slug":447,"type":15},"Debugging","debugging",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:24:40.318583",{"slug":452,"name":452,"fn":453,"description":454,"org":455,"tags":456,"stars":26,"repoUrl":27,"updatedAt":466},"authoring-log-alerts","author log alerts in PostHog","Author useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[457,458,461,462,465],{"name":21,"slug":22,"type":15},{"name":459,"slug":460,"type":15},"Monitoring","monitoring",{"name":13,"slug":14,"type":15},{"name":463,"slug":464,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-07-18T05:10:54.430898",{"slug":468,"name":468,"fn":469,"description":470,"org":471,"tags":472,"stars":26,"repoUrl":27,"updatedAt":483},"building-workflows","build and edit PostHog workflows","Build, edit, test, enable, and monitor PostHog workflows over MCP. Author the action\u002Fedge graph so it runs and opens cleanly in the visual editor, then change drafts surgically with patch operations. Use when asked to build, set up, automate, change, fix, or debug a workflow, campaign, broadcast, drip sequence, or event-triggered automation in the workflows product.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[473,476,479,480],{"name":474,"slug":475,"type":15},"Automation","automation",{"name":477,"slug":478,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},{"name":481,"slug":482,"type":15},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",61,{"items":486,"total":603},[487,494,500,507,514,521,529,536,550,565,575,593],{"slug":387,"name":387,"fn":388,"description":389,"org":488,"tags":489,"stars":26,"repoUrl":27,"updatedAt":398},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[490,491,492,493],{"name":21,"slug":22,"type":15},{"name":394,"slug":395,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},{"slug":400,"name":400,"fn":401,"description":402,"org":495,"tags":496,"stars":26,"repoUrl":27,"updatedAt":410},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[497,498,499],{"name":21,"slug":22,"type":15},{"name":407,"slug":408,"type":15},{"name":9,"slug":8,"type":15},{"slug":412,"name":412,"fn":413,"description":414,"org":501,"tags":502,"stars":26,"repoUrl":27,"updatedAt":422},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[503,504,505,506],{"name":407,"slug":408,"type":15},{"name":419,"slug":35,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},{"slug":424,"name":424,"fn":425,"description":426,"org":508,"tags":509,"stars":26,"repoUrl":27,"updatedAt":435},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[510,511,512,513],{"name":407,"slug":408,"type":15},{"name":419,"slug":35,"type":15},{"name":432,"slug":433,"type":15},{"name":9,"slug":8,"type":15},{"slug":437,"name":437,"fn":438,"description":439,"org":515,"tags":516,"stars":26,"repoUrl":27,"updatedAt":450},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[517,518,519,520],{"name":443,"slug":444,"type":15},{"name":446,"slug":447,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},{"slug":452,"name":452,"fn":453,"description":454,"org":522,"tags":523,"stars":26,"repoUrl":27,"updatedAt":466},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[524,525,526,527,528],{"name":21,"slug":22,"type":15},{"name":459,"slug":460,"type":15},{"name":13,"slug":14,"type":15},{"name":463,"slug":464,"type":15},{"name":9,"slug":8,"type":15},{"slug":468,"name":468,"fn":469,"description":470,"org":530,"tags":531,"stars":26,"repoUrl":27,"updatedAt":483},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[532,533,534,535],{"name":474,"slug":475,"type":15},{"name":477,"slug":478,"type":15},{"name":9,"slug":8,"type":15},{"name":481,"slug":482,"type":15},{"slug":537,"name":537,"fn":538,"description":539,"org":540,"tags":541,"stars":26,"repoUrl":27,"updatedAt":549},"check-posthog-loading","inspect PostHog SDK loading across URLs","Inspect how the PostHog JavaScript SDK is loaded across a list of URLs. Use to confirm consistent installation across pages, find pages missing the snippet, detect mismatched API keys or hosts between pages, and verify the load method (head snippet vs deferred vs array.js).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[542,543,544,547,548],{"name":21,"slug":22,"type":15},{"name":446,"slug":447,"type":15},{"name":545,"slug":546,"type":15},"Frontend","frontend",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-05-07T05:56:19.828048",{"slug":551,"name":551,"fn":552,"description":553,"org":554,"tags":555,"stars":26,"repoUrl":27,"updatedAt":564},"consuming-endpoints-from-client-code","integrate PostHog endpoints into client applications","Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api\u002Fopenapi-ts, sending the right auth header, shaping the variables payload (HogQL code_name vs insight breakdown property), handling rate-limit and materialised-endpoint error responses. Use when the user says \"how do I call my endpoint\", \"generate a client for this\", or \"what auth header do I use\".\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[556,559,560,561],{"name":557,"slug":558,"type":15},"API Development","api-development",{"name":545,"slug":546,"type":15},{"name":9,"slug":8,"type":15},{"name":562,"slug":563,"type":15},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":566,"name":566,"fn":567,"description":568,"org":569,"tags":570,"stars":26,"repoUrl":27,"updatedAt":574},"copying-endpoints-across-projects","copy PostHog endpoints across projects","Copy a PostHog endpoint (a saved HogQL\u002Finsight query exposed as an API route) to another project in the same organization, or duplicate it under a new name in the same project. Use when the user wants to duplicate an endpoint, promote an endpoint from staging to production, replicate an endpoint's query\u002Fvariables\u002Ffreshness config in another workspace, or clone an endpoint to iterate on it. Unlike feature flags and experiments, endpoints have NO native cross-project copy tool — this skill covers the read-then-recreate flow (endpoint-get then endpoint-create), the active-project switching it requires, name-collision checks, and the safe defaults (land unmaterialised in the target, verify with endpoint-run). Does not cover editing endpoint versions (see managing-endpoint-versions) or authoring a brand-new endpoint from scratch (see creating-an-endpoint).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[571,572,573],{"name":557,"slug":558,"type":15},{"name":463,"slug":464,"type":15},{"name":9,"slug":8,"type":15},"2026-07-15T05:29:58.442727",{"slug":576,"name":576,"fn":577,"description":578,"org":579,"tags":580,"stars":26,"repoUrl":27,"updatedAt":592},"creating-ai-subscription","schedule recurring AI-generated PostHog reports","Create a recurring AI-generated PostHog report — schedule a free-text prompt to run on a cron, with the LLM-synthesized markdown delivered to email or Slack on each tick. Use when the user wants a recurring AI summary of X on any cadence (daily, weekly, monthly, yearly) rather than a one-off report. (To attach an AI summary to an existing insight\u002Fdashboard subscription instead of a free-text prompt, see `managing-subscriptions` and its `summary_enabled` option.)\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[581,582,585,586,589],{"name":474,"slug":475,"type":15},{"name":583,"slug":584,"type":15},"Email","email",{"name":9,"slug":8,"type":15},{"name":587,"slug":588,"type":15},"Reporting","reporting",{"name":590,"slug":591,"type":15},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":594,"name":594,"fn":595,"description":596,"org":597,"tags":598,"stars":26,"repoUrl":27,"updatedAt":602},"creating-an-endpoint","create PostHog API endpoints","Create a PostHog endpoint with the right shape on the first try — covers query kind choice, name conventions, what to expose as variables (HogQL code_name vs insight breakdown), data_freshness_seconds, and whether to materialise on day one. Use when the user says \"create an endpoint\", \"expose this query as an API\", \"turn this insight into an endpoint\", or asks for help structuring a new endpoint. Steers away from common mistakes: materialising a query with cohort breakdowns or compare mode, inline-only variables on a materialised endpoint, unbounded date ranges, ambiguous names.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[599,600,601],{"name":21,"slug":22,"type":15},{"name":557,"slug":558,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:29.624498",231]