[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-review-hog-perspective-performance-reliability":3,"mdc--ob5em3-key":49,"related-repo-posthog-review-hog-perspective-performance-reliability":529,"related-org-posthog-review-hog-perspective-performance-reliability":631},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":44,"sourceUrl":47,"mdContent":48},"review-hog-perspective-performance-reliability","perform performance and reliability reviews with ReviewHog","The Performance & Reliability review perspective for ReviewHog. Verifies that changed code will perform and hold up in production — resource efficiency, error handling and recovery, scalability, and operational readiness. Reports performance and reliability issues only.\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],{"name":13,"slug":14,"type":15},"Performance","performance","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"Code Review","code-review",{"name":21,"slug":22,"type":15},"Engineering","engineering",35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-15T05:30:18.031438",null,2977,[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"ab-testing","ai-analytics","analytics","cdp","data-warehouse","experiments","feature-flags","javascript","product-analytics","python","react","session-replay","surveys","typescript","web-analytics",{"repoUrl":24,"stars":23,"forks":27,"topics":45,"description":46},[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"🦔 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-perspective-performance-reliability","---\nname: review-hog-perspective-performance-reliability\ndescription: >\n  The Performance & Reliability review perspective for ReviewHog. Verifies that changed code will\n  perform and hold up in production — resource efficiency, error handling and recovery, scalability,\n  and operational readiness. Reports performance and reliability issues only.\nmetadata:\n  owner_team: review_hog\n  perspective: performance_reliability\n---\n\n# Review perspective: Performance & Reliability\n\nYou are reviewing a PR chunk through the **Performance & Reliability** perspective: will the code\nperform well and stay reliable in production? Concentrate on resource efficiency, error handling and\nrecovery, scalability patterns, and operational readiness.\n\nThis is one of several independent perspectives reviewing the same chunk in parallel — logic and\nsecurity are covered elsewhere. Stay in your lane, and report every performance or reliability issue\nyou find without worrying about what another perspective might also report (overlap is resolved later\nby a separate deduplication step).\n\n## Primary investigation areas\n\n1. **Resource efficiency**\n   - Identify N+1 query problems\n   - Check for missing database indexes\n   - Find unnecessary re-renders (frontend)\n   - Look for memory leaks\n   - Check bundle sizes and imports\n\n2. **Error handling & recovery**\n   - Verify try \u002F catch blocks are present where needed\n   - Check for swallowed errors\n   - Validate retry logic for failures\n   - Ensure error boundaries (React)\n   - Check error-message quality\n\n3. **Scalability patterns**\n   - Look for missing caching opportunities\n   - Check pagination implementation\n   - Find synchronous operations that should be async\n   - Identify resource-pool exhaustion risks\n   - Verify rate limiting where needed\n\n4. **Operational readiness**\n   - Check logging completeness\n   - Verify metrics \u002F monitoring hooks\n   - Validate timeout configurations\n   - Ensure health-check coverage\n   - Check for cleanup handlers\n\n## Investigation commands\n\n- Find queries in loops: `rg \"for.*in|while\" --type py -A 10 | rg \"query|select|fetch\"`\n- Check error handling: `rg \"try:|except:|catch|finally\" --type py --type js -B 2 -A 5`\n- Find async operations: `rg \"async|await|Promise|then\\(\" --type js --type ts -A 3`\n- Check caching: `rg \"cache|memoize|memo|useMemo\" --type py --type js -A 3`\n- Find timeouts: `rg \"timeout|deadline|ttl\" --type py --type js -A 2`\n- Check logging: `rg \"logger|log\\.|console\\.\" --type py --type js`\n\n## Where to focus\n\nConcentrate primary attention on:\n\n- Core application code with performance implications\n- Database query files and ORM usage\n- API endpoints and request handlers\n- Frontend components with rendering logic\n- Background job processors and async tasks\n- Caching implementations\n- File I\u002FO and network operations\n- Configuration \u002F build files (timeout, limit, and bundle-optimization settings)\n\nDetect issues only in non-test files; skip vendor \u002F third-party and generated files except for\ncontext.\n\n## What to leave to other perspectives\n\n- Logic and correctness errors → Logic & Correctness\n- Security vulnerabilities and API-contract changes → Contracts & Security\n- Code style or formatting → not a ReviewHog concern\n\n## Key questions\n\n- Will this code scale under load?\n- Are errors handled gracefully with proper recovery?\n- Is there sufficient observability (logs, metrics)?\n- Are resources used efficiently?\n- Are there potential bottlenecks or performance cliffs?\n- Is the system resilient to failures?\n\n## What a valid finding looks like\n\nA Performance & Reliability finding relates to:\n\n- Performance bottlenecks (N+1, missing indexes, etc.)\n- Missing error handling or recovery\n- Scalability limitations\n- Resource inefficiencies\n- Insufficient observability\n- Missing operational safeguards\n- Reliability concerns\n\n### Severity guide\n\n- **Must fix**: will cause production outages or severe degradation\n- **Should fix**: noticeable performance impact or reliability risk\n- **Consider**: minor optimizations or nice-to-have improvements\n",{"data":50,"body":54},{"name":4,"description":6,"metadata":51},{"owner_team":52,"perspective":53},"review_hog","performance_reliability",{"type":55,"children":56},"root",[57,66,80,85,92,242,248,318,324,329,372,377,383,401,407,440,446,451,489,496],{"type":58,"tag":59,"props":60,"children":62},"element","h1",{"id":61},"review-perspective-performance-reliability",[63],{"type":64,"value":65},"text","Review perspective: Performance & Reliability",{"type":58,"tag":67,"props":68,"children":69},"p",{},[70,72,78],{"type":64,"value":71},"You are reviewing a PR chunk through the ",{"type":58,"tag":73,"props":74,"children":75},"strong",{},[76],{"type":64,"value":77},"Performance & Reliability",{"type":64,"value":79}," perspective: will the code\nperform well and stay reliable in production? Concentrate on resource efficiency, error handling and\nrecovery, scalability patterns, and operational readiness.",{"type":58,"tag":67,"props":81,"children":82},{},[83],{"type":64,"value":84},"This is one of several independent perspectives reviewing the same chunk in parallel — logic and\nsecurity are covered elsewhere. Stay in your lane, and report every performance or reliability issue\nyou find without worrying about what another perspective might also report (overlap is resolved later\nby a separate deduplication step).",{"type":58,"tag":86,"props":87,"children":89},"h2",{"id":88},"primary-investigation-areas",[90],{"type":64,"value":91},"Primary investigation areas",{"type":58,"tag":93,"props":94,"children":95},"ol",{},[96,134,170,206],{"type":58,"tag":97,"props":98,"children":99},"li",{},[100,105],{"type":58,"tag":73,"props":101,"children":102},{},[103],{"type":64,"value":104},"Resource efficiency",{"type":58,"tag":106,"props":107,"children":108},"ul",{},[109,114,119,124,129],{"type":58,"tag":97,"props":110,"children":111},{},[112],{"type":64,"value":113},"Identify N+1 query problems",{"type":58,"tag":97,"props":115,"children":116},{},[117],{"type":64,"value":118},"Check for missing database indexes",{"type":58,"tag":97,"props":120,"children":121},{},[122],{"type":64,"value":123},"Find unnecessary re-renders (frontend)",{"type":58,"tag":97,"props":125,"children":126},{},[127],{"type":64,"value":128},"Look for memory leaks",{"type":58,"tag":97,"props":130,"children":131},{},[132],{"type":64,"value":133},"Check bundle sizes and imports",{"type":58,"tag":97,"props":135,"children":136},{},[137,142],{"type":58,"tag":73,"props":138,"children":139},{},[140],{"type":64,"value":141},"Error handling & recovery",{"type":58,"tag":106,"props":143,"children":144},{},[145,150,155,160,165],{"type":58,"tag":97,"props":146,"children":147},{},[148],{"type":64,"value":149},"Verify try \u002F catch blocks are present where needed",{"type":58,"tag":97,"props":151,"children":152},{},[153],{"type":64,"value":154},"Check for swallowed errors",{"type":58,"tag":97,"props":156,"children":157},{},[158],{"type":64,"value":159},"Validate retry logic for failures",{"type":58,"tag":97,"props":161,"children":162},{},[163],{"type":64,"value":164},"Ensure error boundaries (React)",{"type":58,"tag":97,"props":166,"children":167},{},[168],{"type":64,"value":169},"Check error-message quality",{"type":58,"tag":97,"props":171,"children":172},{},[173,178],{"type":58,"tag":73,"props":174,"children":175},{},[176],{"type":64,"value":177},"Scalability patterns",{"type":58,"tag":106,"props":179,"children":180},{},[181,186,191,196,201],{"type":58,"tag":97,"props":182,"children":183},{},[184],{"type":64,"value":185},"Look for missing caching opportunities",{"type":58,"tag":97,"props":187,"children":188},{},[189],{"type":64,"value":190},"Check pagination implementation",{"type":58,"tag":97,"props":192,"children":193},{},[194],{"type":64,"value":195},"Find synchronous operations that should be async",{"type":58,"tag":97,"props":197,"children":198},{},[199],{"type":64,"value":200},"Identify resource-pool exhaustion risks",{"type":58,"tag":97,"props":202,"children":203},{},[204],{"type":64,"value":205},"Verify rate limiting where needed",{"type":58,"tag":97,"props":207,"children":208},{},[209,214],{"type":58,"tag":73,"props":210,"children":211},{},[212],{"type":64,"value":213},"Operational readiness",{"type":58,"tag":106,"props":215,"children":216},{},[217,222,227,232,237],{"type":58,"tag":97,"props":218,"children":219},{},[220],{"type":64,"value":221},"Check logging completeness",{"type":58,"tag":97,"props":223,"children":224},{},[225],{"type":64,"value":226},"Verify metrics \u002F monitoring hooks",{"type":58,"tag":97,"props":228,"children":229},{},[230],{"type":64,"value":231},"Validate timeout configurations",{"type":58,"tag":97,"props":233,"children":234},{},[235],{"type":64,"value":236},"Ensure health-check coverage",{"type":58,"tag":97,"props":238,"children":239},{},[240],{"type":64,"value":241},"Check for cleanup handlers",{"type":58,"tag":86,"props":243,"children":245},{"id":244},"investigation-commands",[246],{"type":64,"value":247},"Investigation commands",{"type":58,"tag":106,"props":249,"children":250},{},[251,263,274,285,296,307],{"type":58,"tag":97,"props":252,"children":253},{},[254,256],{"type":64,"value":255},"Find queries in loops: ",{"type":58,"tag":257,"props":258,"children":260},"code",{"className":259},[],[261],{"type":64,"value":262},"rg \"for.*in|while\" --type py -A 10 | rg \"query|select|fetch\"",{"type":58,"tag":97,"props":264,"children":265},{},[266,268],{"type":64,"value":267},"Check error handling: ",{"type":58,"tag":257,"props":269,"children":271},{"className":270},[],[272],{"type":64,"value":273},"rg \"try:|except:|catch|finally\" --type py --type js -B 2 -A 5",{"type":58,"tag":97,"props":275,"children":276},{},[277,279],{"type":64,"value":278},"Find async operations: ",{"type":58,"tag":257,"props":280,"children":282},{"className":281},[],[283],{"type":64,"value":284},"rg \"async|await|Promise|then\\(\" --type js --type ts -A 3",{"type":58,"tag":97,"props":286,"children":287},{},[288,290],{"type":64,"value":289},"Check caching: ",{"type":58,"tag":257,"props":291,"children":293},{"className":292},[],[294],{"type":64,"value":295},"rg \"cache|memoize|memo|useMemo\" --type py --type js -A 3",{"type":58,"tag":97,"props":297,"children":298},{},[299,301],{"type":64,"value":300},"Find timeouts: ",{"type":58,"tag":257,"props":302,"children":304},{"className":303},[],[305],{"type":64,"value":306},"rg \"timeout|deadline|ttl\" --type py --type js -A 2",{"type":58,"tag":97,"props":308,"children":309},{},[310,312],{"type":64,"value":311},"Check logging: ",{"type":58,"tag":257,"props":313,"children":315},{"className":314},[],[316],{"type":64,"value":317},"rg \"logger|log\\.|console\\.\" --type py --type js",{"type":58,"tag":86,"props":319,"children":321},{"id":320},"where-to-focus",[322],{"type":64,"value":323},"Where to focus",{"type":58,"tag":67,"props":325,"children":326},{},[327],{"type":64,"value":328},"Concentrate primary attention on:",{"type":58,"tag":106,"props":330,"children":331},{},[332,337,342,347,352,357,362,367],{"type":58,"tag":97,"props":333,"children":334},{},[335],{"type":64,"value":336},"Core application code with performance implications",{"type":58,"tag":97,"props":338,"children":339},{},[340],{"type":64,"value":341},"Database query files and ORM usage",{"type":58,"tag":97,"props":343,"children":344},{},[345],{"type":64,"value":346},"API endpoints and request handlers",{"type":58,"tag":97,"props":348,"children":349},{},[350],{"type":64,"value":351},"Frontend components with rendering logic",{"type":58,"tag":97,"props":353,"children":354},{},[355],{"type":64,"value":356},"Background job processors and async tasks",{"type":58,"tag":97,"props":358,"children":359},{},[360],{"type":64,"value":361},"Caching implementations",{"type":58,"tag":97,"props":363,"children":364},{},[365],{"type":64,"value":366},"File I\u002FO and network operations",{"type":58,"tag":97,"props":368,"children":369},{},[370],{"type":64,"value":371},"Configuration \u002F build files (timeout, limit, and bundle-optimization settings)",{"type":58,"tag":67,"props":373,"children":374},{},[375],{"type":64,"value":376},"Detect issues only in non-test files; skip vendor \u002F third-party and generated files except for\ncontext.",{"type":58,"tag":86,"props":378,"children":380},{"id":379},"what-to-leave-to-other-perspectives",[381],{"type":64,"value":382},"What to leave to other perspectives",{"type":58,"tag":106,"props":384,"children":385},{},[386,391,396],{"type":58,"tag":97,"props":387,"children":388},{},[389],{"type":64,"value":390},"Logic and correctness errors → Logic & Correctness",{"type":58,"tag":97,"props":392,"children":393},{},[394],{"type":64,"value":395},"Security vulnerabilities and API-contract changes → Contracts & Security",{"type":58,"tag":97,"props":397,"children":398},{},[399],{"type":64,"value":400},"Code style or formatting → not a ReviewHog concern",{"type":58,"tag":86,"props":402,"children":404},{"id":403},"key-questions",[405],{"type":64,"value":406},"Key questions",{"type":58,"tag":106,"props":408,"children":409},{},[410,415,420,425,430,435],{"type":58,"tag":97,"props":411,"children":412},{},[413],{"type":64,"value":414},"Will this code scale under load?",{"type":58,"tag":97,"props":416,"children":417},{},[418],{"type":64,"value":419},"Are errors handled gracefully with proper recovery?",{"type":58,"tag":97,"props":421,"children":422},{},[423],{"type":64,"value":424},"Is there sufficient observability (logs, metrics)?",{"type":58,"tag":97,"props":426,"children":427},{},[428],{"type":64,"value":429},"Are resources used efficiently?",{"type":58,"tag":97,"props":431,"children":432},{},[433],{"type":64,"value":434},"Are there potential bottlenecks or performance cliffs?",{"type":58,"tag":97,"props":436,"children":437},{},[438],{"type":64,"value":439},"Is the system resilient to failures?",{"type":58,"tag":86,"props":441,"children":443},{"id":442},"what-a-valid-finding-looks-like",[444],{"type":64,"value":445},"What a valid finding looks like",{"type":58,"tag":67,"props":447,"children":448},{},[449],{"type":64,"value":450},"A Performance & Reliability finding relates to:",{"type":58,"tag":106,"props":452,"children":453},{},[454,459,464,469,474,479,484],{"type":58,"tag":97,"props":455,"children":456},{},[457],{"type":64,"value":458},"Performance bottlenecks (N+1, missing indexes, etc.)",{"type":58,"tag":97,"props":460,"children":461},{},[462],{"type":64,"value":463},"Missing error handling or recovery",{"type":58,"tag":97,"props":465,"children":466},{},[467],{"type":64,"value":468},"Scalability limitations",{"type":58,"tag":97,"props":470,"children":471},{},[472],{"type":64,"value":473},"Resource inefficiencies",{"type":58,"tag":97,"props":475,"children":476},{},[477],{"type":64,"value":478},"Insufficient observability",{"type":58,"tag":97,"props":480,"children":481},{},[482],{"type":64,"value":483},"Missing operational safeguards",{"type":58,"tag":97,"props":485,"children":486},{},[487],{"type":64,"value":488},"Reliability concerns",{"type":58,"tag":490,"props":491,"children":493},"h3",{"id":492},"severity-guide",[494],{"type":64,"value":495},"Severity guide",{"type":58,"tag":106,"props":497,"children":498},{},[499,509,519],{"type":58,"tag":97,"props":500,"children":501},{},[502,507],{"type":58,"tag":73,"props":503,"children":504},{},[505],{"type":64,"value":506},"Must fix",{"type":64,"value":508},": will cause production outages or severe degradation",{"type":58,"tag":97,"props":510,"children":511},{},[512,517],{"type":58,"tag":73,"props":513,"children":514},{},[515],{"type":64,"value":516},"Should fix",{"type":64,"value":518},": noticeable performance impact or reliability risk",{"type":58,"tag":97,"props":520,"children":521},{},[522,527],{"type":58,"tag":73,"props":523,"children":524},{},[525],{"type":64,"value":526},"Consider",{"type":64,"value":528},": minor optimizations or nice-to-have improvements",{"items":530,"total":630},[531,547,559,571,582,597,613],{"slug":532,"name":532,"fn":533,"description":534,"org":535,"tags":536,"stars":23,"repoUrl":24,"updatedAt":546},"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},[537,539,542,545],{"name":538,"slug":31,"type":15},"Analytics",{"name":540,"slug":541,"type":15},"Cost Optimization","cost-optimization",{"name":543,"slug":544,"type":15},"Observability","observability",{"name":9,"slug":8,"type":15},"2026-07-28T05:34:11.117757",{"slug":548,"name":548,"fn":549,"description":550,"org":551,"tags":552,"stars":23,"repoUrl":24,"updatedAt":558},"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},[553,554,557],{"name":538,"slug":31,"type":15},{"name":555,"slug":556,"type":15},"Audit","audit",{"name":9,"slug":8,"type":15},"2026-06-08T08:08:33.693989",{"slug":560,"name":560,"fn":561,"description":562,"org":563,"tags":564,"stars":23,"repoUrl":24,"updatedAt":570},"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},[565,566,568,569],{"name":555,"slug":556,"type":15},{"name":567,"slug":33,"type":15},"Data Warehouse",{"name":543,"slug":544,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:22:57.67984",{"slug":572,"name":572,"fn":573,"description":574,"org":575,"tags":576,"stars":23,"repoUrl":24,"updatedAt":581},"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},[577,578,579,580],{"name":555,"slug":556,"type":15},{"name":567,"slug":33,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:25:10.936787",{"slug":583,"name":583,"fn":584,"description":585,"org":586,"tags":587,"stars":23,"repoUrl":24,"updatedAt":596},"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},[588,591,594,595],{"name":589,"slug":590,"type":15},"Alerting","alerting",{"name":592,"slug":593,"type":15},"Debugging","debugging",{"name":543,"slug":544,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:24:40.318583",{"slug":598,"name":598,"fn":599,"description":600,"org":601,"tags":602,"stars":23,"repoUrl":24,"updatedAt":612},"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},[603,604,607,608,611],{"name":538,"slug":31,"type":15},{"name":605,"slug":606,"type":15},"Monitoring","monitoring",{"name":543,"slug":544,"type":15},{"name":609,"slug":610,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-07-18T05:10:54.430898",{"slug":614,"name":614,"fn":615,"description":616,"org":617,"tags":618,"stars":23,"repoUrl":24,"updatedAt":629},"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},[619,622,625,626],{"name":620,"slug":621,"type":15},"Automation","automation",{"name":623,"slug":624,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},{"name":627,"slug":628,"type":15},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",61,{"items":632,"total":749},[633,640,646,653,660,667,675,682,696,711,721,739],{"slug":532,"name":532,"fn":533,"description":534,"org":634,"tags":635,"stars":23,"repoUrl":24,"updatedAt":546},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[636,637,638,639],{"name":538,"slug":31,"type":15},{"name":540,"slug":541,"type":15},{"name":543,"slug":544,"type":15},{"name":9,"slug":8,"type":15},{"slug":548,"name":548,"fn":549,"description":550,"org":641,"tags":642,"stars":23,"repoUrl":24,"updatedAt":558},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[643,644,645],{"name":538,"slug":31,"type":15},{"name":555,"slug":556,"type":15},{"name":9,"slug":8,"type":15},{"slug":560,"name":560,"fn":561,"description":562,"org":647,"tags":648,"stars":23,"repoUrl":24,"updatedAt":570},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[649,650,651,652],{"name":555,"slug":556,"type":15},{"name":567,"slug":33,"type":15},{"name":543,"slug":544,"type":15},{"name":9,"slug":8,"type":15},{"slug":572,"name":572,"fn":573,"description":574,"org":654,"tags":655,"stars":23,"repoUrl":24,"updatedAt":581},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[656,657,658,659],{"name":555,"slug":556,"type":15},{"name":567,"slug":33,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},{"slug":583,"name":583,"fn":584,"description":585,"org":661,"tags":662,"stars":23,"repoUrl":24,"updatedAt":596},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[663,664,665,666],{"name":589,"slug":590,"type":15},{"name":592,"slug":593,"type":15},{"name":543,"slug":544,"type":15},{"name":9,"slug":8,"type":15},{"slug":598,"name":598,"fn":599,"description":600,"org":668,"tags":669,"stars":23,"repoUrl":24,"updatedAt":612},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[670,671,672,673,674],{"name":538,"slug":31,"type":15},{"name":605,"slug":606,"type":15},{"name":543,"slug":544,"type":15},{"name":609,"slug":610,"type":15},{"name":9,"slug":8,"type":15},{"slug":614,"name":614,"fn":615,"description":616,"org":676,"tags":677,"stars":23,"repoUrl":24,"updatedAt":629},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[678,679,680,681],{"name":620,"slug":621,"type":15},{"name":623,"slug":624,"type":15},{"name":9,"slug":8,"type":15},{"name":627,"slug":628,"type":15},{"slug":683,"name":683,"fn":684,"description":685,"org":686,"tags":687,"stars":23,"repoUrl":24,"updatedAt":695},"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},[688,689,690,693,694],{"name":538,"slug":31,"type":15},{"name":592,"slug":593,"type":15},{"name":691,"slug":692,"type":15},"Frontend","frontend",{"name":543,"slug":544,"type":15},{"name":9,"slug":8,"type":15},"2026-05-07T05:56:19.828048",{"slug":697,"name":697,"fn":698,"description":699,"org":700,"tags":701,"stars":23,"repoUrl":24,"updatedAt":710},"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},[702,705,706,707],{"name":703,"slug":704,"type":15},"API Development","api-development",{"name":691,"slug":692,"type":15},{"name":9,"slug":8,"type":15},{"name":708,"slug":709,"type":15},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":712,"name":712,"fn":713,"description":714,"org":715,"tags":716,"stars":23,"repoUrl":24,"updatedAt":720},"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},[717,718,719],{"name":703,"slug":704,"type":15},{"name":609,"slug":610,"type":15},{"name":9,"slug":8,"type":15},"2026-07-15T05:29:58.442727",{"slug":722,"name":722,"fn":723,"description":724,"org":725,"tags":726,"stars":23,"repoUrl":24,"updatedAt":738},"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},[727,728,731,732,735],{"name":620,"slug":621,"type":15},{"name":729,"slug":730,"type":15},"Email","email",{"name":9,"slug":8,"type":15},{"name":733,"slug":734,"type":15},"Reporting","reporting",{"name":736,"slug":737,"type":15},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":740,"name":740,"fn":741,"description":742,"org":743,"tags":744,"stars":23,"repoUrl":24,"updatedAt":748},"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},[745,746,747],{"name":538,"slug":31,"type":15},{"name":703,"slug":704,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:29.624498",231]