[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-review-hog-validation-criteria":3,"mdc--zd4lfb-key":45,"related-repo-posthog-review-hog-validation-criteria":368,"related-org-posthog-review-hog-validation-criteria":472},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":19,"repoUrl":20,"updatedAt":21,"license":22,"forks":23,"topics":24,"repo":40,"sourceUrl":43,"mdContent":44},"review-hog-validation-criteria","define validation criteria for ReviewHog","The validation criteria for ReviewHog — the bar for deciding whether a flagged PR issue is worth keeping. Keeps real, user-affecting correctness \u002F security \u002F data-loss \u002F contract \u002F performance problems; drops overengineering, speculation, paranoia, never-gonna-happen edge cases, and style.\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],{"name":13,"slug":14,"type":15},"Code Review","code-review","tag",{"name":17,"slug":18,"type":15},"Quality Assurance","quality-assurance",35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-15T05:30:19.259652",null,2977,[25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"ab-testing","ai-analytics","analytics","cdp","data-warehouse","experiments","feature-flags","javascript","product-analytics","python","react","session-replay","surveys","typescript","web-analytics",{"repoUrl":20,"stars":19,"forks":23,"topics":41,"description":42},[25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"🦔 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\u002Fproducts\u002Freview_hog\u002Fskills\u002Freview-hog-validation-criteria","---\nname: review-hog-validation-criteria\ndescription: >\n  The validation criteria for ReviewHog — the bar for deciding whether a flagged PR issue is worth\n  keeping. Keeps real, user-affecting correctness \u002F security \u002F data-loss \u002F contract \u002F performance\n  problems; drops overengineering, speculation, paranoia, never-gonna-happen edge cases, and style.\nmetadata:\n  owner_team: review_hog\n  skill_type: validation_criteria\n---\n\n# Review validation criteria\n\nYou are the final judgment gate of a PR review. Earlier specialist perspectives flagged candidate\nissues; your job is to decide, for each one, whether it is **worth surfacing to the author** — not to\nre-review the PR or invent new issues. Investigate the flagged code against the live codebase, then\nreturn a keep\u002Fdrop verdict (`is_valid`) using the bar below.\n\nThe guiding principle is **precision over recall**: a reviewer that raises noise gets muted, so when\nyou are genuinely unsure whether an issue matters, **drop it**. A smaller set of real, actionable\nfindings is worth far more than a long list padded with maybes.\n\n## Keep an issue (`is_valid = true`) when it is a real problem that plausibly affects users or the codebase\n\nKeep it if the flagged code, as written and as actually reached, would cause one of:\n\n- **Correctness bugs** — wrong results, broken logic, off-by-one \u002F boundary errors, mishandled edge\n  cases that real inputs will hit, incorrect data transformations or state mutations.\n- **Security issues** — injection, auth\u002Fpermission gaps, IDOR \u002F tenant-isolation holes, secret\n  leakage, unsafe deserialization, path traversal, SSRF.\n- **Data loss or corruption** — destructive or non-idempotent operations, lost writes, migrations\n  that drop or mangle data, race conditions that corrupt shared state.\n- **Contract breaks** — backwards-incompatible API \u002F schema \u002F signature changes, broken callers, a\n  changed invariant other code relies on.\n- **Performance problems that bite at real scale** — N+1 queries, unbounded loops\u002Fmemory on\n  realistic inputs, missing indexes on hot paths, blocking I\u002FO on an async path, accidental\n  quadratic behavior.\n- **Resource \u002F reliability defects** — leaked connections \u002F file handles, unreleased locks,\n  swallowed errors that hide failures, missing handling for a failure mode that will occur.\n\nA good \"keep\" can name the concrete trigger and the concrete consequence (\"if `items` is empty this\nraises `IndexError`\", \"this query runs once per row → N+1 on the dashboard\"). If you can't name both,\nbe skeptical.\n\n## Drop an issue (`is_valid = false`) when it is noise\n\nDrop it if it is any of:\n\n- **Overengineering** — \"extract this\", \"add an abstraction\u002Finterface\", \"make it configurable\",\n  \"future-proof for a case that isn't in scope\".\n- **Speculative \"what if\"** — depends on inputs or conditions that can't actually occur given the\n  call sites, types, or validation already in place.\n- **Defensive-coding paranoia** — guarding against `None`\u002Ferrors that upstream types or invariants\n  already rule out; redundant checks the framework or a parent caller already performs.\n- **Never-gonna-happen edge cases** — theoretically possible but practically unreachable, or so rare\n  and low-impact that handling it isn't worth the code.\n- **Pure style \u002F taste** — naming, formatting, comment wording, import order, \"I'd write it\n  differently\" with no behavioral difference. (Formatting is not a ReviewHog concern.)\n- **Already handled** — the supposed problem is prevented elsewhere (a parent caller, a default, a\n  framework guarantee, existing validation), which you confirmed by reading the surrounding code.\n- **Wrong \u002F unreproducible** — investigating the actual code shows the premise is mistaken.\n\n## How to decide\n\n1. Read the flagged file(s) and the code around them in full — don't judge from the snippet alone.\n2. Trace whether the problem can actually be reached: check call sites, types, validation, and how\n   inputs flow in.\n3. Weigh real impact (who is affected, how badly) against the bar above.\n4. On the fence → **drop** (precision over recall, as above).\n5. Record a focused `argumentation` that states the concrete reasoning for your verdict, and set\n   `category` to the kind of issue it is.\n",{"data":46,"body":50},{"name":4,"description":6,"metadata":47},{"owner_team":48,"skill_type":49},"review_hog","validation_criteria",{"type":51,"children":52},"root",[53,62,85,104,119,124,189,210,224,229,310,316],{"type":54,"tag":55,"props":56,"children":58},"element","h1",{"id":57},"review-validation-criteria",[59],{"type":60,"value":61},"text","Review validation criteria",{"type":54,"tag":63,"props":64,"children":65},"p",{},[66,68,74,76,83],{"type":60,"value":67},"You are the final judgment gate of a PR review. Earlier specialist perspectives flagged candidate\nissues; your job is to decide, for each one, whether it is ",{"type":54,"tag":69,"props":70,"children":71},"strong",{},[72],{"type":60,"value":73},"worth surfacing to the author",{"type":60,"value":75}," — not to\nre-review the PR or invent new issues. Investigate the flagged code against the live codebase, then\nreturn a keep\u002Fdrop verdict (",{"type":54,"tag":77,"props":78,"children":80},"code",{"className":79},[],[81],{"type":60,"value":82},"is_valid",{"type":60,"value":84},") using the bar below.",{"type":54,"tag":63,"props":86,"children":87},{},[88,90,95,97,102],{"type":60,"value":89},"The guiding principle is ",{"type":54,"tag":69,"props":91,"children":92},{},[93],{"type":60,"value":94},"precision over recall",{"type":60,"value":96},": a reviewer that raises noise gets muted, so when\nyou are genuinely unsure whether an issue matters, ",{"type":54,"tag":69,"props":98,"children":99},{},[100],{"type":60,"value":101},"drop it",{"type":60,"value":103},". A smaller set of real, actionable\nfindings is worth far more than a long list padded with maybes.",{"type":54,"tag":105,"props":106,"children":108},"h2",{"id":107},"keep-an-issue-is_valid-true-when-it-is-a-real-problem-that-plausibly-affects-users-or-the-codebase",[109,111,117],{"type":60,"value":110},"Keep an issue (",{"type":54,"tag":77,"props":112,"children":114},{"className":113},[],[115],{"type":60,"value":116},"is_valid = true",{"type":60,"value":118},") when it is a real problem that plausibly affects users or the codebase",{"type":54,"tag":63,"props":120,"children":121},{},[122],{"type":60,"value":123},"Keep it if the flagged code, as written and as actually reached, would cause one of:",{"type":54,"tag":125,"props":126,"children":127},"ul",{},[128,139,149,159,169,179],{"type":54,"tag":129,"props":130,"children":131},"li",{},[132,137],{"type":54,"tag":69,"props":133,"children":134},{},[135],{"type":60,"value":136},"Correctness bugs",{"type":60,"value":138}," — wrong results, broken logic, off-by-one \u002F boundary errors, mishandled edge\ncases that real inputs will hit, incorrect data transformations or state mutations.",{"type":54,"tag":129,"props":140,"children":141},{},[142,147],{"type":54,"tag":69,"props":143,"children":144},{},[145],{"type":60,"value":146},"Security issues",{"type":60,"value":148}," — injection, auth\u002Fpermission gaps, IDOR \u002F tenant-isolation holes, secret\nleakage, unsafe deserialization, path traversal, SSRF.",{"type":54,"tag":129,"props":150,"children":151},{},[152,157],{"type":54,"tag":69,"props":153,"children":154},{},[155],{"type":60,"value":156},"Data loss or corruption",{"type":60,"value":158}," — destructive or non-idempotent operations, lost writes, migrations\nthat drop or mangle data, race conditions that corrupt shared state.",{"type":54,"tag":129,"props":160,"children":161},{},[162,167],{"type":54,"tag":69,"props":163,"children":164},{},[165],{"type":60,"value":166},"Contract breaks",{"type":60,"value":168}," — backwards-incompatible API \u002F schema \u002F signature changes, broken callers, a\nchanged invariant other code relies on.",{"type":54,"tag":129,"props":170,"children":171},{},[172,177],{"type":54,"tag":69,"props":173,"children":174},{},[175],{"type":60,"value":176},"Performance problems that bite at real scale",{"type":60,"value":178}," — N+1 queries, unbounded loops\u002Fmemory on\nrealistic inputs, missing indexes on hot paths, blocking I\u002FO on an async path, accidental\nquadratic behavior.",{"type":54,"tag":129,"props":180,"children":181},{},[182,187],{"type":54,"tag":69,"props":183,"children":184},{},[185],{"type":60,"value":186},"Resource \u002F reliability defects",{"type":60,"value":188}," — leaked connections \u002F file handles, unreleased locks,\nswallowed errors that hide failures, missing handling for a failure mode that will occur.",{"type":54,"tag":63,"props":190,"children":191},{},[192,194,200,202,208],{"type":60,"value":193},"A good \"keep\" can name the concrete trigger and the concrete consequence (\"if ",{"type":54,"tag":77,"props":195,"children":197},{"className":196},[],[198],{"type":60,"value":199},"items",{"type":60,"value":201}," is empty this\nraises ",{"type":54,"tag":77,"props":203,"children":205},{"className":204},[],[206],{"type":60,"value":207},"IndexError",{"type":60,"value":209},"\", \"this query runs once per row → N+1 on the dashboard\"). If you can't name both,\nbe skeptical.",{"type":54,"tag":105,"props":211,"children":213},{"id":212},"drop-an-issue-is_valid-false-when-it-is-noise",[214,216,222],{"type":60,"value":215},"Drop an issue (",{"type":54,"tag":77,"props":217,"children":219},{"className":218},[],[220],{"type":60,"value":221},"is_valid = false",{"type":60,"value":223},") when it is noise",{"type":54,"tag":63,"props":225,"children":226},{},[227],{"type":60,"value":228},"Drop it if it is any of:",{"type":54,"tag":125,"props":230,"children":231},{},[232,242,252,270,280,290,300],{"type":54,"tag":129,"props":233,"children":234},{},[235,240],{"type":54,"tag":69,"props":236,"children":237},{},[238],{"type":60,"value":239},"Overengineering",{"type":60,"value":241}," — \"extract this\", \"add an abstraction\u002Finterface\", \"make it configurable\",\n\"future-proof for a case that isn't in scope\".",{"type":54,"tag":129,"props":243,"children":244},{},[245,250],{"type":54,"tag":69,"props":246,"children":247},{},[248],{"type":60,"value":249},"Speculative \"what if\"",{"type":60,"value":251}," — depends on inputs or conditions that can't actually occur given the\ncall sites, types, or validation already in place.",{"type":54,"tag":129,"props":253,"children":254},{},[255,260,262,268],{"type":54,"tag":69,"props":256,"children":257},{},[258],{"type":60,"value":259},"Defensive-coding paranoia",{"type":60,"value":261}," — guarding against ",{"type":54,"tag":77,"props":263,"children":265},{"className":264},[],[266],{"type":60,"value":267},"None",{"type":60,"value":269},"\u002Ferrors that upstream types or invariants\nalready rule out; redundant checks the framework or a parent caller already performs.",{"type":54,"tag":129,"props":271,"children":272},{},[273,278],{"type":54,"tag":69,"props":274,"children":275},{},[276],{"type":60,"value":277},"Never-gonna-happen edge cases",{"type":60,"value":279}," — theoretically possible but practically unreachable, or so rare\nand low-impact that handling it isn't worth the code.",{"type":54,"tag":129,"props":281,"children":282},{},[283,288],{"type":54,"tag":69,"props":284,"children":285},{},[286],{"type":60,"value":287},"Pure style \u002F taste",{"type":60,"value":289}," — naming, formatting, comment wording, import order, \"I'd write it\ndifferently\" with no behavioral difference. (Formatting is not a ReviewHog concern.)",{"type":54,"tag":129,"props":291,"children":292},{},[293,298],{"type":54,"tag":69,"props":294,"children":295},{},[296],{"type":60,"value":297},"Already handled",{"type":60,"value":299}," — the supposed problem is prevented elsewhere (a parent caller, a default, a\nframework guarantee, existing validation), which you confirmed by reading the surrounding code.",{"type":54,"tag":129,"props":301,"children":302},{},[303,308],{"type":54,"tag":69,"props":304,"children":305},{},[306],{"type":60,"value":307},"Wrong \u002F unreproducible",{"type":60,"value":309}," — investigating the actual code shows the premise is mistaken.",{"type":54,"tag":105,"props":311,"children":313},{"id":312},"how-to-decide",[314],{"type":60,"value":315},"How to decide",{"type":54,"tag":317,"props":318,"children":319},"ol",{},[320,325,330,335,347],{"type":54,"tag":129,"props":321,"children":322},{},[323],{"type":60,"value":324},"Read the flagged file(s) and the code around them in full — don't judge from the snippet alone.",{"type":54,"tag":129,"props":326,"children":327},{},[328],{"type":60,"value":329},"Trace whether the problem can actually be reached: check call sites, types, validation, and how\ninputs flow in.",{"type":54,"tag":129,"props":331,"children":332},{},[333],{"type":60,"value":334},"Weigh real impact (who is affected, how badly) against the bar above.",{"type":54,"tag":129,"props":336,"children":337},{},[338,340,345],{"type":60,"value":339},"On the fence → ",{"type":54,"tag":69,"props":341,"children":342},{},[343],{"type":60,"value":344},"drop",{"type":60,"value":346}," (precision over recall, as above).",{"type":54,"tag":129,"props":348,"children":349},{},[350,352,358,360,366],{"type":60,"value":351},"Record a focused ",{"type":54,"tag":77,"props":353,"children":355},{"className":354},[],[356],{"type":60,"value":357},"argumentation",{"type":60,"value":359}," that states the concrete reasoning for your verdict, and set\n",{"type":54,"tag":77,"props":361,"children":363},{"className":362},[],[364],{"type":60,"value":365},"category",{"type":60,"value":367}," to the kind of issue it is.",{"items":369,"total":471},[370,386,398,410,423,438,454],{"slug":371,"name":371,"fn":372,"description":373,"org":374,"tags":375,"stars":19,"repoUrl":20,"updatedAt":385},"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},[376,378,381,384],{"name":377,"slug":27,"type":15},"Analytics",{"name":379,"slug":380,"type":15},"Cost Optimization","cost-optimization",{"name":382,"slug":383,"type":15},"Observability","observability",{"name":9,"slug":8,"type":15},"2026-07-28T05:34:11.117757",{"slug":387,"name":387,"fn":388,"description":389,"org":390,"tags":391,"stars":19,"repoUrl":20,"updatedAt":397},"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},[392,393,396],{"name":377,"slug":27,"type":15},{"name":394,"slug":395,"type":15},"Audit","audit",{"name":9,"slug":8,"type":15},"2026-06-08T08:08:33.693989",{"slug":399,"name":399,"fn":400,"description":401,"org":402,"tags":403,"stars":19,"repoUrl":20,"updatedAt":409},"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},[404,405,407,408],{"name":394,"slug":395,"type":15},{"name":406,"slug":29,"type":15},"Data Warehouse",{"name":382,"slug":383,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:22:57.67984",{"slug":411,"name":411,"fn":412,"description":413,"org":414,"tags":415,"stars":19,"repoUrl":20,"updatedAt":422},"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},[416,417,418,421],{"name":394,"slug":395,"type":15},{"name":406,"slug":29,"type":15},{"name":419,"slug":420,"type":15},"Performance","performance",{"name":9,"slug":8,"type":15},"2026-06-18T08:25:10.936787",{"slug":424,"name":424,"fn":425,"description":426,"org":427,"tags":428,"stars":19,"repoUrl":20,"updatedAt":437},"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},[429,432,435,436],{"name":430,"slug":431,"type":15},"Alerting","alerting",{"name":433,"slug":434,"type":15},"Debugging","debugging",{"name":382,"slug":383,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:24:40.318583",{"slug":439,"name":439,"fn":440,"description":441,"org":442,"tags":443,"stars":19,"repoUrl":20,"updatedAt":453},"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},[444,445,448,449,452],{"name":377,"slug":27,"type":15},{"name":446,"slug":447,"type":15},"Monitoring","monitoring",{"name":382,"slug":383,"type":15},{"name":450,"slug":451,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-07-18T05:10:54.430898",{"slug":455,"name":455,"fn":456,"description":457,"org":458,"tags":459,"stars":19,"repoUrl":20,"updatedAt":470},"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},[460,463,466,467],{"name":461,"slug":462,"type":15},"Automation","automation",{"name":464,"slug":465,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},{"name":468,"slug":469,"type":15},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",61,{"items":473,"total":590},[474,481,487,494,501,508,516,523,537,552,562,580],{"slug":371,"name":371,"fn":372,"description":373,"org":475,"tags":476,"stars":19,"repoUrl":20,"updatedAt":385},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[477,478,479,480],{"name":377,"slug":27,"type":15},{"name":379,"slug":380,"type":15},{"name":382,"slug":383,"type":15},{"name":9,"slug":8,"type":15},{"slug":387,"name":387,"fn":388,"description":389,"org":482,"tags":483,"stars":19,"repoUrl":20,"updatedAt":397},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[484,485,486],{"name":377,"slug":27,"type":15},{"name":394,"slug":395,"type":15},{"name":9,"slug":8,"type":15},{"slug":399,"name":399,"fn":400,"description":401,"org":488,"tags":489,"stars":19,"repoUrl":20,"updatedAt":409},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[490,491,492,493],{"name":394,"slug":395,"type":15},{"name":406,"slug":29,"type":15},{"name":382,"slug":383,"type":15},{"name":9,"slug":8,"type":15},{"slug":411,"name":411,"fn":412,"description":413,"org":495,"tags":496,"stars":19,"repoUrl":20,"updatedAt":422},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[497,498,499,500],{"name":394,"slug":395,"type":15},{"name":406,"slug":29,"type":15},{"name":419,"slug":420,"type":15},{"name":9,"slug":8,"type":15},{"slug":424,"name":424,"fn":425,"description":426,"org":502,"tags":503,"stars":19,"repoUrl":20,"updatedAt":437},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[504,505,506,507],{"name":430,"slug":431,"type":15},{"name":433,"slug":434,"type":15},{"name":382,"slug":383,"type":15},{"name":9,"slug":8,"type":15},{"slug":439,"name":439,"fn":440,"description":441,"org":509,"tags":510,"stars":19,"repoUrl":20,"updatedAt":453},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[511,512,513,514,515],{"name":377,"slug":27,"type":15},{"name":446,"slug":447,"type":15},{"name":382,"slug":383,"type":15},{"name":450,"slug":451,"type":15},{"name":9,"slug":8,"type":15},{"slug":455,"name":455,"fn":456,"description":457,"org":517,"tags":518,"stars":19,"repoUrl":20,"updatedAt":470},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[519,520,521,522],{"name":461,"slug":462,"type":15},{"name":464,"slug":465,"type":15},{"name":9,"slug":8,"type":15},{"name":468,"slug":469,"type":15},{"slug":524,"name":524,"fn":525,"description":526,"org":527,"tags":528,"stars":19,"repoUrl":20,"updatedAt":536},"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},[529,530,531,534,535],{"name":377,"slug":27,"type":15},{"name":433,"slug":434,"type":15},{"name":532,"slug":533,"type":15},"Frontend","frontend",{"name":382,"slug":383,"type":15},{"name":9,"slug":8,"type":15},"2026-05-07T05:56:19.828048",{"slug":538,"name":538,"fn":539,"description":540,"org":541,"tags":542,"stars":19,"repoUrl":20,"updatedAt":551},"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},[543,546,547,548],{"name":544,"slug":545,"type":15},"API Development","api-development",{"name":532,"slug":533,"type":15},{"name":9,"slug":8,"type":15},{"name":549,"slug":550,"type":15},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":553,"name":553,"fn":554,"description":555,"org":556,"tags":557,"stars":19,"repoUrl":20,"updatedAt":561},"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},[558,559,560],{"name":544,"slug":545,"type":15},{"name":450,"slug":451,"type":15},{"name":9,"slug":8,"type":15},"2026-07-15T05:29:58.442727",{"slug":563,"name":563,"fn":564,"description":565,"org":566,"tags":567,"stars":19,"repoUrl":20,"updatedAt":579},"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},[568,569,572,573,576],{"name":461,"slug":462,"type":15},{"name":570,"slug":571,"type":15},"Email","email",{"name":9,"slug":8,"type":15},{"name":574,"slug":575,"type":15},"Reporting","reporting",{"name":577,"slug":578,"type":15},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":19,"repoUrl":20,"updatedAt":589},"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},[586,587,588],{"name":377,"slug":27,"type":15},{"name":544,"slug":545,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:29.624498",231]