[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-context-layer-health-check":3,"mdc-1bxcbn-key":46,"related-repo-posthog-context-layer-health-check":140,"related-org-posthog-context-layer-health-check":237},{"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},"context-layer-health-check","review context wiki quality","Semantic review of context wiki quality after deterministic consolidation",{"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},"Documentation","documentation",{"name":18,"slug":19,"type":13},"Knowledge Management","knowledge-management",35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-08-26T04:12:23.009908",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\u002Fcontext_layer\u002Fskills\u002Fcontext-layer-health-check","---\nname: context-layer-health-check\ndescription: Semantic review of context wiki quality after deterministic consolidation\n---\n\n# Context layer health check\n\nRead recent `wiki-miss:` lines from `git log --merges` and use them as the priority signal. Review for contradictory active claims, unsupported conclusions, repeated low-value activity, stale priorities the report cannot detect, near-duplicate subjects, concepts without an owning page, and sources worth backfilling.\n\nFix what evidence supports. Leave unresolved conflicts as `**Disagreement:**` markers and record remaining work in the run summary. Finish with `scripts\u002Flint` and `scripts\u002Flint --report`.\n\nDo not edit `AGENTS.md`, `CLAUDE.md`, generated indexes, `scripts\u002F`, or Space paths. The server owns wiki structure and tooling.\n",{"data":47,"body":48},{"name":4,"description":6},{"type":49,"children":50},"root",[51,59,82,111],{"type":52,"tag":53,"props":54,"children":55},"element","h1",{"id":4},[56],{"type":57,"value":58},"text","Context layer health check",{"type":52,"tag":60,"props":61,"children":62},"p",{},[63,65,72,74,80],{"type":57,"value":64},"Read recent ",{"type":52,"tag":66,"props":67,"children":69},"code",{"className":68},[],[70],{"type":57,"value":71},"wiki-miss:",{"type":57,"value":73}," lines from ",{"type":52,"tag":66,"props":75,"children":77},{"className":76},[],[78],{"type":57,"value":79},"git log --merges",{"type":57,"value":81}," and use them as the priority signal. Review for contradictory active claims, unsupported conclusions, repeated low-value activity, stale priorities the report cannot detect, near-duplicate subjects, concepts without an owning page, and sources worth backfilling.",{"type":52,"tag":60,"props":83,"children":84},{},[85,87,93,95,101,103,109],{"type":57,"value":86},"Fix what evidence supports. Leave unresolved conflicts as ",{"type":52,"tag":66,"props":88,"children":90},{"className":89},[],[91],{"type":57,"value":92},"**Disagreement:**",{"type":57,"value":94}," markers and record remaining work in the run summary. Finish with ",{"type":52,"tag":66,"props":96,"children":98},{"className":97},[],[99],{"type":57,"value":100},"scripts\u002Flint",{"type":57,"value":102}," and ",{"type":52,"tag":66,"props":104,"children":106},{"className":105},[],[107],{"type":57,"value":108},"scripts\u002Flint --report",{"type":57,"value":110},".",{"type":52,"tag":60,"props":112,"children":113},{},[114,116,122,124,130,132,138],{"type":57,"value":115},"Do not edit ",{"type":52,"tag":66,"props":117,"children":119},{"className":118},[],[120],{"type":57,"value":121},"AGENTS.md",{"type":57,"value":123},", ",{"type":52,"tag":66,"props":125,"children":127},{"className":126},[],[128],{"type":57,"value":129},"CLAUDE.md",{"type":57,"value":131},", generated indexes, ",{"type":52,"tag":66,"props":133,"children":135},{"className":134},[],[136],{"type":57,"value":137},"scripts\u002F",{"type":57,"value":139},", or Space paths. The server owns wiki structure and tooling.",{"items":141,"total":236},[142,158,170,182,194,207,223],{"slug":143,"name":143,"fn":144,"description":145,"org":146,"tags":147,"stars":20,"repoUrl":21,"updatedAt":157},"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},[148,150,153,156],{"name":149,"slug":28,"type":13},"Analytics",{"name":151,"slug":152,"type":13},"Cost Optimization","cost-optimization",{"name":154,"slug":155,"type":13},"Observability","observability",{"name":9,"slug":8,"type":13},"2026-08-13T04:28:38.012786",{"slug":159,"name":159,"fn":160,"description":161,"org":162,"tags":163,"stars":20,"repoUrl":21,"updatedAt":169},"analyzing-task-runs","analyze PostHog task run efficiency","Analyze a completed PostHog task run for inefficiencies — environment failures, missing CLI tools, verbose commands, redundant work, wasted retries — and file evidence-backed findings through the report_insight tool. Use when a task asks to analyze a run, produce run insights or a task analysis, or review a run's efficiency from an attached run log. Covers the log query protocol (bounded jq queries over the raw JSONL), both log schemas, the finding taxonomy, and evidence verification.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[164,167,168],{"name":165,"slug":166,"type":13},"Debugging","debugging",{"name":154,"slug":155,"type":13},{"name":9,"slug":8,"type":13},"2026-08-26T03:35:51.541494",{"slug":171,"name":171,"fn":172,"description":173,"org":174,"tags":175,"stars":20,"repoUrl":21,"updatedAt":181},"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},[176,177,180],{"name":149,"slug":28,"type":13},{"name":178,"slug":179,"type":13},"Audit","audit",{"name":9,"slug":8,"type":13},"2026-06-08T08:08:33.693989",{"slug":183,"name":183,"fn":184,"description":185,"org":186,"tags":187,"stars":20,"repoUrl":21,"updatedAt":193},"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},[188,189,191,192],{"name":178,"slug":179,"type":13},{"name":190,"slug":30,"type":13},"Data Warehouse",{"name":154,"slug":155,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:22:57.67984",{"slug":195,"name":195,"fn":196,"description":197,"org":198,"tags":199,"stars":20,"repoUrl":21,"updatedAt":206},"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},[200,201,202,205],{"name":178,"slug":179,"type":13},{"name":190,"slug":30,"type":13},{"name":203,"slug":204,"type":13},"Performance","performance",{"name":9,"slug":8,"type":13},"2026-06-18T08:25:10.936787",{"slug":208,"name":208,"fn":209,"description":210,"org":211,"tags":212,"stars":20,"repoUrl":21,"updatedAt":222},"authoring-data-quality-checks","author data quality checks for warehouse tables","Adds and runs data quality checks (dbt-test style assertions) on a project's warehouse tables and saved-query views: not-null, uniqueness, accepted values, referential integrity, row-count bounds, freshness, and custom HogQL. Use when asked to test a model, validate a view, check for nulls or duplicates, add data quality checks, find out why a number looks wrong, or judge whether a warehouse table is trustworthy before using it in an analysis. To describe what data *means* (metrics, certifications, joins), see setting-up-data-catalog instead. Trigger terms: data quality, data test, dbt test, not null check, uniqueness check, freshness check, referential integrity, row count check, validate model, is this table trustworthy.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[213,214,217,220],{"name":149,"slug":28,"type":13},{"name":215,"slug":216,"type":13},"Data Engineering","data-engineering",{"name":218,"slug":219,"type":13},"Data Quality","data-quality",{"name":221,"slug":221,"type":13},"dbt","2026-08-19T03:59:25.329274",{"slug":224,"name":224,"fn":225,"description":226,"org":227,"tags":228,"stars":20,"repoUrl":21,"updatedAt":235},"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},[229,232,233,234],{"name":230,"slug":231,"type":13},"Alerting","alerting",{"name":165,"slug":166,"type":13},{"name":154,"slug":155,"type":13},{"name":9,"slug":8,"type":13},"2026-08-13T04:28:36.025103",83,{"items":238,"total":368},[239,246,252,258,265,272,279,286,302,319,337,353],{"slug":143,"name":143,"fn":144,"description":145,"org":240,"tags":241,"stars":20,"repoUrl":21,"updatedAt":157},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[242,243,244,245],{"name":149,"slug":28,"type":13},{"name":151,"slug":152,"type":13},{"name":154,"slug":155,"type":13},{"name":9,"slug":8,"type":13},{"slug":159,"name":159,"fn":160,"description":161,"org":247,"tags":248,"stars":20,"repoUrl":21,"updatedAt":169},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[249,250,251],{"name":165,"slug":166,"type":13},{"name":154,"slug":155,"type":13},{"name":9,"slug":8,"type":13},{"slug":171,"name":171,"fn":172,"description":173,"org":253,"tags":254,"stars":20,"repoUrl":21,"updatedAt":181},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[255,256,257],{"name":149,"slug":28,"type":13},{"name":178,"slug":179,"type":13},{"name":9,"slug":8,"type":13},{"slug":183,"name":183,"fn":184,"description":185,"org":259,"tags":260,"stars":20,"repoUrl":21,"updatedAt":193},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[261,262,263,264],{"name":178,"slug":179,"type":13},{"name":190,"slug":30,"type":13},{"name":154,"slug":155,"type":13},{"name":9,"slug":8,"type":13},{"slug":195,"name":195,"fn":196,"description":197,"org":266,"tags":267,"stars":20,"repoUrl":21,"updatedAt":206},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[268,269,270,271],{"name":178,"slug":179,"type":13},{"name":190,"slug":30,"type":13},{"name":203,"slug":204,"type":13},{"name":9,"slug":8,"type":13},{"slug":208,"name":208,"fn":209,"description":210,"org":273,"tags":274,"stars":20,"repoUrl":21,"updatedAt":222},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[275,276,277,278],{"name":149,"slug":28,"type":13},{"name":215,"slug":216,"type":13},{"name":218,"slug":219,"type":13},{"name":221,"slug":221,"type":13},{"slug":224,"name":224,"fn":225,"description":226,"org":280,"tags":281,"stars":20,"repoUrl":21,"updatedAt":235},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[282,283,284,285],{"name":230,"slug":231,"type":13},{"name":165,"slug":166,"type":13},{"name":154,"slug":155,"type":13},{"name":9,"slug":8,"type":13},{"slug":287,"name":287,"fn":288,"description":289,"org":290,"tags":291,"stars":20,"repoUrl":21,"updatedAt":301},"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},[292,293,296,297,300],{"name":149,"slug":28,"type":13},{"name":294,"slug":295,"type":13},"Monitoring","monitoring",{"name":154,"slug":155,"type":13},{"name":298,"slug":299,"type":13},"Operations","operations",{"name":9,"slug":8,"type":13},"2026-08-13T04:28:20.051489",{"slug":303,"name":303,"fn":304,"description":305,"org":306,"tags":307,"stars":20,"repoUrl":21,"updatedAt":318},"building-canvases","create and edit PostHog canvases","Create or edit a PostHog freeform 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 standalone canvas app, or when a freeform canvas id is given as the publish target. For grid\u002Fhome canvases, widget placements, or reusable components, use composing-grid-canvases instead. 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},[308,311,314,315],{"name":309,"slug":310,"type":13},"Automation","automation",{"name":312,"slug":313,"type":13},"Design","design",{"name":9,"slug":8,"type":13},{"name":316,"slug":317,"type":13},"Prototyping","prototyping","2026-08-26T03:35:54.632968",{"slug":320,"name":320,"fn":321,"description":322,"org":323,"tags":324,"stars":20,"repoUrl":21,"updatedAt":336},"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},[325,328,329,332,335],{"name":326,"slug":327,"type":13},"CSS","css",{"name":312,"slug":313,"type":13},{"name":330,"slug":331,"type":13},"Graphics","graphics",{"name":333,"slug":334,"type":13},"HTML","html",{"name":9,"slug":8,"type":13},"2026-08-22T03:23:06.404123",{"slug":338,"name":338,"fn":339,"description":340,"org":341,"tags":342,"stars":20,"repoUrl":21,"updatedAt":352},"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},[343,344,347,349],{"name":312,"slug":313,"type":13},{"name":345,"slug":346,"type":13},"Frontend","frontend",{"name":348,"slug":36,"type":13},"React",{"name":350,"slug":351,"type":13},"UI Components","ui-components","2026-08-26T03:35:53.599633",{"slug":354,"name":354,"fn":355,"description":356,"org":357,"tags":358,"stars":20,"repoUrl":21,"updatedAt":367},"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},[359,360,363,364],{"name":309,"slug":310,"type":13},{"name":361,"slug":362,"type":13},"MCP","mcp",{"name":9,"slug":8,"type":13},{"name":365,"slug":366,"type":13},"Workflow Automation","workflow-automation","2026-08-10T04:16:26.294119",257]