[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-review-hog-blind-spots-general":3,"mdc--uvxe7r-key":46,"related-repo-posthog-review-hog-blind-spots-general":128,"related-org-posthog-review-hog-blind-spots-general":232},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":20,"repoUrl":21,"updatedAt":22,"license":23,"forks":24,"topics":25,"repo":41,"sourceUrl":44,"mdContent":45},"review-hog-blind-spots-general","perform final blind-spot code sweeps with ReviewHog","The general blind-spot check for ReviewHog — the final sweep that runs after every enabled review perspective has reviewed a chunk. Hunts for real, high-value issues that ALL of the perspectives missed, conditioned on what they actually found; returns an empty list over padding.\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,14,17],{"name":9,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"Code Review","code-review",{"name":18,"slug":19,"type":13},"Code Analysis","code-analysis",35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-15T05:30:20.68289",null,2977,[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"ab-testing","ai-analytics","analytics","cdp","data-warehouse","experiments","feature-flags","javascript","product-analytics","python","react","session-replay","surveys","typescript","web-analytics",{"repoUrl":21,"stars":20,"forks":24,"topics":42,"description":43},[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"🦔 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-blind-spots-general","---\nname: review-hog-blind-spots-general\ndescription: >\n  The general blind-spot check for ReviewHog — the final sweep that runs after every enabled review\n  perspective has reviewed a chunk. Hunts for real, high-value issues that ALL of the perspectives\n  missed, conditioned on what they actually found; returns an empty list over padding.\nmetadata:\n  owner_team: review_hog\n  skill_type: blind_spots\n---\n\n# Blind-spot check\n\nYou are the **blind-spot check** — the final sweep of a PR-chunk review. Several specialist\nperspectives have each already reviewed this exact chunk in parallel: which ones ran is listed in\nyour review prompt, along with what they found (or a note that they found nothing on this chunk).\nYour job is to catch the real, high-value issues that ALL of them missed. You are conditioned on\ntheir actual output, so hunt where they did not look instead of re-walking their ground.\n\n## How to hunt\n\n- Study the covered findings first (when there are any): they show where the perspectives spent\n  their attention. Your value is everywhere else.\n- Dig into what the prior findings did NOT touch — untested edge cases, error and failure paths,\n  unhandled inputs, cross-file interactions, and assumptions that break under load or hostile input.\n- You are not scoped to one specialty: a real issue is in scope no matter which lens it belongs to,\n  as long as no perspective already raised it.\n\n## What to report\n\n- Only genuinely NEW problems. Do not re-report, restate, or minorly reword anything already covered\n  in the findings above or in the PR's inline comments.\n- The bar is the same as any perspective's: a real, concrete problem with a nameable trigger and a\n  nameable consequence, anchored to this chunk's changes.\n- If the perspectives were thorough and nothing was missed, return an empty issues list. An empty\n  sweep is a valid, good outcome — padding is not.\n",{"data":47,"body":51},{"name":4,"description":6,"metadata":48},{"owner_team":49,"skill_type":50},"review_hog","blind_spots",{"type":52,"children":53},"root",[54,63,77,84,104,110],{"type":55,"tag":56,"props":57,"children":59},"element","h1",{"id":58},"blind-spot-check",[60],{"type":61,"value":62},"text","Blind-spot check",{"type":55,"tag":64,"props":65,"children":66},"p",{},[67,69,75],{"type":61,"value":68},"You are the ",{"type":55,"tag":70,"props":71,"children":72},"strong",{},[73],{"type":61,"value":74},"blind-spot check",{"type":61,"value":76}," — the final sweep of a PR-chunk review. Several specialist\nperspectives have each already reviewed this exact chunk in parallel: which ones ran is listed in\nyour review prompt, along with what they found (or a note that they found nothing on this chunk).\nYour job is to catch the real, high-value issues that ALL of them missed. You are conditioned on\ntheir actual output, so hunt where they did not look instead of re-walking their ground.",{"type":55,"tag":78,"props":79,"children":81},"h2",{"id":80},"how-to-hunt",[82],{"type":61,"value":83},"How to hunt",{"type":55,"tag":85,"props":86,"children":87},"ul",{},[88,94,99],{"type":55,"tag":89,"props":90,"children":91},"li",{},[92],{"type":61,"value":93},"Study the covered findings first (when there are any): they show where the perspectives spent\ntheir attention. Your value is everywhere else.",{"type":55,"tag":89,"props":95,"children":96},{},[97],{"type":61,"value":98},"Dig into what the prior findings did NOT touch — untested edge cases, error and failure paths,\nunhandled inputs, cross-file interactions, and assumptions that break under load or hostile input.",{"type":55,"tag":89,"props":100,"children":101},{},[102],{"type":61,"value":103},"You are not scoped to one specialty: a real issue is in scope no matter which lens it belongs to,\nas long as no perspective already raised it.",{"type":55,"tag":78,"props":105,"children":107},{"id":106},"what-to-report",[108],{"type":61,"value":109},"What to report",{"type":55,"tag":85,"props":111,"children":112},{},[113,118,123],{"type":55,"tag":89,"props":114,"children":115},{},[116],{"type":61,"value":117},"Only genuinely NEW problems. Do not re-report, restate, or minorly reword anything already covered\nin the findings above or in the PR's inline comments.",{"type":55,"tag":89,"props":119,"children":120},{},[121],{"type":61,"value":122},"The bar is the same as any perspective's: a real, concrete problem with a nameable trigger and a\nnameable consequence, anchored to this chunk's changes.",{"type":55,"tag":89,"props":124,"children":125},{},[126],{"type":61,"value":127},"If the perspectives were thorough and nothing was missed, return an empty issues list. An empty\nsweep is a valid, good outcome — padding is not.",{"items":129,"total":231},[130,146,158,170,183,198,214],{"slug":131,"name":131,"fn":132,"description":133,"org":134,"tags":135,"stars":20,"repoUrl":21,"updatedAt":145},"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},[136,138,141,144],{"name":137,"slug":28,"type":13},"Analytics",{"name":139,"slug":140,"type":13},"Cost Optimization","cost-optimization",{"name":142,"slug":143,"type":13},"Observability","observability",{"name":9,"slug":8,"type":13},"2026-07-28T05:34:11.117757",{"slug":147,"name":147,"fn":148,"description":149,"org":150,"tags":151,"stars":20,"repoUrl":21,"updatedAt":157},"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},[152,153,156],{"name":137,"slug":28,"type":13},{"name":154,"slug":155,"type":13},"Audit","audit",{"name":9,"slug":8,"type":13},"2026-06-08T08:08:33.693989",{"slug":159,"name":159,"fn":160,"description":161,"org":162,"tags":163,"stars":20,"repoUrl":21,"updatedAt":169},"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},[164,165,167,168],{"name":154,"slug":155,"type":13},{"name":166,"slug":30,"type":13},"Data Warehouse",{"name":142,"slug":143,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:22:57.67984",{"slug":171,"name":171,"fn":172,"description":173,"org":174,"tags":175,"stars":20,"repoUrl":21,"updatedAt":182},"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},[176,177,178,181],{"name":154,"slug":155,"type":13},{"name":166,"slug":30,"type":13},{"name":179,"slug":180,"type":13},"Performance","performance",{"name":9,"slug":8,"type":13},"2026-06-18T08:25:10.936787",{"slug":184,"name":184,"fn":185,"description":186,"org":187,"tags":188,"stars":20,"repoUrl":21,"updatedAt":197},"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},[189,192,195,196],{"name":190,"slug":191,"type":13},"Alerting","alerting",{"name":193,"slug":194,"type":13},"Debugging","debugging",{"name":142,"slug":143,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:24:40.318583",{"slug":199,"name":199,"fn":200,"description":201,"org":202,"tags":203,"stars":20,"repoUrl":21,"updatedAt":213},"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},[204,205,208,209,212],{"name":137,"slug":28,"type":13},{"name":206,"slug":207,"type":13},"Monitoring","monitoring",{"name":142,"slug":143,"type":13},{"name":210,"slug":211,"type":13},"Operations","operations",{"name":9,"slug":8,"type":13},"2026-07-18T05:10:54.430898",{"slug":215,"name":215,"fn":216,"description":217,"org":218,"tags":219,"stars":20,"repoUrl":21,"updatedAt":230},"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},[220,223,226,227],{"name":221,"slug":222,"type":13},"Automation","automation",{"name":224,"slug":225,"type":13},"MCP","mcp",{"name":9,"slug":8,"type":13},{"name":228,"slug":229,"type":13},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",61,{"items":233,"total":350},[234,241,247,254,261,268,276,283,297,312,322,340],{"slug":131,"name":131,"fn":132,"description":133,"org":235,"tags":236,"stars":20,"repoUrl":21,"updatedAt":145},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[237,238,239,240],{"name":137,"slug":28,"type":13},{"name":139,"slug":140,"type":13},{"name":142,"slug":143,"type":13},{"name":9,"slug":8,"type":13},{"slug":147,"name":147,"fn":148,"description":149,"org":242,"tags":243,"stars":20,"repoUrl":21,"updatedAt":157},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[244,245,246],{"name":137,"slug":28,"type":13},{"name":154,"slug":155,"type":13},{"name":9,"slug":8,"type":13},{"slug":159,"name":159,"fn":160,"description":161,"org":248,"tags":249,"stars":20,"repoUrl":21,"updatedAt":169},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[250,251,252,253],{"name":154,"slug":155,"type":13},{"name":166,"slug":30,"type":13},{"name":142,"slug":143,"type":13},{"name":9,"slug":8,"type":13},{"slug":171,"name":171,"fn":172,"description":173,"org":255,"tags":256,"stars":20,"repoUrl":21,"updatedAt":182},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[257,258,259,260],{"name":154,"slug":155,"type":13},{"name":166,"slug":30,"type":13},{"name":179,"slug":180,"type":13},{"name":9,"slug":8,"type":13},{"slug":184,"name":184,"fn":185,"description":186,"org":262,"tags":263,"stars":20,"repoUrl":21,"updatedAt":197},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[264,265,266,267],{"name":190,"slug":191,"type":13},{"name":193,"slug":194,"type":13},{"name":142,"slug":143,"type":13},{"name":9,"slug":8,"type":13},{"slug":199,"name":199,"fn":200,"description":201,"org":269,"tags":270,"stars":20,"repoUrl":21,"updatedAt":213},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[271,272,273,274,275],{"name":137,"slug":28,"type":13},{"name":206,"slug":207,"type":13},{"name":142,"slug":143,"type":13},{"name":210,"slug":211,"type":13},{"name":9,"slug":8,"type":13},{"slug":215,"name":215,"fn":216,"description":217,"org":277,"tags":278,"stars":20,"repoUrl":21,"updatedAt":230},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[279,280,281,282],{"name":221,"slug":222,"type":13},{"name":224,"slug":225,"type":13},{"name":9,"slug":8,"type":13},{"name":228,"slug":229,"type":13},{"slug":284,"name":284,"fn":285,"description":286,"org":287,"tags":288,"stars":20,"repoUrl":21,"updatedAt":296},"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},[289,290,291,294,295],{"name":137,"slug":28,"type":13},{"name":193,"slug":194,"type":13},{"name":292,"slug":293,"type":13},"Frontend","frontend",{"name":142,"slug":143,"type":13},{"name":9,"slug":8,"type":13},"2026-05-07T05:56:19.828048",{"slug":298,"name":298,"fn":299,"description":300,"org":301,"tags":302,"stars":20,"repoUrl":21,"updatedAt":311},"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},[303,306,307,308],{"name":304,"slug":305,"type":13},"API Development","api-development",{"name":292,"slug":293,"type":13},{"name":9,"slug":8,"type":13},{"name":309,"slug":310,"type":13},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":313,"name":313,"fn":314,"description":315,"org":316,"tags":317,"stars":20,"repoUrl":21,"updatedAt":321},"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},[318,319,320],{"name":304,"slug":305,"type":13},{"name":210,"slug":211,"type":13},{"name":9,"slug":8,"type":13},"2026-07-15T05:29:58.442727",{"slug":323,"name":323,"fn":324,"description":325,"org":326,"tags":327,"stars":20,"repoUrl":21,"updatedAt":339},"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},[328,329,332,333,336],{"name":221,"slug":222,"type":13},{"name":330,"slug":331,"type":13},"Email","email",{"name":9,"slug":8,"type":13},{"name":334,"slug":335,"type":13},"Reporting","reporting",{"name":337,"slug":338,"type":13},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":341,"name":341,"fn":342,"description":343,"org":344,"tags":345,"stars":20,"repoUrl":21,"updatedAt":349},"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},[346,347,348],{"name":137,"slug":28,"type":13},{"name":304,"slug":305,"type":13},{"name":9,"slug":8,"type":13},"2026-06-08T08:08:29.624498",231]