[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-copying-flags-across-projects":3,"mdc--x4xwis-key":31,"related-repo-posthog-copying-flags-across-projects":842,"related-org-posthog-copying-flags-across-projects":949},{"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":26,"sourceUrl":29,"mdContent":30},"copying-flags-across-projects","copy feature flags across PostHog projects","Copy a feature flag from one PostHog project to one or more target projects in the same organization. Use when the user wants to duplicate a flag, promote a flag from staging to production, sync flags across projects, or replicate a flag configuration in a different workspace. Covers cohort remapping, scheduled-change handling, encrypted payloads, and the safe defaults (disabled in target, no scheduled changes).",{"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},"Feature Flags","feature-flags",{"name":18,"slug":19,"type":13},"Deployment","deployment",56,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills","2026-05-04T05:56:44.484909",null,4,[],{"repoUrl":21,"stars":20,"forks":24,"topics":27,"description":28},[],"PostHog skills (under construction)","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002Fomnibus\u002Fcopying-flags-across-projects","---\nname: copying-flags-across-projects\ndescription: 'Copy a feature flag from one PostHog project to one or more target projects in the same organization. Use when the user wants to duplicate a flag, promote a flag from staging to production, sync flags across projects, or replicate a flag configuration in a different workspace. Covers cohort remapping, scheduled-change handling, encrypted payloads, and the safe defaults (disabled in target, no scheduled changes).'\n---\n\n# Copying feature flags across projects\n\nThis skill guides you through duplicating a feature flag from a source project into one or more target projects within the same PostHog organization.\n\n## When to use this skill\n\n- The user asks to \"copy a flag to another project\", \"duplicate this flag\", or \"sync a flag between projects\"\n- The user wants to promote a flag from a staging project to a production project (or vice versa)\n- The user wants to replicate a flag configuration in a different workspace and keep cohort dependencies intact\n- The user is working around the absence of true environments by using projects-as-environments\n\n## What this skill does not cover\n\n- **Cross-organization copy** is not supported. The endpoint requires source and target projects to belong to the same org.\n- **Bulk copying every flag in a project**. The tool copies one flag at a time. For batch copies, loop through flag keys; each call is independent.\n- **Cleaning up old or stale flags** — see the `cleaning-up-stale-feature-flags` skill instead.\n\n## Workflow\n\n### 1. Resolve the source flag\n\nYou need the flag's **key** and the **source project's id**.\n\n- If the user gave a flag key and a project id, use them directly.\n- If the user gave a flag name (e.g. \"the new pricing flag\"), call `posthog:feature-flag-get-all` in the source project to find the matching flag and read its `key`.\n- If the user only gave a flag and not a project, ask which project it lives in. Don't assume the active MCP project — copying out of the wrong source is a common foot-gun.\n\n### 2. Resolve target project ids\n\nTargets must be in the same organization as the source. Call `posthog:projects-get` to list available projects and confirm membership before issuing the copy.\n\nFor a multi-target copy, the tool accepts up to 50 target project ids in a single call. Successes and failures are reported per target, so a partial failure does not block the rest.\n\n### 3. Preview the source flag\n\nCall `posthog:feature-flag-get-definition` on the source flag and present a concise summary to the user before copying:\n\n- Flag key, name, and active state in the source\n- Filter groups (rollout %, property filters, variant splits)\n- Any cohort references in `filters.groups[].properties[]` — these will be remapped server-side, but the user should know whether the target project already has matching cohorts\n- Whether the flag has encrypted payloads (`has_encrypted_payloads`) or is remote configuration (`is_remote_configuration`)\n- Whether scheduled changes exist (the user can opt to copy them in step 4)\n\n### 4. Confirm copy options\n\nDefault to the safest combination and ask the user to override only if they explicitly want different behavior:\n\n- **`disable_copied_flag: true`** — the copied flag lands disabled in the target. Recommended by default; turning a flag on in a new project should be a deliberate, observed action.\n- **`copy_schedule: false`** — scheduled changes do not come along. Recommended by default; schedules are usually project-specific.\n\nIf the user says \"promote it as-is\" or \"turn it on in prod\", switch `disable_copied_flag` to `false`. If they say \"include the rollout schedule\" or \"with the scheduled rollout\", switch `copy_schedule` to `true`.\n\n### 5. Execute the copy\n\nCall `posthog:feature-flags-copy-flags-create` with:\n\n- `feature_flag_key`: the source flag's key\n- `from_project`: the source project id\n- `target_project_ids`: the resolved list of target project ids\n- `disable_copied_flag`: from step 4 (default `true`)\n- `copy_schedule`: from step 4 (default `false`)\n\n### 6. Report per-target outcome\n\nThe response includes a `success` array (one entry per copied flag) and a `failed` array (per-target errors). Surface both:\n\n- For each success: target project id, the new flag's id, and its `active` state in the target.\n- For each failure: target project id and the error message. Common causes are missing editor access on the target team, or the flag already existing as a non-overridable resource in the target.\n\nIf any targets failed, ask the user whether to retry the failed ones, skip them, or fix the underlying issue (e.g. grant access, then retry).\n\n## Important notes\n\n- **Cohorts are remapped automatically.** When the source flag references a cohort, the endpoint creates or reuses an equivalent cohort in each target project and rewrites the flag's filters to point at the target-project cohort id. You don't need to handle this — but tell the user it's happening so they understand the new cohorts that may appear in the target.\n- **Encrypted payloads are preserved.** Remote-configuration flags with encrypted payloads keep their encryption when copied; the payload is re-encrypted under the target project's key.\n- **Scheduled changes copy with cohort remap too.** If `copy_schedule: true`, any scheduled cohort references are remapped just like the live filter conditions.\n- **Auth requirements.** The user's API key must include explicit `feature_flag:write` (or `feature_flag:*`) scope. A `*`-only key will be rejected — this endpoint is gated by an INTERNAL viewset and `*` consent does not satisfy it. Team-scoped keys cannot reach this endpoint either; an org-scoped or unscoped key is required.\n- **Editor access on the source.** The user must have at least editor-level access on the source flag's team. The endpoint enforces this via PostHog's access control before copying.\n- **Per-target access on targets.** Targets the user can't see are silently dropped from the result; targets they can see but lack edit rights on appear in the `failed` array with a permission error.\n- **No undo.** A copy creates a new flag in the target (or overwrites an existing flag with the same key). Always confirm with the user before issuing the copy, especially when the target is a production project.\n\n## Example interaction\n\n> **User:** Copy the `new-checkout` flag from project 12345 to project 67890.\n>\n> **Agent:** Looking at the source flag in project 12345.\n>\n> _(calls `posthog:feature-flag-get-definition`)_\n>\n> The `new-checkout` flag is currently a boolean at 25% rollout in project 12345, with no cohort filters and no scheduled changes. I'll copy it as **disabled** in project 67890 with no scheduled changes — this is the safer default. Confirm?\n>\n> **User:** Yes, but enable it in the target.\n>\n> **Agent:** Got it — enabling in the target.\n>\n> _(calls `posthog:feature-flags-copy-flags-create` with `disable_copied_flag: false`, `copy_schedule: false`)_\n>\n> Done. Created flag id 99887 in project 67890 (`active: true`). No failed targets.\n\n## Available tools\n\n- `posthog:feature-flags-copy-flags-create` — performs the copy. Required fields: `feature_flag_key`, `from_project`, `target_project_ids`. Optional: `disable_copied_flag`, `copy_schedule`.\n- `posthog:feature-flag-get-all` — find a flag by key\u002Fname in a given project when the user only gave a friendly name.\n- `posthog:feature-flag-get-definition` — fetch the full source flag (filters, variants, cohort references, encryption flags) so you can preview before copying.\n- `posthog:projects-get` — list projects in the active organization, used to resolve and validate target project ids.\n",{"data":32,"body":33},{"name":4,"description":6},{"type":34,"children":35},"root",[36,45,51,58,83,89,132,138,145,164,196,202,215,220,226,239,291,297,302,333,368,374,386,453,459,480,501,506,512,631,637,762,768],{"type":37,"tag":38,"props":39,"children":41},"element","h1",{"id":40},"copying-feature-flags-across-projects",[42],{"type":43,"value":44},"text","Copying feature flags across projects",{"type":37,"tag":46,"props":47,"children":48},"p",{},[49],{"type":43,"value":50},"This skill guides you through duplicating a feature flag from a source project into one or more target projects within the same PostHog organization.",{"type":37,"tag":52,"props":53,"children":55},"h2",{"id":54},"when-to-use-this-skill",[56],{"type":43,"value":57},"When to use this skill",{"type":37,"tag":59,"props":60,"children":61},"ul",{},[62,68,73,78],{"type":37,"tag":63,"props":64,"children":65},"li",{},[66],{"type":43,"value":67},"The user asks to \"copy a flag to another project\", \"duplicate this flag\", or \"sync a flag between projects\"",{"type":37,"tag":63,"props":69,"children":70},{},[71],{"type":43,"value":72},"The user wants to promote a flag from a staging project to a production project (or vice versa)",{"type":37,"tag":63,"props":74,"children":75},{},[76],{"type":43,"value":77},"The user wants to replicate a flag configuration in a different workspace and keep cohort dependencies intact",{"type":37,"tag":63,"props":79,"children":80},{},[81],{"type":43,"value":82},"The user is working around the absence of true environments by using projects-as-environments",{"type":37,"tag":52,"props":84,"children":86},{"id":85},"what-this-skill-does-not-cover",[87],{"type":43,"value":88},"What this skill does not cover",{"type":37,"tag":59,"props":90,"children":91},{},[92,103,113],{"type":37,"tag":63,"props":93,"children":94},{},[95,101],{"type":37,"tag":96,"props":97,"children":98},"strong",{},[99],{"type":43,"value":100},"Cross-organization copy",{"type":43,"value":102}," is not supported. The endpoint requires source and target projects to belong to the same org.",{"type":37,"tag":63,"props":104,"children":105},{},[106,111],{"type":37,"tag":96,"props":107,"children":108},{},[109],{"type":43,"value":110},"Bulk copying every flag in a project",{"type":43,"value":112},". The tool copies one flag at a time. For batch copies, loop through flag keys; each call is independent.",{"type":37,"tag":63,"props":114,"children":115},{},[116,121,123,130],{"type":37,"tag":96,"props":117,"children":118},{},[119],{"type":43,"value":120},"Cleaning up old or stale flags",{"type":43,"value":122}," — see the ",{"type":37,"tag":124,"props":125,"children":127},"code",{"className":126},[],[128],{"type":43,"value":129},"cleaning-up-stale-feature-flags",{"type":43,"value":131}," skill instead.",{"type":37,"tag":52,"props":133,"children":135},{"id":134},"workflow",[136],{"type":43,"value":137},"Workflow",{"type":37,"tag":139,"props":140,"children":142},"h3",{"id":141},"_1-resolve-the-source-flag",[143],{"type":43,"value":144},"1. Resolve the source flag",{"type":37,"tag":46,"props":146,"children":147},{},[148,150,155,157,162],{"type":43,"value":149},"You need the flag's ",{"type":37,"tag":96,"props":151,"children":152},{},[153],{"type":43,"value":154},"key",{"type":43,"value":156}," and the ",{"type":37,"tag":96,"props":158,"children":159},{},[160],{"type":43,"value":161},"source project's id",{"type":43,"value":163},".",{"type":37,"tag":59,"props":165,"children":166},{},[167,172,191],{"type":37,"tag":63,"props":168,"children":169},{},[170],{"type":43,"value":171},"If the user gave a flag key and a project id, use them directly.",{"type":37,"tag":63,"props":173,"children":174},{},[175,177,183,185,190],{"type":43,"value":176},"If the user gave a flag name (e.g. \"the new pricing flag\"), call ",{"type":37,"tag":124,"props":178,"children":180},{"className":179},[],[181],{"type":43,"value":182},"posthog:feature-flag-get-all",{"type":43,"value":184}," in the source project to find the matching flag and read its ",{"type":37,"tag":124,"props":186,"children":188},{"className":187},[],[189],{"type":43,"value":154},{"type":43,"value":163},{"type":37,"tag":63,"props":192,"children":193},{},[194],{"type":43,"value":195},"If the user only gave a flag and not a project, ask which project it lives in. Don't assume the active MCP project — copying out of the wrong source is a common foot-gun.",{"type":37,"tag":139,"props":197,"children":199},{"id":198},"_2-resolve-target-project-ids",[200],{"type":43,"value":201},"2. Resolve target project ids",{"type":37,"tag":46,"props":203,"children":204},{},[205,207,213],{"type":43,"value":206},"Targets must be in the same organization as the source. Call ",{"type":37,"tag":124,"props":208,"children":210},{"className":209},[],[211],{"type":43,"value":212},"posthog:projects-get",{"type":43,"value":214}," to list available projects and confirm membership before issuing the copy.",{"type":37,"tag":46,"props":216,"children":217},{},[218],{"type":43,"value":219},"For a multi-target copy, the tool accepts up to 50 target project ids in a single call. Successes and failures are reported per target, so a partial failure does not block the rest.",{"type":37,"tag":139,"props":221,"children":223},{"id":222},"_3-preview-the-source-flag",[224],{"type":43,"value":225},"3. Preview the source flag",{"type":37,"tag":46,"props":227,"children":228},{},[229,231,237],{"type":43,"value":230},"Call ",{"type":37,"tag":124,"props":232,"children":234},{"className":233},[],[235],{"type":43,"value":236},"posthog:feature-flag-get-definition",{"type":43,"value":238}," on the source flag and present a concise summary to the user before copying:",{"type":37,"tag":59,"props":240,"children":241},{},[242,247,252,265,286],{"type":37,"tag":63,"props":243,"children":244},{},[245],{"type":43,"value":246},"Flag key, name, and active state in the source",{"type":37,"tag":63,"props":248,"children":249},{},[250],{"type":43,"value":251},"Filter groups (rollout %, property filters, variant splits)",{"type":37,"tag":63,"props":253,"children":254},{},[255,257,263],{"type":43,"value":256},"Any cohort references in ",{"type":37,"tag":124,"props":258,"children":260},{"className":259},[],[261],{"type":43,"value":262},"filters.groups[].properties[]",{"type":43,"value":264}," — these will be remapped server-side, but the user should know whether the target project already has matching cohorts",{"type":37,"tag":63,"props":266,"children":267},{},[268,270,276,278,284],{"type":43,"value":269},"Whether the flag has encrypted payloads (",{"type":37,"tag":124,"props":271,"children":273},{"className":272},[],[274],{"type":43,"value":275},"has_encrypted_payloads",{"type":43,"value":277},") or is remote configuration (",{"type":37,"tag":124,"props":279,"children":281},{"className":280},[],[282],{"type":43,"value":283},"is_remote_configuration",{"type":43,"value":285},")",{"type":37,"tag":63,"props":287,"children":288},{},[289],{"type":43,"value":290},"Whether scheduled changes exist (the user can opt to copy them in step 4)",{"type":37,"tag":139,"props":292,"children":294},{"id":293},"_4-confirm-copy-options",[295],{"type":43,"value":296},"4. Confirm copy options",{"type":37,"tag":46,"props":298,"children":299},{},[300],{"type":43,"value":301},"Default to the safest combination and ask the user to override only if they explicitly want different behavior:",{"type":37,"tag":59,"props":303,"children":304},{},[305,319],{"type":37,"tag":63,"props":306,"children":307},{},[308,317],{"type":37,"tag":96,"props":309,"children":310},{},[311],{"type":37,"tag":124,"props":312,"children":314},{"className":313},[],[315],{"type":43,"value":316},"disable_copied_flag: true",{"type":43,"value":318}," — the copied flag lands disabled in the target. Recommended by default; turning a flag on in a new project should be a deliberate, observed action.",{"type":37,"tag":63,"props":320,"children":321},{},[322,331],{"type":37,"tag":96,"props":323,"children":324},{},[325],{"type":37,"tag":124,"props":326,"children":328},{"className":327},[],[329],{"type":43,"value":330},"copy_schedule: false",{"type":43,"value":332}," — scheduled changes do not come along. Recommended by default; schedules are usually project-specific.",{"type":37,"tag":46,"props":334,"children":335},{},[336,338,344,346,352,354,360,361,367],{"type":43,"value":337},"If the user says \"promote it as-is\" or \"turn it on in prod\", switch ",{"type":37,"tag":124,"props":339,"children":341},{"className":340},[],[342],{"type":43,"value":343},"disable_copied_flag",{"type":43,"value":345}," to ",{"type":37,"tag":124,"props":347,"children":349},{"className":348},[],[350],{"type":43,"value":351},"false",{"type":43,"value":353},". If they say \"include the rollout schedule\" or \"with the scheduled rollout\", switch ",{"type":37,"tag":124,"props":355,"children":357},{"className":356},[],[358],{"type":43,"value":359},"copy_schedule",{"type":43,"value":345},{"type":37,"tag":124,"props":362,"children":364},{"className":363},[],[365],{"type":43,"value":366},"true",{"type":43,"value":163},{"type":37,"tag":139,"props":369,"children":371},{"id":370},"_5-execute-the-copy",[372],{"type":43,"value":373},"5. Execute the copy",{"type":37,"tag":46,"props":375,"children":376},{},[377,378,384],{"type":43,"value":230},{"type":37,"tag":124,"props":379,"children":381},{"className":380},[],[382],{"type":43,"value":383},"posthog:feature-flags-copy-flags-create",{"type":43,"value":385}," with:",{"type":37,"tag":59,"props":387,"children":388},{},[389,400,411,422,438],{"type":37,"tag":63,"props":390,"children":391},{},[392,398],{"type":37,"tag":124,"props":393,"children":395},{"className":394},[],[396],{"type":43,"value":397},"feature_flag_key",{"type":43,"value":399},": the source flag's key",{"type":37,"tag":63,"props":401,"children":402},{},[403,409],{"type":37,"tag":124,"props":404,"children":406},{"className":405},[],[407],{"type":43,"value":408},"from_project",{"type":43,"value":410},": the source project id",{"type":37,"tag":63,"props":412,"children":413},{},[414,420],{"type":37,"tag":124,"props":415,"children":417},{"className":416},[],[418],{"type":43,"value":419},"target_project_ids",{"type":43,"value":421},": the resolved list of target project ids",{"type":37,"tag":63,"props":423,"children":424},{},[425,430,432,437],{"type":37,"tag":124,"props":426,"children":428},{"className":427},[],[429],{"type":43,"value":343},{"type":43,"value":431},": from step 4 (default ",{"type":37,"tag":124,"props":433,"children":435},{"className":434},[],[436],{"type":43,"value":366},{"type":43,"value":285},{"type":37,"tag":63,"props":439,"children":440},{},[441,446,447,452],{"type":37,"tag":124,"props":442,"children":444},{"className":443},[],[445],{"type":43,"value":359},{"type":43,"value":431},{"type":37,"tag":124,"props":448,"children":450},{"className":449},[],[451],{"type":43,"value":351},{"type":43,"value":285},{"type":37,"tag":139,"props":454,"children":456},{"id":455},"_6-report-per-target-outcome",[457],{"type":43,"value":458},"6. Report per-target outcome",{"type":37,"tag":46,"props":460,"children":461},{},[462,464,470,472,478],{"type":43,"value":463},"The response includes a ",{"type":37,"tag":124,"props":465,"children":467},{"className":466},[],[468],{"type":43,"value":469},"success",{"type":43,"value":471}," array (one entry per copied flag) and a ",{"type":37,"tag":124,"props":473,"children":475},{"className":474},[],[476],{"type":43,"value":477},"failed",{"type":43,"value":479}," array (per-target errors). Surface both:",{"type":37,"tag":59,"props":481,"children":482},{},[483,496],{"type":37,"tag":63,"props":484,"children":485},{},[486,488,494],{"type":43,"value":487},"For each success: target project id, the new flag's id, and its ",{"type":37,"tag":124,"props":489,"children":491},{"className":490},[],[492],{"type":43,"value":493},"active",{"type":43,"value":495}," state in the target.",{"type":37,"tag":63,"props":497,"children":498},{},[499],{"type":43,"value":500},"For each failure: target project id and the error message. Common causes are missing editor access on the target team, or the flag already existing as a non-overridable resource in the target.",{"type":37,"tag":46,"props":502,"children":503},{},[504],{"type":43,"value":505},"If any targets failed, ask the user whether to retry the failed ones, skip them, or fix the underlying issue (e.g. grant access, then retry).",{"type":37,"tag":52,"props":507,"children":509},{"id":508},"important-notes",[510],{"type":43,"value":511},"Important notes",{"type":37,"tag":59,"props":513,"children":514},{},[515,525,535,553,594,604,621],{"type":37,"tag":63,"props":516,"children":517},{},[518,523],{"type":37,"tag":96,"props":519,"children":520},{},[521],{"type":43,"value":522},"Cohorts are remapped automatically.",{"type":43,"value":524}," When the source flag references a cohort, the endpoint creates or reuses an equivalent cohort in each target project and rewrites the flag's filters to point at the target-project cohort id. You don't need to handle this — but tell the user it's happening so they understand the new cohorts that may appear in the target.",{"type":37,"tag":63,"props":526,"children":527},{},[528,533],{"type":37,"tag":96,"props":529,"children":530},{},[531],{"type":43,"value":532},"Encrypted payloads are preserved.",{"type":43,"value":534}," Remote-configuration flags with encrypted payloads keep their encryption when copied; the payload is re-encrypted under the target project's key.",{"type":37,"tag":63,"props":536,"children":537},{},[538,543,545,551],{"type":37,"tag":96,"props":539,"children":540},{},[541],{"type":43,"value":542},"Scheduled changes copy with cohort remap too.",{"type":43,"value":544}," If ",{"type":37,"tag":124,"props":546,"children":548},{"className":547},[],[549],{"type":43,"value":550},"copy_schedule: true",{"type":43,"value":552},", any scheduled cohort references are remapped just like the live filter conditions.",{"type":37,"tag":63,"props":554,"children":555},{},[556,561,563,569,571,577,579,585,587,592],{"type":37,"tag":96,"props":557,"children":558},{},[559],{"type":43,"value":560},"Auth requirements.",{"type":43,"value":562}," The user's API key must include explicit ",{"type":37,"tag":124,"props":564,"children":566},{"className":565},[],[567],{"type":43,"value":568},"feature_flag:write",{"type":43,"value":570}," (or ",{"type":37,"tag":124,"props":572,"children":574},{"className":573},[],[575],{"type":43,"value":576},"feature_flag:*",{"type":43,"value":578},") scope. A ",{"type":37,"tag":124,"props":580,"children":582},{"className":581},[],[583],{"type":43,"value":584},"*",{"type":43,"value":586},"-only key will be rejected — this endpoint is gated by an INTERNAL viewset and ",{"type":37,"tag":124,"props":588,"children":590},{"className":589},[],[591],{"type":43,"value":584},{"type":43,"value":593}," consent does not satisfy it. Team-scoped keys cannot reach this endpoint either; an org-scoped or unscoped key is required.",{"type":37,"tag":63,"props":595,"children":596},{},[597,602],{"type":37,"tag":96,"props":598,"children":599},{},[600],{"type":43,"value":601},"Editor access on the source.",{"type":43,"value":603}," The user must have at least editor-level access on the source flag's team. The endpoint enforces this via PostHog's access control before copying.",{"type":37,"tag":63,"props":605,"children":606},{},[607,612,614,619],{"type":37,"tag":96,"props":608,"children":609},{},[610],{"type":43,"value":611},"Per-target access on targets.",{"type":43,"value":613}," Targets the user can't see are silently dropped from the result; targets they can see but lack edit rights on appear in the ",{"type":37,"tag":124,"props":615,"children":617},{"className":616},[],[618],{"type":43,"value":477},{"type":43,"value":620}," array with a permission error.",{"type":37,"tag":63,"props":622,"children":623},{},[624,629],{"type":37,"tag":96,"props":625,"children":626},{},[627],{"type":43,"value":628},"No undo.",{"type":43,"value":630}," A copy creates a new flag in the target (or overwrites an existing flag with the same key). Always confirm with the user before issuing the copy, especially when the target is a production project.",{"type":37,"tag":52,"props":632,"children":634},{"id":633},"example-interaction",[635],{"type":43,"value":636},"Example interaction",{"type":37,"tag":638,"props":639,"children":640},"blockquote",{},[641,659,669,684,703,712,721,749],{"type":37,"tag":46,"props":642,"children":643},{},[644,649,651,657],{"type":37,"tag":96,"props":645,"children":646},{},[647],{"type":43,"value":648},"User:",{"type":43,"value":650}," Copy the ",{"type":37,"tag":124,"props":652,"children":654},{"className":653},[],[655],{"type":43,"value":656},"new-checkout",{"type":43,"value":658}," flag from project 12345 to project 67890.",{"type":37,"tag":46,"props":660,"children":661},{},[662,667],{"type":37,"tag":96,"props":663,"children":664},{},[665],{"type":43,"value":666},"Agent:",{"type":43,"value":668}," Looking at the source flag in project 12345.",{"type":37,"tag":46,"props":670,"children":671},{},[672],{"type":37,"tag":673,"props":674,"children":675},"em",{},[676,678,683],{"type":43,"value":677},"(calls ",{"type":37,"tag":124,"props":679,"children":681},{"className":680},[],[682],{"type":43,"value":236},{"type":43,"value":285},{"type":37,"tag":46,"props":685,"children":686},{},[687,689,694,696,701],{"type":43,"value":688},"The ",{"type":37,"tag":124,"props":690,"children":692},{"className":691},[],[693],{"type":43,"value":656},{"type":43,"value":695}," flag is currently a boolean at 25% rollout in project 12345, with no cohort filters and no scheduled changes. I'll copy it as ",{"type":37,"tag":96,"props":697,"children":698},{},[699],{"type":43,"value":700},"disabled",{"type":43,"value":702}," in project 67890 with no scheduled changes — this is the safer default. Confirm?",{"type":37,"tag":46,"props":704,"children":705},{},[706,710],{"type":37,"tag":96,"props":707,"children":708},{},[709],{"type":43,"value":648},{"type":43,"value":711}," Yes, but enable it in the target.",{"type":37,"tag":46,"props":713,"children":714},{},[715,719],{"type":37,"tag":96,"props":716,"children":717},{},[718],{"type":43,"value":666},{"type":43,"value":720}," Got it — enabling in the target.",{"type":37,"tag":46,"props":722,"children":723},{},[724],{"type":37,"tag":673,"props":725,"children":726},{},[727,728,733,735,741,743,748],{"type":43,"value":677},{"type":37,"tag":124,"props":729,"children":731},{"className":730},[],[732],{"type":43,"value":383},{"type":43,"value":734}," with ",{"type":37,"tag":124,"props":736,"children":738},{"className":737},[],[739],{"type":43,"value":740},"disable_copied_flag: false",{"type":43,"value":742},", ",{"type":37,"tag":124,"props":744,"children":746},{"className":745},[],[747],{"type":43,"value":330},{"type":43,"value":285},{"type":37,"tag":46,"props":750,"children":751},{},[752,754,760],{"type":43,"value":753},"Done. Created flag id 99887 in project 67890 (",{"type":37,"tag":124,"props":755,"children":757},{"className":756},[],[758],{"type":43,"value":759},"active: true",{"type":43,"value":761},"). No failed targets.",{"type":37,"tag":52,"props":763,"children":765},{"id":764},"available-tools",[766],{"type":43,"value":767},"Available tools",{"type":37,"tag":59,"props":769,"children":770},{},[771,812,822,832],{"type":37,"tag":63,"props":772,"children":773},{},[774,779,781,786,787,792,793,798,800,805,806,811],{"type":37,"tag":124,"props":775,"children":777},{"className":776},[],[778],{"type":43,"value":383},{"type":43,"value":780}," — performs the copy. Required fields: ",{"type":37,"tag":124,"props":782,"children":784},{"className":783},[],[785],{"type":43,"value":397},{"type":43,"value":742},{"type":37,"tag":124,"props":788,"children":790},{"className":789},[],[791],{"type":43,"value":408},{"type":43,"value":742},{"type":37,"tag":124,"props":794,"children":796},{"className":795},[],[797],{"type":43,"value":419},{"type":43,"value":799},". Optional: ",{"type":37,"tag":124,"props":801,"children":803},{"className":802},[],[804],{"type":43,"value":343},{"type":43,"value":742},{"type":37,"tag":124,"props":807,"children":809},{"className":808},[],[810],{"type":43,"value":359},{"type":43,"value":163},{"type":37,"tag":63,"props":813,"children":814},{},[815,820],{"type":37,"tag":124,"props":816,"children":818},{"className":817},[],[819],{"type":43,"value":182},{"type":43,"value":821}," — find a flag by key\u002Fname in a given project when the user only gave a friendly name.",{"type":37,"tag":63,"props":823,"children":824},{},[825,830],{"type":37,"tag":124,"props":826,"children":828},{"className":827},[],[829],{"type":43,"value":236},{"type":43,"value":831}," — fetch the full source flag (filters, variants, cohort references, encryption flags) so you can preview before copying.",{"type":37,"tag":63,"props":833,"children":834},{},[835,840],{"type":37,"tag":124,"props":836,"children":838},{"className":837},[],[839],{"type":43,"value":212},{"type":43,"value":841}," — list projects in the active organization, used to resolve and validate target project ids.",{"items":843,"total":948},[844,861,881,887,907,921,932],{"slug":845,"name":845,"fn":846,"description":847,"org":848,"tags":849,"stars":20,"repoUrl":21,"updatedAt":860},"account-handover","draft sales account handover notes","Draft structured handover notes for transitioning a PostHog account from one TAM or CSM to another. Use this skill when a TAM needs to hand over an account, prepare a transition briefing, write handover notes, create an account summary for a new owner, or any request involving account transitions between TAMs or CSMs. Triggers on \"hand over this account\", \"transition account to\", \"draft handover notes\", \"account briefing for new TAM\", \"prepare account transition\", or when a TAM names an account and says they're leaving or reassigning it.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[850,853,856,857],{"name":851,"slug":852,"type":13},"Communications","communications",{"name":854,"slug":855,"type":13},"CRM","crm",{"name":9,"slug":8,"type":13},{"name":858,"slug":859,"type":13},"Sales","sales","2026-04-16T05:13:00.172732",{"slug":862,"name":862,"fn":863,"description":864,"org":865,"tags":866,"stars":20,"repoUrl":21,"updatedAt":880},"auditing-warehouse-data-health","audit PostHog data warehouse health","Audit the health of a PostHog project's data warehouse — find every broken or degraded pipeline item across sources, sync schemas, materialized views, batch exports, and transformations. Use when the user asks \"what's broken in my warehouse?\", \"give me a health check\", \"audit my data pipeline\", \"why are some dashboards stale?\", or wants a one-shot triage summary before deciding where to spend time. Produces a prioritized report of issues grouped by severity and type, with recommended next steps.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[867,870,873,876,879],{"name":868,"slug":869,"type":13},"Audit","audit",{"name":871,"slug":872,"type":13},"Data Engineering","data-engineering",{"name":874,"slug":875,"type":13},"Data Quality","data-quality",{"name":877,"slug":878,"type":13},"Observability","observability",{"name":9,"slug":8,"type":13},"2026-06-21T08:19:05.85849",{"slug":4,"name":4,"fn":5,"description":6,"org":882,"tags":883,"stars":20,"repoUrl":21,"updatedAt":22},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[884,885,886],{"name":18,"slug":19,"type":13},{"name":15,"slug":16,"type":13},{"name":9,"slug":8,"type":13},{"slug":888,"name":888,"fn":889,"description":890,"org":891,"tags":892,"stars":20,"repoUrl":21,"updatedAt":906},"diagnosing-experiment-results","diagnose PostHog experiment results and anomalies","Diagnoses bias, anomalies, and strange-looking results on a specific PostHog experiment. Covers empty \u002F 0-exposure experiments, sample ratio mismatch, identity fragmentation, multi-variant exposure, uneven-split exclusion bias, significance traps (peeking, A\u002FA, Bayesian vs Frequentist), PostHog-vs-SQL discrepancies, and surprises after mid-run edits. Symptom-driven dispatch to the right diagnostic.\nTRIGGER when: user asks 'is my experiment biased?' or 'why 0 exposures?', references the bias banner, says a variant looks strange \u002F wrong \u002F off, sees significance flipping, notices PostHog numbers disagreeing with their SQL, sees an A\u002FA test showing significance, or reports surprises after mid-run edits.\nDO NOT TRIGGER when: creating a new experiment (use creating-experiments), only configuring rollout (use configuring-experiment-rollout) or metrics (use configuring-experiment-analytics), or only asking lifecycle questions (use managing-experiment-lifecycle).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[893,896,899,902,905],{"name":894,"slug":895,"type":13},"A\u002FB Testing","a-b-testing",{"name":897,"slug":898,"type":13},"Analytics","analytics",{"name":900,"slug":901,"type":13},"Data Analysis","data-analysis",{"name":903,"slug":904,"type":13},"Debugging","debugging",{"name":9,"slug":8,"type":13},"2026-05-22T06:59:58.103867",{"slug":908,"name":908,"fn":909,"description":910,"org":911,"tags":912,"stars":20,"repoUrl":21,"updatedAt":920},"diagnosing-missing-recordings","diagnose missing PostHog session recordings","Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling, triggers, ad blockers, and quota\u002Fbilling scenarios.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[913,914,915,918,919],{"name":897,"slug":898,"type":13},{"name":903,"slug":904,"type":13},{"name":916,"slug":917,"type":13},"Frontend","frontend",{"name":877,"slug":878,"type":13},{"name":9,"slug":8,"type":13},"2026-04-22T05:06:51.989772",{"slug":922,"name":922,"fn":923,"description":924,"org":925,"tags":926,"stars":20,"repoUrl":21,"updatedAt":931},"diagnosing-sdk-health","diagnose PostHog SDK health","Diagnoses the health of a project's PostHog SDK integrations — which SDKs are out of date and how to fix them. Use when a user asks about PostHog SDK versions, outdated SDKs, upgrade recommendations, \"SDK health\", \"SDK doctor\" (the former name), or when events or features seem off and it might be due to an old SDK.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[927,928,929,930],{"name":897,"slug":898,"type":13},{"name":903,"slug":904,"type":13},{"name":877,"slug":878,"type":13},{"name":9,"slug":8,"type":13},"2026-04-27T05:46:14.554016",{"slug":933,"name":933,"fn":934,"description":935,"org":936,"tags":937,"stars":20,"repoUrl":21,"updatedAt":947},"error-tracking-android","track Android errors with PostHog","PostHog error tracking for Android",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[938,941,942,945,946],{"name":939,"slug":940,"type":13},"Android","android",{"name":903,"slug":904,"type":13},{"name":943,"slug":944,"type":13},"Mobile","mobile",{"name":877,"slug":878,"type":13},{"name":9,"slug":8,"type":13},"2026-04-06T18:46:26.982494",110,{"items":950,"total":1113},[951,966,976,989,1002,1015,1031,1048,1060,1075,1085,1103],{"slug":952,"name":952,"fn":953,"description":954,"org":955,"tags":956,"stars":963,"repoUrl":964,"updatedAt":965},"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},[957,958,961,962],{"name":897,"slug":898,"type":13},{"name":959,"slug":960,"type":13},"Cost Optimization","cost-optimization",{"name":877,"slug":878,"type":13},{"name":9,"slug":8,"type":13},35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-28T05:34:11.117757",{"slug":967,"name":967,"fn":968,"description":969,"org":970,"tags":971,"stars":963,"repoUrl":964,"updatedAt":975},"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},[972,973,974],{"name":897,"slug":898,"type":13},{"name":868,"slug":869,"type":13},{"name":9,"slug":8,"type":13},"2026-06-08T08:08:33.693989",{"slug":977,"name":977,"fn":978,"description":979,"org":980,"tags":981,"stars":963,"repoUrl":964,"updatedAt":988},"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},[982,983,986,987],{"name":868,"slug":869,"type":13},{"name":984,"slug":985,"type":13},"Data Warehouse","data-warehouse",{"name":877,"slug":878,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:22:57.67984",{"slug":990,"name":990,"fn":991,"description":992,"org":993,"tags":994,"stars":963,"repoUrl":964,"updatedAt":1001},"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},[995,996,997,1000],{"name":868,"slug":869,"type":13},{"name":984,"slug":985,"type":13},{"name":998,"slug":999,"type":13},"Performance","performance",{"name":9,"slug":8,"type":13},"2026-06-18T08:25:10.936787",{"slug":1003,"name":1003,"fn":1004,"description":1005,"org":1006,"tags":1007,"stars":963,"repoUrl":964,"updatedAt":1014},"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},[1008,1011,1012,1013],{"name":1009,"slug":1010,"type":13},"Alerting","alerting",{"name":903,"slug":904,"type":13},{"name":877,"slug":878,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:24:40.318583",{"slug":1016,"name":1016,"fn":1017,"description":1018,"org":1019,"tags":1020,"stars":963,"repoUrl":964,"updatedAt":1030},"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},[1021,1022,1025,1026,1029],{"name":897,"slug":898,"type":13},{"name":1023,"slug":1024,"type":13},"Monitoring","monitoring",{"name":877,"slug":878,"type":13},{"name":1027,"slug":1028,"type":13},"Operations","operations",{"name":9,"slug":8,"type":13},"2026-07-18T05:10:54.430898",{"slug":1032,"name":1032,"fn":1033,"description":1034,"org":1035,"tags":1036,"stars":963,"repoUrl":964,"updatedAt":1047},"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},[1037,1040,1043,1044],{"name":1038,"slug":1039,"type":13},"Automation","automation",{"name":1041,"slug":1042,"type":13},"MCP","mcp",{"name":9,"slug":8,"type":13},{"name":1045,"slug":1046,"type":13},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",{"slug":1049,"name":1049,"fn":1050,"description":1051,"org":1052,"tags":1053,"stars":963,"repoUrl":964,"updatedAt":1059},"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},[1054,1055,1056,1057,1058],{"name":897,"slug":898,"type":13},{"name":903,"slug":904,"type":13},{"name":916,"slug":917,"type":13},{"name":877,"slug":878,"type":13},{"name":9,"slug":8,"type":13},"2026-05-07T05:56:19.828048",{"slug":1061,"name":1061,"fn":1062,"description":1063,"org":1064,"tags":1065,"stars":963,"repoUrl":964,"updatedAt":1074},"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},[1066,1069,1070,1071],{"name":1067,"slug":1068,"type":13},"API Development","api-development",{"name":916,"slug":917,"type":13},{"name":9,"slug":8,"type":13},{"name":1072,"slug":1073,"type":13},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":1076,"name":1076,"fn":1077,"description":1078,"org":1079,"tags":1080,"stars":963,"repoUrl":964,"updatedAt":1084},"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},[1081,1082,1083],{"name":1067,"slug":1068,"type":13},{"name":1027,"slug":1028,"type":13},{"name":9,"slug":8,"type":13},"2026-07-15T05:29:58.442727",{"slug":1086,"name":1086,"fn":1087,"description":1088,"org":1089,"tags":1090,"stars":963,"repoUrl":964,"updatedAt":1102},"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},[1091,1092,1095,1096,1099],{"name":1038,"slug":1039,"type":13},{"name":1093,"slug":1094,"type":13},"Email","email",{"name":9,"slug":8,"type":13},{"name":1097,"slug":1098,"type":13},"Reporting","reporting",{"name":1100,"slug":1101,"type":13},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":1104,"name":1104,"fn":1105,"description":1106,"org":1107,"tags":1108,"stars":963,"repoUrl":964,"updatedAt":1112},"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},[1109,1110,1111],{"name":897,"slug":898,"type":13},{"name":1067,"slug":1068,"type":13},{"name":9,"slug":8,"type":13},"2026-06-08T08:08:29.624498",231]