[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-signals-scout-silent-failure":3,"mdc-3qwzq9-key":39,"related-org-posthog-signals-scout-silent-failure":315,"related-repo-posthog-signals-scout-silent-failure":493},{"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":34,"sourceUrl":37,"mdContent":38},"signals-scout-silent-failure","detect and diagnose silent application failures","Watches the completion rate of one named core action for breaks from its own norm, and reports the likely cause – with swallowed exceptions as the first thing it looks for.\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},"Observability","observability","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"Monitoring","monitoring",{"name":21,"slug":22,"type":15},"Debugging","debugging",1091,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog.com","2026-08-10T04:45:56.482808",null,856,[29,30,31,32,8,33],"design","docs","gatsby","handbook","tailwindcss",{"repoUrl":24,"stars":23,"forks":27,"topics":35,"description":36},[29,30,31,32,8,33],"Official docs, website, and handbook for PostHog.","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog.com\u002Ftree\u002FHEAD\u002Fcontents\u002Fpocket-guides\u002Fself-driving\u002Fsilent-failure-core-action","---\nname: signals-scout-silent-failure\ndescription: >\n  Watches the completion rate of one named core action for breaks from its own norm, and\n  reports the likely cause – with swallowed exceptions as the first thing it looks for.\nallowed_tools:\n  - emit_report\n  - edit_report\n---\n\n# Silent failure in the core action\n\nWatch one named flow for failures that never surface as errors.\n\nThe mechanism this is built around: **something caught the failure.** A retry wrapper, a\n`try`\u002F`catch` with a log line, a fallback that returns an empty result. The user sees a spinner\nand then nothing, no error page renders, no alert fires, and the only trace is the completion\nrate quietly dropping. That's what makes it silent, and it's what this scout looks for first.\n\nNarrower than `signals-scout-anomaly-detection`, which builds a durable watchlist of the\ninsights a team actually looks at and scores each one against a seasonality-matched baseline.\nThis one watches a single flow you name, every run, whether or not anyone has built an insight\nfor it. If the core action is already on that scout's watchlist and you're hearing about breaks\nin time, you don't need both.\n\nDaily is the fleet default. For a flow where hours matter, set `run_interval_minutes` to 60 when\nyou create the scout – the tradeoff is that hourly buckets are noisier, so raise the volume\nfloor below to match.\n\n## Discriminator\n\nEmit a report when the **completion rate** – completions divided by attempts – breaks from its\ntrailing two-week norm for the same day of week. Write nothing when attempts and completions\nmoved together and the rate held: that's a traffic change, not breakage.\n\nAttempts are the disqualifier check, not half the trigger. Watching two counts separately leaves\nyou stuck the moment both move a little; watching the rate doesn't.\n\n### The bar\n\nA starting point, to be tuned against what this flow's data actually does:\n\n- a completion rate **≥10 points below** its trailing 14-day median for the same weekday, on a\n  complete bucket, and\n- **≥500 attempts** in that bucket.\n\nThe volume floor matters more than the threshold. A completion rate computed on 40 attempts is\nnoise, and a scout that fires on it is exactly the crying-wolf failure the discriminator is\nmeant to prevent. If the flow doesn't clear the floor, widen the bucket rather than lowering the\nbar, and write what you chose to the scratchpad.\n\n## Explore\n\n1. **Confirm the instrumentation still works.** Before anything else: is the completion event\n   still firing at all, and was it renamed, moved, or removed in the deploy window? A broken\n   tracking call looks identical to a broken product – attempts flat, completions gone – and it\n   is the most likely false positive for this scout. Check the event's total volume across all\n   properties, not just within the flow. `signals-scout-observability-gaps` watches this kind of\n   drift more broadly.\n2. **Check whether the drop is uniform.** Did the completion rate fall across every segment, or\n   only inside a new or shifted one? Steady attempts with a falling rate is also the shape of a\n   traffic-composition change – a campaign bringing lower-intent users, a new geo, a bot wave.\n   Nothing is broken in that case, and the rate framing alone won't catch it. Break down by\n   source, device, geo, and new-vs-returning before going further.\n3. **Find what was caught.** Look for new or spiking error-tracking issues on the same code\n   path, weighting **handled** exceptions – the ones that never reached the user. A caught\n   timeout, a retry that exhausted, a fallback that returned empty. This is the mechanism the\n   whole scout is built around, so look here before looking anywhere else.\n4. **Check the failures that never reached your server.** If Error Tracking is clean, the failure\n   may not have made it out of the browser: a dropped request, an ad blocker or CSP rule\n   blocking the call, the tab closing mid-request. Session Replay is the only thing that sees\n   these – look for stalls, rage clicks, and abandonment at a consistent point in the flow.\n5. **Locate it in the flow.** If intermediate events exist, find the step where the drop happens.\n   Without them you can say the flow broke, but not where.\n6. **Tie it to a deploy.** Where a deploy sits in the window, include the commit range.\n7. Name the most likely cause in the report. A rate that moved with no cause attached is\n   something the reader still has to go investigate themselves.\n\n## Disqualifiers\n\n- Attempts and completions moved together – the rate held.\n- The completion event stopped firing entirely, or was renamed in the window. That's an\n  instrumentation finding, not a product one, and it should say so.\n- The rate fell only inside one new or shifted segment – that's a mix change, not breakage.\n- The bucket is below the volume floor.\n- The change is within normal weekday\u002Fweekend variance.\n- A known, announced maintenance window covers the period.\n",{"data":40,"body":44},{"name":4,"description":6,"allowed_tools":41},[42,43],"emit_report","edit_report",{"type":45,"children":46},"root",[47,56,62,92,105,118,125,137,142,149,154,181,186,192,276,282],{"type":48,"tag":49,"props":50,"children":52},"element","h1",{"id":51},"silent-failure-in-the-core-action",[53],{"type":54,"value":55},"text","Silent failure in the core action",{"type":48,"tag":57,"props":58,"children":59},"p",{},[60],{"type":54,"value":61},"Watch one named flow for failures that never surface as errors.",{"type":48,"tag":57,"props":63,"children":64},{},[65,67,73,75,82,84,90],{"type":54,"value":66},"The mechanism this is built around: ",{"type":48,"tag":68,"props":69,"children":70},"strong",{},[71],{"type":54,"value":72},"something caught the failure.",{"type":54,"value":74}," A retry wrapper, a\n",{"type":48,"tag":76,"props":77,"children":79},"code",{"className":78},[],[80],{"type":54,"value":81},"try",{"type":54,"value":83},"\u002F",{"type":48,"tag":76,"props":85,"children":87},{"className":86},[],[88],{"type":54,"value":89},"catch",{"type":54,"value":91}," with a log line, a fallback that returns an empty result. The user sees a spinner\nand then nothing, no error page renders, no alert fires, and the only trace is the completion\nrate quietly dropping. That's what makes it silent, and it's what this scout looks for first.",{"type":48,"tag":57,"props":93,"children":94},{},[95,97,103],{"type":54,"value":96},"Narrower than ",{"type":48,"tag":76,"props":98,"children":100},{"className":99},[],[101],{"type":54,"value":102},"signals-scout-anomaly-detection",{"type":54,"value":104},", which builds a durable watchlist of the\ninsights a team actually looks at and scores each one against a seasonality-matched baseline.\nThis one watches a single flow you name, every run, whether or not anyone has built an insight\nfor it. If the core action is already on that scout's watchlist and you're hearing about breaks\nin time, you don't need both.",{"type":48,"tag":57,"props":106,"children":107},{},[108,110,116],{"type":54,"value":109},"Daily is the fleet default. For a flow where hours matter, set ",{"type":48,"tag":76,"props":111,"children":113},{"className":112},[],[114],{"type":54,"value":115},"run_interval_minutes",{"type":54,"value":117}," to 60 when\nyou create the scout – the tradeoff is that hourly buckets are noisier, so raise the volume\nfloor below to match.",{"type":48,"tag":119,"props":120,"children":122},"h2",{"id":121},"discriminator",[123],{"type":54,"value":124},"Discriminator",{"type":48,"tag":57,"props":126,"children":127},{},[128,130,135],{"type":54,"value":129},"Emit a report when the ",{"type":48,"tag":68,"props":131,"children":132},{},[133],{"type":54,"value":134},"completion rate",{"type":54,"value":136}," – completions divided by attempts – breaks from its\ntrailing two-week norm for the same day of week. Write nothing when attempts and completions\nmoved together and the rate held: that's a traffic change, not breakage.",{"type":48,"tag":57,"props":138,"children":139},{},[140],{"type":54,"value":141},"Attempts are the disqualifier check, not half the trigger. Watching two counts separately leaves\nyou stuck the moment both move a little; watching the rate doesn't.",{"type":48,"tag":143,"props":144,"children":146},"h3",{"id":145},"the-bar",[147],{"type":54,"value":148},"The bar",{"type":48,"tag":57,"props":150,"children":151},{},[152],{"type":54,"value":153},"A starting point, to be tuned against what this flow's data actually does:",{"type":48,"tag":155,"props":156,"children":157},"ul",{},[158,171],{"type":48,"tag":159,"props":160,"children":161},"li",{},[162,164,169],{"type":54,"value":163},"a completion rate ",{"type":48,"tag":68,"props":165,"children":166},{},[167],{"type":54,"value":168},"≥10 points below",{"type":54,"value":170}," its trailing 14-day median for the same weekday, on a\ncomplete bucket, and",{"type":48,"tag":159,"props":172,"children":173},{},[174,179],{"type":48,"tag":68,"props":175,"children":176},{},[177],{"type":54,"value":178},"≥500 attempts",{"type":54,"value":180}," in that bucket.",{"type":48,"tag":57,"props":182,"children":183},{},[184],{"type":54,"value":185},"The volume floor matters more than the threshold. A completion rate computed on 40 attempts is\nnoise, and a scout that fires on it is exactly the crying-wolf failure the discriminator is\nmeant to prevent. If the flow doesn't clear the floor, widen the bucket rather than lowering the\nbar, and write what you chose to the scratchpad.",{"type":48,"tag":119,"props":187,"children":189},{"id":188},"explore",[190],{"type":54,"value":191},"Explore",{"type":48,"tag":193,"props":194,"children":195},"ol",{},[196,214,224,241,251,261,271],{"type":48,"tag":159,"props":197,"children":198},{},[199,204,206,212],{"type":48,"tag":68,"props":200,"children":201},{},[202],{"type":54,"value":203},"Confirm the instrumentation still works.",{"type":54,"value":205}," Before anything else: is the completion event\nstill firing at all, and was it renamed, moved, or removed in the deploy window? A broken\ntracking call looks identical to a broken product – attempts flat, completions gone – and it\nis the most likely false positive for this scout. Check the event's total volume across all\nproperties, not just within the flow. ",{"type":48,"tag":76,"props":207,"children":209},{"className":208},[],[210],{"type":54,"value":211},"signals-scout-observability-gaps",{"type":54,"value":213}," watches this kind of\ndrift more broadly.",{"type":48,"tag":159,"props":215,"children":216},{},[217,222],{"type":48,"tag":68,"props":218,"children":219},{},[220],{"type":54,"value":221},"Check whether the drop is uniform.",{"type":54,"value":223}," Did the completion rate fall across every segment, or\nonly inside a new or shifted one? Steady attempts with a falling rate is also the shape of a\ntraffic-composition change – a campaign bringing lower-intent users, a new geo, a bot wave.\nNothing is broken in that case, and the rate framing alone won't catch it. Break down by\nsource, device, geo, and new-vs-returning before going further.",{"type":48,"tag":159,"props":225,"children":226},{},[227,232,234,239],{"type":48,"tag":68,"props":228,"children":229},{},[230],{"type":54,"value":231},"Find what was caught.",{"type":54,"value":233}," Look for new or spiking error-tracking issues on the same code\npath, weighting ",{"type":48,"tag":68,"props":235,"children":236},{},[237],{"type":54,"value":238},"handled",{"type":54,"value":240}," exceptions – the ones that never reached the user. A caught\ntimeout, a retry that exhausted, a fallback that returned empty. This is the mechanism the\nwhole scout is built around, so look here before looking anywhere else.",{"type":48,"tag":159,"props":242,"children":243},{},[244,249],{"type":48,"tag":68,"props":245,"children":246},{},[247],{"type":54,"value":248},"Check the failures that never reached your server.",{"type":54,"value":250}," If Error Tracking is clean, the failure\nmay not have made it out of the browser: a dropped request, an ad blocker or CSP rule\nblocking the call, the tab closing mid-request. Session Replay is the only thing that sees\nthese – look for stalls, rage clicks, and abandonment at a consistent point in the flow.",{"type":48,"tag":159,"props":252,"children":253},{},[254,259],{"type":48,"tag":68,"props":255,"children":256},{},[257],{"type":54,"value":258},"Locate it in the flow.",{"type":54,"value":260}," If intermediate events exist, find the step where the drop happens.\nWithout them you can say the flow broke, but not where.",{"type":48,"tag":159,"props":262,"children":263},{},[264,269],{"type":48,"tag":68,"props":265,"children":266},{},[267],{"type":54,"value":268},"Tie it to a deploy.",{"type":54,"value":270}," Where a deploy sits in the window, include the commit range.",{"type":48,"tag":159,"props":272,"children":273},{},[274],{"type":54,"value":275},"Name the most likely cause in the report. A rate that moved with no cause attached is\nsomething the reader still has to go investigate themselves.",{"type":48,"tag":119,"props":277,"children":279},{"id":278},"disqualifiers",[280],{"type":54,"value":281},"Disqualifiers",{"type":48,"tag":155,"props":283,"children":284},{},[285,290,295,300,305,310],{"type":48,"tag":159,"props":286,"children":287},{},[288],{"type":54,"value":289},"Attempts and completions moved together – the rate held.",{"type":48,"tag":159,"props":291,"children":292},{},[293],{"type":54,"value":294},"The completion event stopped firing entirely, or was renamed in the window. That's an\ninstrumentation finding, not a product one, and it should say so.",{"type":48,"tag":159,"props":296,"children":297},{},[298],{"type":54,"value":299},"The rate fell only inside one new or shifted segment – that's a mix change, not breakage.",{"type":48,"tag":159,"props":301,"children":302},{},[303],{"type":54,"value":304},"The bucket is below the volume floor.",{"type":48,"tag":159,"props":306,"children":307},{},[308],{"type":54,"value":309},"The change is within normal weekday\u002Fweekend variance.",{"type":48,"tag":159,"props":311,"children":312},{},[313],{"type":54,"value":314},"A known, announced maintenance window covers the period.",{"items":316,"total":492},[317,334,346,359,372,385,399,415,433,450,465,477],{"slug":318,"name":318,"fn":319,"description":320,"org":321,"tags":322,"stars":331,"repoUrl":332,"updatedAt":333},"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},[323,326,329,330],{"name":324,"slug":325,"type":15},"Analytics","analytics",{"name":327,"slug":328,"type":15},"Cost Optimization","cost-optimization",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-08-10T04:16:25.279222",{"slug":335,"name":335,"fn":336,"description":337,"org":338,"tags":339,"stars":331,"repoUrl":332,"updatedAt":345},"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},[340,341,344],{"name":324,"slug":325,"type":15},{"name":342,"slug":343,"type":15},"Audit","audit",{"name":9,"slug":8,"type":15},"2026-06-08T08:08:33.693989",{"slug":347,"name":347,"fn":348,"description":349,"org":350,"tags":351,"stars":331,"repoUrl":332,"updatedAt":358},"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},[352,353,356,357],{"name":342,"slug":343,"type":15},{"name":354,"slug":355,"type":15},"Data Warehouse","data-warehouse",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:22:57.67984",{"slug":360,"name":360,"fn":361,"description":362,"org":363,"tags":364,"stars":331,"repoUrl":332,"updatedAt":371},"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},[365,366,367,370],{"name":342,"slug":343,"type":15},{"name":354,"slug":355,"type":15},{"name":368,"slug":369,"type":15},"Performance","performance",{"name":9,"slug":8,"type":15},"2026-06-18T08:25:10.936787",{"slug":373,"name":373,"fn":374,"description":375,"org":376,"tags":377,"stars":331,"repoUrl":332,"updatedAt":384},"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},[378,381,382,383],{"name":379,"slug":380,"type":15},"Alerting","alerting",{"name":21,"slug":22,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:24:40.318583",{"slug":386,"name":386,"fn":387,"description":388,"org":389,"tags":390,"stars":331,"repoUrl":332,"updatedAt":398},"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},[391,392,393,394,397],{"name":324,"slug":325,"type":15},{"name":18,"slug":19,"type":15},{"name":13,"slug":14,"type":15},{"name":395,"slug":396,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-07-18T05:10:54.430898",{"slug":400,"name":400,"fn":401,"description":402,"org":403,"tags":404,"stars":331,"repoUrl":332,"updatedAt":414},"building-canvases","create and edit PostHog canvases","Create or edit a PostHog canvas — a sandboxed browser application (data board, document, form, small tool, graphics experiment) stored in PostHog and rendered by the desktop\u002Fweb app. Use when a task asks to build, generate, update, or fix a canvas, or when a canvas id is given as the publish target. Covers resolving or creating the target canvas, choosing an implementation approach (React + Quill vs plain HTML\u002Fbrowser APIs), the read → edit → validate → publish → build loop, and which companion canvas skills to load for the details.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[405,408,410,411],{"name":406,"slug":407,"type":15},"Automation","automation",{"name":409,"slug":29,"type":15},"Design",{"name":9,"slug":8,"type":15},{"name":412,"slug":413,"type":15},"Prototyping","prototyping","2026-08-06T06:09:29.946969",{"slug":416,"name":416,"fn":417,"description":418,"org":419,"tags":420,"stars":331,"repoUrl":332,"updatedAt":432},"building-html-canvases","author HTML and CSS PostHog canvases","Author a PostHog canvas with semantic HTML, CSS, and direct browser APIs — documents, articles, generative graphics, 2D canvas and WebGL experiences, and focused experiments where React components add no useful structure. Use after building-canvases has routed a canvas request to a plain-HTML\u002Fbrowser-API implementation. Covers the thin component wrapper the current runtime requires, styling and theming without Quill, drawing surfaces, and animation\u002Fcleanup patterns.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[421,424,425,428,431],{"name":422,"slug":423,"type":15},"CSS","css",{"name":409,"slug":29,"type":15},{"name":426,"slug":427,"type":15},"Graphics","graphics",{"name":429,"slug":430,"type":15},"HTML","html",{"name":9,"slug":8,"type":15},"2026-08-06T06:09:30.313848",{"slug":434,"name":434,"fn":435,"description":436,"org":437,"tags":438,"stars":331,"repoUrl":332,"updatedAt":449},"building-react-quill-canvases","build React and Quill canvases","Author the React + Quill implementation of a PostHog canvas: the single-component contract, the allowed imports, Quill (PostHog's design system) component and composition rules, theme-aware design tokens, loading skeletons, and the in-canvas date picker. Use after building-canvases has routed a canvas request to a React implementation — dashboards, data boards, forms, tools, or any canvas that should look native to PostHog.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[439,440,443,446],{"name":409,"slug":29,"type":15},{"name":441,"slug":442,"type":15},"Frontend","frontend",{"name":444,"slug":445,"type":15},"React","react",{"name":447,"slug":448,"type":15},"UI Components","ui-components","2026-08-06T06:09:18.633724",{"slug":451,"name":451,"fn":452,"description":453,"org":454,"tags":455,"stars":331,"repoUrl":332,"updatedAt":464},"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},[456,457,460,461],{"name":406,"slug":407,"type":15},{"name":458,"slug":459,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},{"name":462,"slug":463,"type":15},"Workflow Automation","workflow-automation","2026-08-10T04:16:26.294119",{"slug":466,"name":466,"fn":467,"description":468,"org":469,"tags":470,"stars":331,"repoUrl":332,"updatedAt":476},"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},[471,472,473,474,475],{"name":324,"slug":325,"type":15},{"name":21,"slug":22,"type":15},{"name":441,"slug":442,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-05-07T05:56:19.828048",{"slug":478,"name":478,"fn":479,"description":480,"org":481,"tags":482,"stars":331,"repoUrl":332,"updatedAt":491},"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},[483,486,487,488],{"name":484,"slug":485,"type":15},"API Development","api-development",{"name":441,"slug":442,"type":15},{"name":9,"slug":8,"type":15},{"name":489,"slug":490,"type":15},"SDK","sdk","2026-06-08T08:08:34.929454",248,{"items":494,"total":542},[495,509,524,531],{"slug":496,"name":496,"fn":497,"description":498,"org":499,"tags":500,"stars":23,"repoUrl":24,"updatedAt":508},"signals-scout-ai-cost","monitor AI feature costs and performance","Watches cost per conversation for AI features and reports when it breaks from its recent norm while volume holds steady, attributing the change to a model, prompt, cache, or retry cause.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[501,502,505,506,507],{"name":327,"slug":328,"type":15},{"name":503,"slug":504,"type":15},"LLM","llm",{"name":18,"slug":19,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-08-10T04:45:48.936016",{"slug":510,"name":510,"fn":511,"description":512,"org":513,"tags":514,"stars":23,"repoUrl":24,"updatedAt":523},"signals-scout-flag-debt","identify and remove stale feature flags","Finds feature flags whose decision is over but which are still evaluated in production – terminal rollouts left in place, or keys that no longer appear in any connected repo.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[515,518,519,520],{"name":516,"slug":517,"type":15},"Feature Flags","feature-flags",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},{"name":521,"slug":522,"type":15},"Tech Debt","tech-debt","2026-08-10T04:45:50.019808",{"slug":4,"name":4,"fn":5,"description":6,"org":525,"tags":526,"stars":23,"repoUrl":24,"updatedAt":25},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[527,528,529,530],{"name":21,"slug":22,"type":15},{"name":18,"slug":19,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},{"slug":532,"name":532,"fn":533,"description":534,"org":535,"tags":536,"stars":23,"repoUrl":24,"updatedAt":541},"signals-scout-your-scout","configure PostHog signal scouts","What this scout watches and the condition under which it files a report.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[537,538,539,540],{"name":406,"slug":407,"type":15},{"name":18,"slug":19,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-08-10T04:45:49.295902",4]