[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-checking-deploy-timing":3,"mdc--1wujlj-key":41,"related-repo-posthog-checking-deploy-timing":599,"related-org-posthog-checking-deploy-timing":709},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":26,"repoUrl":27,"updatedAt":28,"license":29,"forks":30,"topics":31,"repo":36,"sourceUrl":39,"mdContent":40},"checking-deploy-timing","correlate PostHog deployments with GitHub commits","Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask \"when was X deployed\", \"is my change live in the US\u002FEU yet\", \"has my PR shipped\", \"did the fix roll out to prod-us\", or otherwise want to know whether\u002Fwhen a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event\u002Fdata volume alone — that only shows when data changed, not when code shipped.",{"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,23],{"name":13,"slug":14,"type":15},"Observability","observability","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"GitHub","github",{"name":21,"slug":22,"type":15},"Git","git",{"name":24,"slug":25,"type":15},"Deployment","deployment",59,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fai-plugin","2026-06-28T07:46:59.53536",null,11,[32,33,34,35],"claude-code-plugin","codex-plugin","cursor-plugin","gemini-cli-extension",{"repoUrl":27,"stars":26,"forks":30,"topics":37,"description":38},[32,33,34,35],"Official PostHog plugin for Claude Code, Cursor, Gemini, Codex and other AI coding tools","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fai-plugin\u002Ftree\u002FHEAD\u002Fskills\u002Fchecking-deploy-timing","---\nname: checking-deploy-timing\ndescription: 'Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask \"when was X deployed\", \"is my change live in the US\u002FEU yet\", \"has my PR shipped\", \"did the fix roll out to prod-us\", or otherwise want to know whether\u002Fwhen a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event\u002Fdata volume alone — that only shows when data changed, not when code shipped.'\n---\n\n# Checking when something was deployed\n\nPostHog's CI writes a deploy marker into the project as an **annotation** every time a commit\nships to an environment. These annotations are `hidden_in_user_interface: true`, so they don't\nshow in the UI and are easy to forget — but they are the source of truth for \"when did this go\nout\". Always check them when staff ask about deploy timing, rather than inferring from when a\nmetric or event volume changed (that conflates a capture change with a query\u002Fcode change).\n\n## The deploy annotations\n\nList them with `posthog:annotations-list` using `{\"search\": \"deploy\"}`. Each deploy marker looks like:\n\n- `content`: `Deployed PostHog\u002Fposthog@\u003Csha> to \u003Cenv>` — env is `prod-us`, `prod-eu`, or `dev`\n- `creation_type`: `GIT`\n- `scope`: `organization`\n- `hidden_in_user_interface`: `true`\n- `date_marker`: the deploy time (UTC)\n\nThey're returned newest-first; paginate with `offset` if you need to go further back.\n\n## Workflow\n\n1. **Find the change's merge commit.** Identify the PR (e.g. `gh search prs --repo PostHog\u002Fposthog --author \u003Cuser> \"\u003Ckeywords>\"`), then `gh pr view \u003Cn> --repo PostHog\u002Fposthog --json number,title,mergedAt,mergeCommit,state`. Note the merge commit SHA and `mergedAt`.\n2. **List the target environment's deploys around the merge, oldest-first.** Match the region the user asked about (`prod-us` for \"the US\", `prod-eu` for \"the EU\"). The annotations come back **newest-first**, so don't just take the first `... to \u003Cenv>` match on page 1 — that's the _most recent_ deploy. Paginate (with `offset`) until you reach markers around `mergedAt`, then consider that environment's deploys in chronological order, starting with the first whose `date_marker` is _after_ `mergedAt`. Check them earliest-first in step 3.\n3. **Confirm the deployed commit actually contains the merge commit.** A later `date_marker` is necessary but not sufficient — a deploy can fire just after the merge yet build a slightly older commit. Verify ancestry:\n\n   ```sh\n   gh api repos\u002FPostHog\u002Fposthog\u002Fcompare\u002F\u003Cmerge_sha>...\u003Cdeployed_sha> --jq '{status,ahead_by,behind_by}'\n   ```\n\n   `behind_by: 0` with `status` `ahead` or `identical` means the deployed commit includes the merge — that's your answer. If `behind_by > 0`, this deploy predates the change; move to the **next newer** deploy of that environment (the next one chronologically) and re-check. The first deploy that passes is the one that shipped the change.\n\n4. **Report** the deploy time (and PR\u002Fcommit) for the region asked about. Mention other regions if relevant — `prod-us` and `prod-eu` usually deploy minutes apart but not simultaneously.\n\n## Notes\n\n- \"Live in the US\" = `prod-us`; \"the EU\" = `prod-eu`. `dev` is the internal staging environment, not customer-facing.\n- For a **query-runner \u002F read-path** change, the new behaviour applies retroactively to all data once deployed — so you can't time it from event volume, only from the deploy annotation. For a **capture** change, event volume for the new property is a secondary cross-check, but the annotation is still the authoritative deploy time.\n",{"data":42,"body":43},{"name":4,"description":6},{"type":44,"children":45},"root",[46,55,78,85,106,211,224,230,539,545,593],{"type":47,"tag":48,"props":49,"children":51},"element","h1",{"id":50},"checking-when-something-was-deployed",[52],{"type":53,"value":54},"text","Checking when something was deployed",{"type":47,"tag":56,"props":57,"children":58},"p",{},[59,61,67,69,76],{"type":53,"value":60},"PostHog's CI writes a deploy marker into the project as an ",{"type":47,"tag":62,"props":63,"children":64},"strong",{},[65],{"type":53,"value":66},"annotation",{"type":53,"value":68}," every time a commit\nships to an environment. These annotations are ",{"type":47,"tag":70,"props":71,"children":73},"code",{"className":72},[],[74],{"type":53,"value":75},"hidden_in_user_interface: true",{"type":53,"value":77},", so they don't\nshow in the UI and are easy to forget — but they are the source of truth for \"when did this go\nout\". Always check them when staff ask about deploy timing, rather than inferring from when a\nmetric or event volume changed (that conflates a capture change with a query\u002Fcode change).",{"type":47,"tag":79,"props":80,"children":82},"h2",{"id":81},"the-deploy-annotations",[83],{"type":53,"value":84},"The deploy annotations",{"type":47,"tag":56,"props":86,"children":87},{},[88,90,96,98,104],{"type":53,"value":89},"List them with ",{"type":47,"tag":70,"props":91,"children":93},{"className":92},[],[94],{"type":53,"value":95},"posthog:annotations-list",{"type":53,"value":97}," using ",{"type":47,"tag":70,"props":99,"children":101},{"className":100},[],[102],{"type":53,"value":103},"{\"search\": \"deploy\"}",{"type":53,"value":105},". Each deploy marker looks like:",{"type":47,"tag":107,"props":108,"children":109},"ul",{},[110,152,168,184,200],{"type":47,"tag":111,"props":112,"children":113},"li",{},[114,120,122,128,130,136,138,144,146],{"type":47,"tag":70,"props":115,"children":117},{"className":116},[],[118],{"type":53,"value":119},"content",{"type":53,"value":121},": ",{"type":47,"tag":70,"props":123,"children":125},{"className":124},[],[126],{"type":53,"value":127},"Deployed PostHog\u002Fposthog@\u003Csha> to \u003Cenv>",{"type":53,"value":129}," — env is ",{"type":47,"tag":70,"props":131,"children":133},{"className":132},[],[134],{"type":53,"value":135},"prod-us",{"type":53,"value":137},", ",{"type":47,"tag":70,"props":139,"children":141},{"className":140},[],[142],{"type":53,"value":143},"prod-eu",{"type":53,"value":145},", or ",{"type":47,"tag":70,"props":147,"children":149},{"className":148},[],[150],{"type":53,"value":151},"dev",{"type":47,"tag":111,"props":153,"children":154},{},[155,161,162],{"type":47,"tag":70,"props":156,"children":158},{"className":157},[],[159],{"type":53,"value":160},"creation_type",{"type":53,"value":121},{"type":47,"tag":70,"props":163,"children":165},{"className":164},[],[166],{"type":53,"value":167},"GIT",{"type":47,"tag":111,"props":169,"children":170},{},[171,177,178],{"type":47,"tag":70,"props":172,"children":174},{"className":173},[],[175],{"type":53,"value":176},"scope",{"type":53,"value":121},{"type":47,"tag":70,"props":179,"children":181},{"className":180},[],[182],{"type":53,"value":183},"organization",{"type":47,"tag":111,"props":185,"children":186},{},[187,193,194],{"type":47,"tag":70,"props":188,"children":190},{"className":189},[],[191],{"type":53,"value":192},"hidden_in_user_interface",{"type":53,"value":121},{"type":47,"tag":70,"props":195,"children":197},{"className":196},[],[198],{"type":53,"value":199},"true",{"type":47,"tag":111,"props":201,"children":202},{},[203,209],{"type":47,"tag":70,"props":204,"children":206},{"className":205},[],[207],{"type":53,"value":208},"date_marker",{"type":53,"value":210},": the deploy time (UTC)",{"type":47,"tag":56,"props":212,"children":213},{},[214,216,222],{"type":53,"value":215},"They're returned newest-first; paginate with ",{"type":47,"tag":70,"props":217,"children":219},{"className":218},[],[220],{"type":53,"value":221},"offset",{"type":53,"value":223}," if you need to go further back.",{"type":47,"tag":79,"props":225,"children":227},{"id":226},"workflow",[228],{"type":53,"value":229},"Workflow",{"type":47,"tag":231,"props":232,"children":233},"ol",{},[234,268,350,515],{"type":47,"tag":111,"props":235,"children":236},{},[237,242,244,250,252,258,260,266],{"type":47,"tag":62,"props":238,"children":239},{},[240],{"type":53,"value":241},"Find the change's merge commit.",{"type":53,"value":243}," Identify the PR (e.g. ",{"type":47,"tag":70,"props":245,"children":247},{"className":246},[],[248],{"type":53,"value":249},"gh search prs --repo PostHog\u002Fposthog --author \u003Cuser> \"\u003Ckeywords>\"",{"type":53,"value":251},"), then ",{"type":47,"tag":70,"props":253,"children":255},{"className":254},[],[256],{"type":53,"value":257},"gh pr view \u003Cn> --repo PostHog\u002Fposthog --json number,title,mergedAt,mergeCommit,state",{"type":53,"value":259},". Note the merge commit SHA and ",{"type":47,"tag":70,"props":261,"children":263},{"className":262},[],[264],{"type":53,"value":265},"mergedAt",{"type":53,"value":267},".",{"type":47,"tag":111,"props":269,"children":270},{},[271,276,278,283,285,290,292,297,299,305,307,313,315,320,322,327,329,334,336,341,343,348],{"type":47,"tag":62,"props":272,"children":273},{},[274],{"type":53,"value":275},"List the target environment's deploys around the merge, oldest-first.",{"type":53,"value":277}," Match the region the user asked about (",{"type":47,"tag":70,"props":279,"children":281},{"className":280},[],[282],{"type":53,"value":135},{"type":53,"value":284}," for \"the US\", ",{"type":47,"tag":70,"props":286,"children":288},{"className":287},[],[289],{"type":53,"value":143},{"type":53,"value":291}," for \"the EU\"). The annotations come back ",{"type":47,"tag":62,"props":293,"children":294},{},[295],{"type":53,"value":296},"newest-first",{"type":53,"value":298},", so don't just take the first ",{"type":47,"tag":70,"props":300,"children":302},{"className":301},[],[303],{"type":53,"value":304},"... to \u003Cenv>",{"type":53,"value":306}," match on page 1 — that's the ",{"type":47,"tag":308,"props":309,"children":310},"em",{},[311],{"type":53,"value":312},"most recent",{"type":53,"value":314}," deploy. Paginate (with ",{"type":47,"tag":70,"props":316,"children":318},{"className":317},[],[319],{"type":53,"value":221},{"type":53,"value":321},") until you reach markers around ",{"type":47,"tag":70,"props":323,"children":325},{"className":324},[],[326],{"type":53,"value":265},{"type":53,"value":328},", then consider that environment's deploys in chronological order, starting with the first whose ",{"type":47,"tag":70,"props":330,"children":332},{"className":331},[],[333],{"type":53,"value":208},{"type":53,"value":335}," is ",{"type":47,"tag":308,"props":337,"children":338},{},[339],{"type":53,"value":340},"after",{"type":53,"value":342}," ",{"type":47,"tag":70,"props":344,"children":346},{"className":345},[],[347],{"type":53,"value":265},{"type":53,"value":349},". Check them earliest-first in step 3.",{"type":47,"tag":111,"props":351,"children":352},{},[353,358,360,365,367,465,469,475,477,483,484,490,492,498,500,506,508,513],{"type":47,"tag":62,"props":354,"children":355},{},[356],{"type":53,"value":357},"Confirm the deployed commit actually contains the merge commit.",{"type":53,"value":359}," A later ",{"type":47,"tag":70,"props":361,"children":363},{"className":362},[],[364],{"type":53,"value":208},{"type":53,"value":366}," is necessary but not sufficient — a deploy can fire just after the merge yet build a slightly older commit. Verify ancestry:",{"type":47,"tag":368,"props":369,"children":374},"pre",{"className":370,"code":371,"language":372,"meta":373,"style":373},"language-sh shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","gh api repos\u002FPostHog\u002Fposthog\u002Fcompare\u002F\u003Cmerge_sha>...\u003Cdeployed_sha> --jq '{status,ahead_by,behind_by}'\n","sh","",[375],{"type":47,"tag":70,"props":376,"children":377},{"__ignoreMap":373},[378],{"type":47,"tag":379,"props":380,"children":383},"span",{"class":381,"line":382},"line",1,[384,390,396,401,407,412,418,423,428,432,437,441,445,450,455,460],{"type":47,"tag":379,"props":385,"children":387},{"style":386},"--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B",[388],{"type":53,"value":389},"gh",{"type":47,"tag":379,"props":391,"children":393},{"style":392},"--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D",[394],{"type":53,"value":395}," api",{"type":47,"tag":379,"props":397,"children":398},{"style":392},[399],{"type":53,"value":400}," repos\u002FPostHog\u002Fposthog\u002Fcompare\u002F",{"type":47,"tag":379,"props":402,"children":404},{"style":403},"--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF",[405],{"type":53,"value":406},"\u003C",{"type":47,"tag":379,"props":408,"children":409},{"style":392},[410],{"type":53,"value":411},"merge_sh",{"type":47,"tag":379,"props":413,"children":415},{"style":414},"--shiki-light:#90A4AE;--shiki-default:#EEFFFF;--shiki-dark:#BABED8",[416],{"type":53,"value":417},"a",{"type":47,"tag":379,"props":419,"children":420},{"style":403},[421],{"type":53,"value":422},">",{"type":47,"tag":379,"props":424,"children":425},{"style":392},[426],{"type":53,"value":427},"...",{"type":47,"tag":379,"props":429,"children":430},{"style":403},[431],{"type":53,"value":406},{"type":47,"tag":379,"props":433,"children":434},{"style":392},[435],{"type":53,"value":436},"deployed_sh",{"type":47,"tag":379,"props":438,"children":439},{"style":414},[440],{"type":53,"value":417},{"type":47,"tag":379,"props":442,"children":443},{"style":403},[444],{"type":53,"value":422},{"type":47,"tag":379,"props":446,"children":447},{"style":392},[448],{"type":53,"value":449}," --jq",{"type":47,"tag":379,"props":451,"children":452},{"style":403},[453],{"type":53,"value":454}," '",{"type":47,"tag":379,"props":456,"children":457},{"style":392},[458],{"type":53,"value":459},"{status,ahead_by,behind_by}",{"type":47,"tag":379,"props":461,"children":462},{"style":403},[463],{"type":53,"value":464},"'\n",{"type":47,"tag":466,"props":467,"children":468},"br",{},[],{"type":47,"tag":70,"props":470,"children":472},{"className":471},[],[473],{"type":53,"value":474},"behind_by: 0",{"type":53,"value":476}," with ",{"type":47,"tag":70,"props":478,"children":480},{"className":479},[],[481],{"type":53,"value":482},"status",{"type":53,"value":342},{"type":47,"tag":70,"props":485,"children":487},{"className":486},[],[488],{"type":53,"value":489},"ahead",{"type":53,"value":491}," or ",{"type":47,"tag":70,"props":493,"children":495},{"className":494},[],[496],{"type":53,"value":497},"identical",{"type":53,"value":499}," means the deployed commit includes the merge — that's your answer. If ",{"type":47,"tag":70,"props":501,"children":503},{"className":502},[],[504],{"type":53,"value":505},"behind_by > 0",{"type":53,"value":507},", this deploy predates the change; move to the ",{"type":47,"tag":62,"props":509,"children":510},{},[511],{"type":53,"value":512},"next newer",{"type":53,"value":514}," deploy of that environment (the next one chronologically) and re-check. The first deploy that passes is the one that shipped the change.",{"type":47,"tag":111,"props":516,"children":517},{},[518,523,525,530,532,537],{"type":47,"tag":62,"props":519,"children":520},{},[521],{"type":53,"value":522},"Report",{"type":53,"value":524}," the deploy time (and PR\u002Fcommit) for the region asked about. Mention other regions if relevant — ",{"type":47,"tag":70,"props":526,"children":528},{"className":527},[],[529],{"type":53,"value":135},{"type":53,"value":531}," and ",{"type":47,"tag":70,"props":533,"children":535},{"className":534},[],[536],{"type":53,"value":143},{"type":53,"value":538}," usually deploy minutes apart but not simultaneously.",{"type":47,"tag":79,"props":540,"children":542},{"id":541},"notes",[543],{"type":53,"value":544},"Notes",{"type":47,"tag":107,"props":546,"children":547},{},[548,574],{"type":47,"tag":111,"props":549,"children":550},{},[551,553,558,560,565,567,572],{"type":53,"value":552},"\"Live in the US\" = ",{"type":47,"tag":70,"props":554,"children":556},{"className":555},[],[557],{"type":53,"value":135},{"type":53,"value":559},"; \"the EU\" = ",{"type":47,"tag":70,"props":561,"children":563},{"className":562},[],[564],{"type":53,"value":143},{"type":53,"value":566},". ",{"type":47,"tag":70,"props":568,"children":570},{"className":569},[],[571],{"type":53,"value":151},{"type":53,"value":573}," is the internal staging environment, not customer-facing.",{"type":47,"tag":111,"props":575,"children":576},{},[577,579,584,586,591],{"type":53,"value":578},"For a ",{"type":47,"tag":62,"props":580,"children":581},{},[582],{"type":53,"value":583},"query-runner \u002F read-path",{"type":53,"value":585}," change, the new behaviour applies retroactively to all data once deployed — so you can't time it from event volume, only from the deploy annotation. For a ",{"type":47,"tag":62,"props":587,"children":588},{},[589],{"type":53,"value":590},"capture",{"type":53,"value":592}," change, event volume for the new property is a secondary cross-check, but the annotation is still the authoritative deploy time.",{"type":47,"tag":594,"props":595,"children":596},"style",{},[597],{"type":53,"value":598},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"items":600,"total":708},[601,618,636,653,668,682,690],{"slug":602,"name":602,"fn":603,"description":604,"org":605,"tags":606,"stars":26,"repoUrl":27,"updatedAt":617},"analyzing-experiment-session-replays","analyze session replays for PostHog experiments","Analyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with different experiment variants, identify usability issues, compare behavior patterns between control and test groups, or get qualitative insights to complement quantitative experiment results.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[607,610,613,614],{"name":608,"slug":609,"type":15},"Analytics","analytics",{"name":611,"slug":612,"type":15},"Design","design",{"name":9,"slug":8,"type":15},{"name":615,"slug":616,"type":15},"User Research","user-research","2026-04-06T18:44:38.291781",{"slug":619,"name":619,"fn":620,"description":621,"org":622,"tags":623,"stars":26,"repoUrl":27,"updatedAt":635},"assessing-heatmaps","analyze page heatmaps and suggest improvements","Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click \u002F rageclick \u002F scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements.\nTRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap\u002Fclick data, or to 'analyze\u002Fassess\u002Freview the heatmap' for a URL.\nDO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[624,625,628,629,632],{"name":608,"slug":609,"type":15},{"name":626,"slug":627,"type":15},"Frontend","frontend",{"name":9,"slug":8,"type":15},{"name":630,"slug":631,"type":15},"Product Management","product-management",{"name":633,"slug":634,"type":15},"UX Design","ux-design","2026-06-05T07:40:43.37798",{"slug":637,"name":637,"fn":638,"description":639,"org":640,"tags":641,"stars":26,"repoUrl":27,"updatedAt":652},"auditing-experiments-flags","audit PostHog experiments and feature flags","Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[642,645,648,649],{"name":643,"slug":644,"type":15},"Audit","audit",{"name":646,"slug":647,"type":15},"Feature Flags","feature-flags",{"name":9,"slug":8,"type":15},{"name":650,"slug":651,"type":15},"QA","qa","2026-04-06T18:44:30.657553",{"slug":654,"name":654,"fn":655,"description":656,"org":657,"tags":658,"stars":26,"repoUrl":27,"updatedAt":667},"authoring-scouts","author and edit PostHog Signals scouts","How to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak a scout's schedule or dry-run posture, or write a brand-new scout from scratch for a specific use case (a custom event, a product surface no canonical scout covers), or steer a scout without editing it at all by leaving it a note. Covers the scout SKILL.md anatomy, the report contract, the dedupe + scratchpad-memory conventions, the scout-notes steering channel, the per-team skills-store path vs the canonical in-repo path, and the write-and-inspect test loop (with dry-run as an optional safety net). Trigger on \"write\u002Fedit\u002Fcustomize a signals scout\", \"new scout for X\", \"tune my scout schedule\", \"make a scout that watches \u003Cevent>\", \"leave a note for \u002F give feedback to a scout\", \"tell the scouts about X\".\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[659,662,665,666],{"name":660,"slug":661,"type":15},"Agents","agents",{"name":663,"slug":664,"type":15},"Automation","automation",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-07-28T05:33:45.509154",{"slug":669,"name":669,"fn":670,"description":671,"org":672,"tags":673,"stars":26,"repoUrl":27,"updatedAt":681},"building-a-dashboard","build and update PostHog dashboards","Build a new dashboard, or update an existing one, from a set of insights — the same job the in-app assistant does with its upsert-dashboard tool, but over MCP. Use when a user asks to create a dashboard, put several metrics\u002Fcharts together on one page, assemble a dashboard for a topic (product analytics, retention, revenue, activation, etc.), or add\u002Fremove\u002Freplace insights on a dashboard they already have. Covers deciding create vs update, reusing existing insights vs creating new ones, and using PostHog's vetted dashboard templates as reference for what a strong dashboard on a topic looks like.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[674,675,678],{"name":608,"slug":609,"type":15},{"name":676,"slug":677,"type":15},"Dashboards","dashboards",{"name":679,"slug":680,"type":15},"MCP","mcp","2026-07-21T06:07:38.060598",{"slug":4,"name":4,"fn":5,"description":6,"org":683,"tags":684,"stars":26,"repoUrl":27,"updatedAt":28},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[685,686,687,688,689],{"name":24,"slug":25,"type":15},{"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":691,"name":691,"fn":692,"description":693,"org":694,"tags":695,"stars":26,"repoUrl":27,"updatedAt":707},"choosing-trend-or-slope-view","visualize trends and growth over time","Clarify how to visualize change over a time range before building a trend. Use whenever the user asks how much something changed, grew, dropped, improved, or regressed between two points or periods — \"how much did X change from A to B\", \"before vs after\", \"start vs end\", \"week over week\", \"compare this month to last\", \"change over time\" — or mentions a \"slope chart\" \u002F \"slopegraph\". Two readings of \"change\" need different charts: the whole trend (a line, every interval) versus just the two endpoints (a slope, start vs end). Ask which they want, then render it. Not for choosing a saved insight ChartDisplayType in the insight editor.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[696,697,700,703,704],{"name":608,"slug":609,"type":15},{"name":698,"slug":699,"type":15},"Charts","charts",{"name":701,"slug":702,"type":15},"Data Visualization","data-visualization",{"name":9,"slug":8,"type":15},{"name":705,"slug":706,"type":15},"Reporting","reporting","2026-06-18T08:18:57.960157",56,{"items":710,"total":869},[711,726,736,749,762,777,793,806,818,833,843,859],{"slug":712,"name":712,"fn":713,"description":714,"org":715,"tags":716,"stars":723,"repoUrl":724,"updatedAt":725},"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},[717,718,721,722],{"name":608,"slug":609,"type":15},{"name":719,"slug":720,"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-07-28T05:34:11.117757",{"slug":727,"name":727,"fn":728,"description":729,"org":730,"tags":731,"stars":723,"repoUrl":724,"updatedAt":735},"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},[732,733,734],{"name":608,"slug":609,"type":15},{"name":643,"slug":644,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:33.693989",{"slug":737,"name":737,"fn":738,"description":739,"org":740,"tags":741,"stars":723,"repoUrl":724,"updatedAt":748},"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},[742,743,746,747],{"name":643,"slug":644,"type":15},{"name":744,"slug":745,"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":750,"name":750,"fn":751,"description":752,"org":753,"tags":754,"stars":723,"repoUrl":724,"updatedAt":761},"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},[755,756,757,760],{"name":643,"slug":644,"type":15},{"name":744,"slug":745,"type":15},{"name":758,"slug":759,"type":15},"Performance","performance",{"name":9,"slug":8,"type":15},"2026-06-18T08:25:10.936787",{"slug":763,"name":763,"fn":764,"description":765,"org":766,"tags":767,"stars":723,"repoUrl":724,"updatedAt":776},"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},[768,771,774,775],{"name":769,"slug":770,"type":15},"Alerting","alerting",{"name":772,"slug":773,"type":15},"Debugging","debugging",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:24:40.318583",{"slug":778,"name":778,"fn":779,"description":780,"org":781,"tags":782,"stars":723,"repoUrl":724,"updatedAt":792},"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},[783,784,787,788,791],{"name":608,"slug":609,"type":15},{"name":785,"slug":786,"type":15},"Monitoring","monitoring",{"name":13,"slug":14,"type":15},{"name":789,"slug":790,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-07-18T05:10:54.430898",{"slug":794,"name":794,"fn":795,"description":796,"org":797,"tags":798,"stars":723,"repoUrl":724,"updatedAt":805},"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},[799,800,801,802],{"name":663,"slug":664,"type":15},{"name":679,"slug":680,"type":15},{"name":9,"slug":8,"type":15},{"name":803,"slug":804,"type":15},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",{"slug":807,"name":807,"fn":808,"description":809,"org":810,"tags":811,"stars":723,"repoUrl":724,"updatedAt":817},"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},[812,813,814,815,816],{"name":608,"slug":609,"type":15},{"name":772,"slug":773,"type":15},{"name":626,"slug":627,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-05-07T05:56:19.828048",{"slug":819,"name":819,"fn":820,"description":821,"org":822,"tags":823,"stars":723,"repoUrl":724,"updatedAt":832},"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},[824,827,828,829],{"name":825,"slug":826,"type":15},"API Development","api-development",{"name":626,"slug":627,"type":15},{"name":9,"slug":8,"type":15},{"name":830,"slug":831,"type":15},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":834,"name":834,"fn":835,"description":836,"org":837,"tags":838,"stars":723,"repoUrl":724,"updatedAt":842},"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},[839,840,841],{"name":825,"slug":826,"type":15},{"name":789,"slug":790,"type":15},{"name":9,"slug":8,"type":15},"2026-07-15T05:29:58.442727",{"slug":844,"name":844,"fn":845,"description":846,"org":847,"tags":848,"stars":723,"repoUrl":724,"updatedAt":858},"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},[849,850,853,854,855],{"name":663,"slug":664,"type":15},{"name":851,"slug":852,"type":15},"Email","email",{"name":9,"slug":8,"type":15},{"name":705,"slug":706,"type":15},{"name":856,"slug":857,"type":15},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":860,"name":860,"fn":861,"description":862,"org":863,"tags":864,"stars":723,"repoUrl":724,"updatedAt":868},"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},[865,866,867],{"name":608,"slug":609,"type":15},{"name":825,"slug":826,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:29.624498",231]