[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-suggesting-data-imports":3,"mdc-gc6d2-key":37,"related-org-posthog-suggesting-data-imports":763,"related-repo-posthog-suggesting-data-imports":936},{"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":32,"sourceUrl":35,"mdContent":36},"suggesting-data-imports","suggest data imports for PostHog","Use when the user asks about revenue, payments, subscriptions, billing, CRM deals, support tickets, production database tables, or other data that PostHog does not collect natively. Also use when a query fails because a table does not exist or returns no results for expected external data. The data warehouse can import from SaaS tools (Stripe, Hubspot, etc.), production databases (Postgres, MySQL, BigQuery, Snowflake), and other arbitrary data sources. Covers checking existing sources, identifying the right source type, and guiding the setup.",{"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,20,23],{"name":9,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"Data Engineering","data-engineering",{"name":18,"slug":19,"type":13},"Integrations","integrations",{"name":21,"slug":22,"type":13},"ETL","etl",{"name":24,"slug":25,"type":13},"Analytics","analytics",56,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills","2026-04-27T05:46:16.872117",null,4,[],{"repoUrl":27,"stars":26,"forks":30,"topics":33,"description":34},[],"PostHog skills (under construction)","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002Fomnibus\u002Fsuggesting-data-imports","---\nname: suggesting-data-imports\ndescription: 'Use when the user asks about revenue, payments, subscriptions, billing, CRM deals, support tickets, production database tables, or other data that PostHog does not collect natively. Also use when a query fails because a table does not exist or returns no results for expected external data. The data warehouse can import from SaaS tools (Stripe, Hubspot, etc.), production databases (Postgres, MySQL, BigQuery, Snowflake), and other arbitrary data sources. Covers checking existing sources, identifying the right source type, and guiding the setup.'\n---\n\n# Suggesting data imports\n\nThis skill helps identify when data the user needs lives outside PostHog and guides them toward importing it via the data warehouse. The key insight is recognizing the gap — then connecting it to the right source type.\n\n## What PostHog collects natively\n\nPostHog collects product analytics events, persons, sessions, and groups via its SDKs. Additional products are available but must be enabled: session replay, feature flags, experiments, surveys, web analytics, error tracking, AI observability, conversations, logs, revenue analytics, workflows, CDP destinations, and batch exports. PostHog does **not** collect external business data like payments, subscriptions, CRM records, support tickets from other systems, or production database tables — that data must be imported via the data warehouse.\n\n## When to use this skill\n\n- A HogQL query fails because a table doesn't exist\n- The user asks about data from an external system (Stripe, Hubspot, Salesforce, etc.)\n- The user wants to correlate PostHog analytics with business data (revenue, support tickets, CRM records, etc)\n- The user asks \"how do I get my X data into PostHog?\"\n- Analysis requires joining PostHog events with external data\n- The user asks about exporting PostHog data for comparison elsewhere (in a google sheet, external warehouse, etc)\n\n## Workflow\n\n### 1. Understand what data is missing\n\nListen for signals that the user needs external data:\n\n- They mention a specific tool or system (Stripe, Hubspot, Zendesk, their production database, etc.)\n- A query references a table that doesn't exist in PostHog\n- They want to analyze something PostHog doesn't track natively (revenue, support tickets, CRM deals, etc.)\n\nIf a query failed, check the error — if it's \"table not found\" or similar, the data likely needs to be imported.\n\n### 2. Check what's already connected\n\nCall `posthog:external-data-sources-list` to see existing sources. The data might already be imported but the user doesn't know the table name or prefix.\n\nIf a source exists for the system they're asking about, call `posthog:external-data-schemas-list` to show the available tables. The data might be there but under a different name or prefix.\n\nAlso call `posthog:read-data-warehouse-schema` to see all queryable tables — the data might already be available as a view or joined table.\n\n### 3. Identify the right source type\n\nIf the data isn't imported yet, call `posthog:external-data-sources-wizard` to see available source types. Match the user's need to a source:\n\n**Common patterns:**\n\n| User wants                 | Source type                                    | Key tables                                  |\n| -------------------------- | ---------------------------------------------- | ------------------------------------------- |\n| Revenue \u002F payment data     | Stripe, Chargebee, Shopify                     | charges, subscriptions, invoices, customers |\n| CRM \u002F sales pipeline       | Hubspot, Salesforce, Attio                     | contacts, deals, companies                  |\n| Support tickets            | Zendesk                                        | tickets, users, organizations               |\n| Product data from their DB | Postgres, MySQL, BigQuery, Snowflake, Redshift | user's own tables                           |\n| Marketing \u002F ads            | Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads | campaigns, ad_groups, ads                   |\n| Email marketing            | Mailchimp, Klaviyo                             | campaigns, lists, subscribers               |\n| Project management         | Linear                                         | issues, projects                            |\n| Error tracking (external)  | Sentry                                         | issues, events                              |\n\n### 4. Suggest the import\n\nPresent the recommendation concisely:\n\n- What source type to connect\n- What tables would become available\n- How this enables the analysis they want\n\nExample: \"Your Stripe data isn't in PostHog yet. If you connect a Stripe source, you'll get tables like `charges`, `subscriptions`, and `customers` that you can join with PostHog events to analyze revenue by user behavior.\"\n\n### 5. Offer to set up the source\n\nIf the user wants to proceed, the fastest path is the one-step `data-warehouse-source-setup` tool (validate creds →\ndiscover tables → sync defaults → create, in one call), with `data-warehouse-source-connect-link` to collect\ncredentials securely in the browser rather than in chat. For anything beyond the happy path (hand-picking tables,\nnon-default sync types, webhooks, CDC), hand off to the **`setting-up-a-data-warehouse-source`** skill, which covers\nthe full flow, sync-type selection, webhook registration, and prefix guidance. Do not duplicate that workflow here.\n\n### 6. Show what's possible after import\n\nOnce connected, help the user write their first query joining PostHog data with the imported data. Use `posthog:execute-sql` to demonstrate.\n\nCommon join patterns:\n\n- Join Stripe customers with PostHog persons on email: `SELECT * FROM stripe_customers sc JOIN persons p ON sc.email = p.properties.$email`\n- Join CRM deals with events: correlate product usage with sales outcomes\n- Join support tickets with session recordings: find recordings for users who filed tickets\n\n## Important notes\n\n- **Don't guess table names.** Always check `posthog:read-data-warehouse-schema` and `posthog:external-data-schemas-list` before saying data doesn't exist.\n- **Check prefixes.** Imported tables are often prefixed (e.g. `stripe_charges` not `charges`). The user might not know the prefix.\n- **Collect credentials securely.** Use `data-warehouse-source-connect-link` to hand the user a browser link — it opens a minimal connect page rendering the source's full connection form (OAuth or credentials, whichever the source offers) that stashes the details temporarily without creating the source. Afterwards pass `{\"credential_id\": \u003Cid>}` (discovered via `data-warehouse-stored-credentials-list`) to `data-warehouse-source-setup` — stored credentials are single-use and expire after 24 hours. Don't collect passwords or OAuth tokens in chat.\n- **Not all systems are supported.** If the user's system isn't in the wizard list, suggest using Postgres\u002FMySQL as a bridge if they can export to a database, or mention that custom sources can be requested.\n\n## Related tools\n\n- `posthog:external-data-sources-list`: Check existing source connections\n- `posthog:external-data-schemas-list`: Check what tables are already imported\n- `posthog:read-data-warehouse-schema`: See all queryable tables including views\n- `posthog:external-data-sources-wizard`: Get available source types\n- `posthog:data-warehouse-source-connect-link`: Get a secure browser\u002FOAuth link to collect credentials\n- `posthog:data-warehouse-source-setup`: One-step create (validate, discover tables, apply sync defaults, create)\n- `posthog:execute-sql`: Run queries to demonstrate what's possible\n\n## Related skills\n\n- **`setting-up-a-data-warehouse-source`**: Full source creation workflow — hand off here once the user decides to connect a source\n",{"data":38,"body":39},{"name":4,"description":6},{"type":40,"children":41},"root",[42,50,56,63,76,82,117,123,130,135,153,158,164,178,191,204,210,223,231,408,414,419,437,466,472,504,510,523,528,552,558,660,666,741,747],{"type":43,"tag":44,"props":45,"children":46},"element","h1",{"id":4},[47],{"type":48,"value":49},"text","Suggesting data imports",{"type":43,"tag":51,"props":52,"children":53},"p",{},[54],{"type":48,"value":55},"This skill helps identify when data the user needs lives outside PostHog and guides them toward importing it via the data warehouse. The key insight is recognizing the gap — then connecting it to the right source type.",{"type":43,"tag":57,"props":58,"children":60},"h2",{"id":59},"what-posthog-collects-natively",[61],{"type":48,"value":62},"What PostHog collects natively",{"type":43,"tag":51,"props":64,"children":65},{},[66,68,74],{"type":48,"value":67},"PostHog collects product analytics events, persons, sessions, and groups via its SDKs. Additional products are available but must be enabled: session replay, feature flags, experiments, surveys, web analytics, error tracking, AI observability, conversations, logs, revenue analytics, workflows, CDP destinations, and batch exports. PostHog does ",{"type":43,"tag":69,"props":70,"children":71},"strong",{},[72],{"type":48,"value":73},"not",{"type":48,"value":75}," collect external business data like payments, subscriptions, CRM records, support tickets from other systems, or production database tables — that data must be imported via the data warehouse.",{"type":43,"tag":57,"props":77,"children":79},{"id":78},"when-to-use-this-skill",[80],{"type":48,"value":81},"When to use this skill",{"type":43,"tag":83,"props":84,"children":85},"ul",{},[86,92,97,102,107,112],{"type":43,"tag":87,"props":88,"children":89},"li",{},[90],{"type":48,"value":91},"A HogQL query fails because a table doesn't exist",{"type":43,"tag":87,"props":93,"children":94},{},[95],{"type":48,"value":96},"The user asks about data from an external system (Stripe, Hubspot, Salesforce, etc.)",{"type":43,"tag":87,"props":98,"children":99},{},[100],{"type":48,"value":101},"The user wants to correlate PostHog analytics with business data (revenue, support tickets, CRM records, etc)",{"type":43,"tag":87,"props":103,"children":104},{},[105],{"type":48,"value":106},"The user asks \"how do I get my X data into PostHog?\"",{"type":43,"tag":87,"props":108,"children":109},{},[110],{"type":48,"value":111},"Analysis requires joining PostHog events with external data",{"type":43,"tag":87,"props":113,"children":114},{},[115],{"type":48,"value":116},"The user asks about exporting PostHog data for comparison elsewhere (in a google sheet, external warehouse, etc)",{"type":43,"tag":57,"props":118,"children":120},{"id":119},"workflow",[121],{"type":48,"value":122},"Workflow",{"type":43,"tag":124,"props":125,"children":127},"h3",{"id":126},"_1-understand-what-data-is-missing",[128],{"type":48,"value":129},"1. Understand what data is missing",{"type":43,"tag":51,"props":131,"children":132},{},[133],{"type":48,"value":134},"Listen for signals that the user needs external data:",{"type":43,"tag":83,"props":136,"children":137},{},[138,143,148],{"type":43,"tag":87,"props":139,"children":140},{},[141],{"type":48,"value":142},"They mention a specific tool or system (Stripe, Hubspot, Zendesk, their production database, etc.)",{"type":43,"tag":87,"props":144,"children":145},{},[146],{"type":48,"value":147},"A query references a table that doesn't exist in PostHog",{"type":43,"tag":87,"props":149,"children":150},{},[151],{"type":48,"value":152},"They want to analyze something PostHog doesn't track natively (revenue, support tickets, CRM deals, etc.)",{"type":43,"tag":51,"props":154,"children":155},{},[156],{"type":48,"value":157},"If a query failed, check the error — if it's \"table not found\" or similar, the data likely needs to be imported.",{"type":43,"tag":124,"props":159,"children":161},{"id":160},"_2-check-whats-already-connected",[162],{"type":48,"value":163},"2. Check what's already connected",{"type":43,"tag":51,"props":165,"children":166},{},[167,169,176],{"type":48,"value":168},"Call ",{"type":43,"tag":170,"props":171,"children":173},"code",{"className":172},[],[174],{"type":48,"value":175},"posthog:external-data-sources-list",{"type":48,"value":177}," to see existing sources. The data might already be imported but the user doesn't know the table name or prefix.",{"type":43,"tag":51,"props":179,"children":180},{},[181,183,189],{"type":48,"value":182},"If a source exists for the system they're asking about, call ",{"type":43,"tag":170,"props":184,"children":186},{"className":185},[],[187],{"type":48,"value":188},"posthog:external-data-schemas-list",{"type":48,"value":190}," to show the available tables. The data might be there but under a different name or prefix.",{"type":43,"tag":51,"props":192,"children":193},{},[194,196,202],{"type":48,"value":195},"Also call ",{"type":43,"tag":170,"props":197,"children":199},{"className":198},[],[200],{"type":48,"value":201},"posthog:read-data-warehouse-schema",{"type":48,"value":203}," to see all queryable tables — the data might already be available as a view or joined table.",{"type":43,"tag":124,"props":205,"children":207},{"id":206},"_3-identify-the-right-source-type",[208],{"type":48,"value":209},"3. Identify the right source type",{"type":43,"tag":51,"props":211,"children":212},{},[213,215,221],{"type":48,"value":214},"If the data isn't imported yet, call ",{"type":43,"tag":170,"props":216,"children":218},{"className":217},[],[219],{"type":48,"value":220},"posthog:external-data-sources-wizard",{"type":48,"value":222}," to see available source types. Match the user's need to a source:",{"type":43,"tag":51,"props":224,"children":225},{},[226],{"type":43,"tag":69,"props":227,"children":228},{},[229],{"type":48,"value":230},"Common patterns:",{"type":43,"tag":232,"props":233,"children":234},"table",{},[235,259],{"type":43,"tag":236,"props":237,"children":238},"thead",{},[239],{"type":43,"tag":240,"props":241,"children":242},"tr",{},[243,249,254],{"type":43,"tag":244,"props":245,"children":246},"th",{},[247],{"type":48,"value":248},"User wants",{"type":43,"tag":244,"props":250,"children":251},{},[252],{"type":48,"value":253},"Source type",{"type":43,"tag":244,"props":255,"children":256},{},[257],{"type":48,"value":258},"Key tables",{"type":43,"tag":260,"props":261,"children":262},"tbody",{},[263,282,300,318,336,354,372,390],{"type":43,"tag":240,"props":264,"children":265},{},[266,272,277],{"type":43,"tag":267,"props":268,"children":269},"td",{},[270],{"type":48,"value":271},"Revenue \u002F payment data",{"type":43,"tag":267,"props":273,"children":274},{},[275],{"type":48,"value":276},"Stripe, Chargebee, Shopify",{"type":43,"tag":267,"props":278,"children":279},{},[280],{"type":48,"value":281},"charges, subscriptions, invoices, customers",{"type":43,"tag":240,"props":283,"children":284},{},[285,290,295],{"type":43,"tag":267,"props":286,"children":287},{},[288],{"type":48,"value":289},"CRM \u002F sales pipeline",{"type":43,"tag":267,"props":291,"children":292},{},[293],{"type":48,"value":294},"Hubspot, Salesforce, Attio",{"type":43,"tag":267,"props":296,"children":297},{},[298],{"type":48,"value":299},"contacts, deals, companies",{"type":43,"tag":240,"props":301,"children":302},{},[303,308,313],{"type":43,"tag":267,"props":304,"children":305},{},[306],{"type":48,"value":307},"Support tickets",{"type":43,"tag":267,"props":309,"children":310},{},[311],{"type":48,"value":312},"Zendesk",{"type":43,"tag":267,"props":314,"children":315},{},[316],{"type":48,"value":317},"tickets, users, organizations",{"type":43,"tag":240,"props":319,"children":320},{},[321,326,331],{"type":43,"tag":267,"props":322,"children":323},{},[324],{"type":48,"value":325},"Product data from their DB",{"type":43,"tag":267,"props":327,"children":328},{},[329],{"type":48,"value":330},"Postgres, MySQL, BigQuery, Snowflake, Redshift",{"type":43,"tag":267,"props":332,"children":333},{},[334],{"type":48,"value":335},"user's own tables",{"type":43,"tag":240,"props":337,"children":338},{},[339,344,349],{"type":43,"tag":267,"props":340,"children":341},{},[342],{"type":48,"value":343},"Marketing \u002F ads",{"type":43,"tag":267,"props":345,"children":346},{},[347],{"type":48,"value":348},"Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads",{"type":43,"tag":267,"props":350,"children":351},{},[352],{"type":48,"value":353},"campaigns, ad_groups, ads",{"type":43,"tag":240,"props":355,"children":356},{},[357,362,367],{"type":43,"tag":267,"props":358,"children":359},{},[360],{"type":48,"value":361},"Email marketing",{"type":43,"tag":267,"props":363,"children":364},{},[365],{"type":48,"value":366},"Mailchimp, Klaviyo",{"type":43,"tag":267,"props":368,"children":369},{},[370],{"type":48,"value":371},"campaigns, lists, subscribers",{"type":43,"tag":240,"props":373,"children":374},{},[375,380,385],{"type":43,"tag":267,"props":376,"children":377},{},[378],{"type":48,"value":379},"Project management",{"type":43,"tag":267,"props":381,"children":382},{},[383],{"type":48,"value":384},"Linear",{"type":43,"tag":267,"props":386,"children":387},{},[388],{"type":48,"value":389},"issues, projects",{"type":43,"tag":240,"props":391,"children":392},{},[393,398,403],{"type":43,"tag":267,"props":394,"children":395},{},[396],{"type":48,"value":397},"Error tracking (external)",{"type":43,"tag":267,"props":399,"children":400},{},[401],{"type":48,"value":402},"Sentry",{"type":43,"tag":267,"props":404,"children":405},{},[406],{"type":48,"value":407},"issues, events",{"type":43,"tag":124,"props":409,"children":411},{"id":410},"_4-suggest-the-import",[412],{"type":48,"value":413},"4. Suggest the import",{"type":43,"tag":51,"props":415,"children":416},{},[417],{"type":48,"value":418},"Present the recommendation concisely:",{"type":43,"tag":83,"props":420,"children":421},{},[422,427,432],{"type":43,"tag":87,"props":423,"children":424},{},[425],{"type":48,"value":426},"What source type to connect",{"type":43,"tag":87,"props":428,"children":429},{},[430],{"type":48,"value":431},"What tables would become available",{"type":43,"tag":87,"props":433,"children":434},{},[435],{"type":48,"value":436},"How this enables the analysis they want",{"type":43,"tag":51,"props":438,"children":439},{},[440,442,448,450,456,458,464],{"type":48,"value":441},"Example: \"Your Stripe data isn't in PostHog yet. If you connect a Stripe source, you'll get tables like ",{"type":43,"tag":170,"props":443,"children":445},{"className":444},[],[446],{"type":48,"value":447},"charges",{"type":48,"value":449},", ",{"type":43,"tag":170,"props":451,"children":453},{"className":452},[],[454],{"type":48,"value":455},"subscriptions",{"type":48,"value":457},", and ",{"type":43,"tag":170,"props":459,"children":461},{"className":460},[],[462],{"type":48,"value":463},"customers",{"type":48,"value":465}," that you can join with PostHog events to analyze revenue by user behavior.\"",{"type":43,"tag":124,"props":467,"children":469},{"id":468},"_5-offer-to-set-up-the-source",[470],{"type":48,"value":471},"5. Offer to set up the source",{"type":43,"tag":51,"props":473,"children":474},{},[475,477,483,485,491,493,502],{"type":48,"value":476},"If the user wants to proceed, the fastest path is the one-step ",{"type":43,"tag":170,"props":478,"children":480},{"className":479},[],[481],{"type":48,"value":482},"data-warehouse-source-setup",{"type":48,"value":484}," tool (validate creds →\ndiscover tables → sync defaults → create, in one call), with ",{"type":43,"tag":170,"props":486,"children":488},{"className":487},[],[489],{"type":48,"value":490},"data-warehouse-source-connect-link",{"type":48,"value":492}," to collect\ncredentials securely in the browser rather than in chat. For anything beyond the happy path (hand-picking tables,\nnon-default sync types, webhooks, CDC), hand off to the ",{"type":43,"tag":69,"props":494,"children":495},{},[496],{"type":43,"tag":170,"props":497,"children":499},{"className":498},[],[500],{"type":48,"value":501},"setting-up-a-data-warehouse-source",{"type":48,"value":503}," skill, which covers\nthe full flow, sync-type selection, webhook registration, and prefix guidance. Do not duplicate that workflow here.",{"type":43,"tag":124,"props":505,"children":507},{"id":506},"_6-show-whats-possible-after-import",[508],{"type":48,"value":509},"6. Show what's possible after import",{"type":43,"tag":51,"props":511,"children":512},{},[513,515,521],{"type":48,"value":514},"Once connected, help the user write their first query joining PostHog data with the imported data. Use ",{"type":43,"tag":170,"props":516,"children":518},{"className":517},[],[519],{"type":48,"value":520},"posthog:execute-sql",{"type":48,"value":522}," to demonstrate.",{"type":43,"tag":51,"props":524,"children":525},{},[526],{"type":48,"value":527},"Common join patterns:",{"type":43,"tag":83,"props":529,"children":530},{},[531,542,547],{"type":43,"tag":87,"props":532,"children":533},{},[534,536],{"type":48,"value":535},"Join Stripe customers with PostHog persons on email: ",{"type":43,"tag":170,"props":537,"children":539},{"className":538},[],[540],{"type":48,"value":541},"SELECT * FROM stripe_customers sc JOIN persons p ON sc.email = p.properties.$email",{"type":43,"tag":87,"props":543,"children":544},{},[545],{"type":48,"value":546},"Join CRM deals with events: correlate product usage with sales outcomes",{"type":43,"tag":87,"props":548,"children":549},{},[550],{"type":48,"value":551},"Join support tickets with session recordings: find recordings for users who filed tickets",{"type":43,"tag":57,"props":553,"children":555},{"id":554},"important-notes",[556],{"type":48,"value":557},"Important notes",{"type":43,"tag":83,"props":559,"children":560},{},[561,585,610,650],{"type":43,"tag":87,"props":562,"children":563},{},[564,569,571,576,578,583],{"type":43,"tag":69,"props":565,"children":566},{},[567],{"type":48,"value":568},"Don't guess table names.",{"type":48,"value":570}," Always check ",{"type":43,"tag":170,"props":572,"children":574},{"className":573},[],[575],{"type":48,"value":201},{"type":48,"value":577}," and ",{"type":43,"tag":170,"props":579,"children":581},{"className":580},[],[582],{"type":48,"value":188},{"type":48,"value":584}," before saying data doesn't exist.",{"type":43,"tag":87,"props":586,"children":587},{},[588,593,595,601,603,608],{"type":43,"tag":69,"props":589,"children":590},{},[591],{"type":48,"value":592},"Check prefixes.",{"type":48,"value":594}," Imported tables are often prefixed (e.g. ",{"type":43,"tag":170,"props":596,"children":598},{"className":597},[],[599],{"type":48,"value":600},"stripe_charges",{"type":48,"value":602}," not ",{"type":43,"tag":170,"props":604,"children":606},{"className":605},[],[607],{"type":48,"value":447},{"type":48,"value":609},"). The user might not know the prefix.",{"type":43,"tag":87,"props":611,"children":612},{},[613,618,620,625,627,633,635,641,643,648],{"type":43,"tag":69,"props":614,"children":615},{},[616],{"type":48,"value":617},"Collect credentials securely.",{"type":48,"value":619}," Use ",{"type":43,"tag":170,"props":621,"children":623},{"className":622},[],[624],{"type":48,"value":490},{"type":48,"value":626}," to hand the user a browser link — it opens a minimal connect page rendering the source's full connection form (OAuth or credentials, whichever the source offers) that stashes the details temporarily without creating the source. Afterwards pass ",{"type":43,"tag":170,"props":628,"children":630},{"className":629},[],[631],{"type":48,"value":632},"{\"credential_id\": \u003Cid>}",{"type":48,"value":634}," (discovered via ",{"type":43,"tag":170,"props":636,"children":638},{"className":637},[],[639],{"type":48,"value":640},"data-warehouse-stored-credentials-list",{"type":48,"value":642},") to ",{"type":43,"tag":170,"props":644,"children":646},{"className":645},[],[647],{"type":48,"value":482},{"type":48,"value":649}," — stored credentials are single-use and expire after 24 hours. Don't collect passwords or OAuth tokens in chat.",{"type":43,"tag":87,"props":651,"children":652},{},[653,658],{"type":43,"tag":69,"props":654,"children":655},{},[656],{"type":48,"value":657},"Not all systems are supported.",{"type":48,"value":659}," If the user's system isn't in the wizard list, suggest using Postgres\u002FMySQL as a bridge if they can export to a database, or mention that custom sources can be requested.",{"type":43,"tag":57,"props":661,"children":663},{"id":662},"related-tools",[664],{"type":48,"value":665},"Related tools",{"type":43,"tag":83,"props":667,"children":668},{},[669,679,689,699,709,720,731],{"type":43,"tag":87,"props":670,"children":671},{},[672,677],{"type":43,"tag":170,"props":673,"children":675},{"className":674},[],[676],{"type":48,"value":175},{"type":48,"value":678},": Check existing source connections",{"type":43,"tag":87,"props":680,"children":681},{},[682,687],{"type":43,"tag":170,"props":683,"children":685},{"className":684},[],[686],{"type":48,"value":188},{"type":48,"value":688},": Check what tables are already imported",{"type":43,"tag":87,"props":690,"children":691},{},[692,697],{"type":43,"tag":170,"props":693,"children":695},{"className":694},[],[696],{"type":48,"value":201},{"type":48,"value":698},": See all queryable tables including views",{"type":43,"tag":87,"props":700,"children":701},{},[702,707],{"type":43,"tag":170,"props":703,"children":705},{"className":704},[],[706],{"type":48,"value":220},{"type":48,"value":708},": Get available source types",{"type":43,"tag":87,"props":710,"children":711},{},[712,718],{"type":43,"tag":170,"props":713,"children":715},{"className":714},[],[716],{"type":48,"value":717},"posthog:data-warehouse-source-connect-link",{"type":48,"value":719},": Get a secure browser\u002FOAuth link to collect credentials",{"type":43,"tag":87,"props":721,"children":722},{},[723,729],{"type":43,"tag":170,"props":724,"children":726},{"className":725},[],[727],{"type":48,"value":728},"posthog:data-warehouse-source-setup",{"type":48,"value":730},": One-step create (validate, discover tables, apply sync defaults, create)",{"type":43,"tag":87,"props":732,"children":733},{},[734,739],{"type":43,"tag":170,"props":735,"children":737},{"className":736},[],[738],{"type":48,"value":520},{"type":48,"value":740},": Run queries to demonstrate what's possible",{"type":43,"tag":57,"props":742,"children":744},{"id":743},"related-skills",[745],{"type":48,"value":746},"Related skills",{"type":43,"tag":83,"props":748,"children":749},{},[750],{"type":43,"tag":87,"props":751,"children":752},{},[753,761],{"type":43,"tag":69,"props":754,"children":755},{},[756],{"type":43,"tag":170,"props":757,"children":759},{"className":758},[],[760],{"type":48,"value":501},{"type":48,"value":762},": Full source creation workflow — hand off here once the user decides to connect a source",{"items":764,"total":935},[765,782,794,807,820,835,851,868,882,897,907,925],{"slug":766,"name":766,"fn":767,"description":768,"org":769,"tags":770,"stars":779,"repoUrl":780,"updatedAt":781},"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},[771,772,775,778],{"name":24,"slug":25,"type":13},{"name":773,"slug":774,"type":13},"Cost Optimization","cost-optimization",{"name":776,"slug":777,"type":13},"Observability","observability",{"name":9,"slug":8,"type":13},35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-28T05:34:11.117757",{"slug":783,"name":783,"fn":784,"description":785,"org":786,"tags":787,"stars":779,"repoUrl":780,"updatedAt":793},"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},[788,789,792],{"name":24,"slug":25,"type":13},{"name":790,"slug":791,"type":13},"Audit","audit",{"name":9,"slug":8,"type":13},"2026-06-08T08:08:33.693989",{"slug":795,"name":795,"fn":796,"description":797,"org":798,"tags":799,"stars":779,"repoUrl":780,"updatedAt":806},"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},[800,801,804,805],{"name":790,"slug":791,"type":13},{"name":802,"slug":803,"type":13},"Data Warehouse","data-warehouse",{"name":776,"slug":777,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:22:57.67984",{"slug":808,"name":808,"fn":809,"description":810,"org":811,"tags":812,"stars":779,"repoUrl":780,"updatedAt":819},"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},[813,814,815,818],{"name":790,"slug":791,"type":13},{"name":802,"slug":803,"type":13},{"name":816,"slug":817,"type":13},"Performance","performance",{"name":9,"slug":8,"type":13},"2026-06-18T08:25:10.936787",{"slug":821,"name":821,"fn":822,"description":823,"org":824,"tags":825,"stars":779,"repoUrl":780,"updatedAt":834},"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},[826,829,832,833],{"name":827,"slug":828,"type":13},"Alerting","alerting",{"name":830,"slug":831,"type":13},"Debugging","debugging",{"name":776,"slug":777,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:24:40.318583",{"slug":836,"name":836,"fn":837,"description":838,"org":839,"tags":840,"stars":779,"repoUrl":780,"updatedAt":850},"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},[841,842,845,846,849],{"name":24,"slug":25,"type":13},{"name":843,"slug":844,"type":13},"Monitoring","monitoring",{"name":776,"slug":777,"type":13},{"name":847,"slug":848,"type":13},"Operations","operations",{"name":9,"slug":8,"type":13},"2026-07-18T05:10:54.430898",{"slug":852,"name":852,"fn":853,"description":854,"org":855,"tags":856,"stars":779,"repoUrl":780,"updatedAt":867},"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},[857,860,863,864],{"name":858,"slug":859,"type":13},"Automation","automation",{"name":861,"slug":862,"type":13},"MCP","mcp",{"name":9,"slug":8,"type":13},{"name":865,"slug":866,"type":13},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",{"slug":869,"name":869,"fn":870,"description":871,"org":872,"tags":873,"stars":779,"repoUrl":780,"updatedAt":881},"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},[874,875,876,879,880],{"name":24,"slug":25,"type":13},{"name":830,"slug":831,"type":13},{"name":877,"slug":878,"type":13},"Frontend","frontend",{"name":776,"slug":777,"type":13},{"name":9,"slug":8,"type":13},"2026-05-07T05:56:19.828048",{"slug":883,"name":883,"fn":884,"description":885,"org":886,"tags":887,"stars":779,"repoUrl":780,"updatedAt":896},"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},[888,891,892,893],{"name":889,"slug":890,"type":13},"API Development","api-development",{"name":877,"slug":878,"type":13},{"name":9,"slug":8,"type":13},{"name":894,"slug":895,"type":13},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":898,"name":898,"fn":899,"description":900,"org":901,"tags":902,"stars":779,"repoUrl":780,"updatedAt":906},"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},[903,904,905],{"name":889,"slug":890,"type":13},{"name":847,"slug":848,"type":13},{"name":9,"slug":8,"type":13},"2026-07-15T05:29:58.442727",{"slug":908,"name":908,"fn":909,"description":910,"org":911,"tags":912,"stars":779,"repoUrl":780,"updatedAt":924},"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},[913,914,917,918,921],{"name":858,"slug":859,"type":13},{"name":915,"slug":916,"type":13},"Email","email",{"name":9,"slug":8,"type":13},{"name":919,"slug":920,"type":13},"Reporting","reporting",{"name":922,"slug":923,"type":13},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":926,"name":926,"fn":927,"description":928,"org":929,"tags":930,"stars":779,"repoUrl":780,"updatedAt":934},"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},[931,932,933],{"name":24,"slug":25,"type":13},{"name":889,"slug":890,"type":13},{"name":9,"slug":8,"type":13},"2026-06-08T08:08:29.624498",231,{"items":937,"total":1038},[938,955,969,983,999,1011,1022],{"slug":939,"name":939,"fn":940,"description":941,"org":942,"tags":943,"stars":26,"repoUrl":27,"updatedAt":954},"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},[944,947,950,951],{"name":945,"slug":946,"type":13},"Communications","communications",{"name":948,"slug":949,"type":13},"CRM","crm",{"name":9,"slug":8,"type":13},{"name":952,"slug":953,"type":13},"Sales","sales","2026-04-16T05:13:00.172732",{"slug":956,"name":956,"fn":957,"description":958,"org":959,"tags":960,"stars":26,"repoUrl":27,"updatedAt":968},"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},[961,962,963,966,967],{"name":790,"slug":791,"type":13},{"name":15,"slug":16,"type":13},{"name":964,"slug":965,"type":13},"Data Quality","data-quality",{"name":776,"slug":777,"type":13},{"name":9,"slug":8,"type":13},"2026-06-21T08:19:05.85849",{"slug":970,"name":970,"fn":971,"description":972,"org":973,"tags":974,"stars":26,"repoUrl":27,"updatedAt":982},"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},[975,978,981],{"name":976,"slug":977,"type":13},"Deployment","deployment",{"name":979,"slug":980,"type":13},"Feature Flags","feature-flags",{"name":9,"slug":8,"type":13},"2026-05-04T05:56:44.484909",{"slug":984,"name":984,"fn":985,"description":986,"org":987,"tags":988,"stars":26,"repoUrl":27,"updatedAt":998},"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},[989,992,993,996,997],{"name":990,"slug":991,"type":13},"A\u002FB Testing","a-b-testing",{"name":24,"slug":25,"type":13},{"name":994,"slug":995,"type":13},"Data Analysis","data-analysis",{"name":830,"slug":831,"type":13},{"name":9,"slug":8,"type":13},"2026-05-22T06:59:58.103867",{"slug":1000,"name":1000,"fn":1001,"description":1002,"org":1003,"tags":1004,"stars":26,"repoUrl":27,"updatedAt":1010},"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},[1005,1006,1007,1008,1009],{"name":24,"slug":25,"type":13},{"name":830,"slug":831,"type":13},{"name":877,"slug":878,"type":13},{"name":776,"slug":777,"type":13},{"name":9,"slug":8,"type":13},"2026-04-22T05:06:51.989772",{"slug":1012,"name":1012,"fn":1013,"description":1014,"org":1015,"tags":1016,"stars":26,"repoUrl":27,"updatedAt":1021},"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},[1017,1018,1019,1020],{"name":24,"slug":25,"type":13},{"name":830,"slug":831,"type":13},{"name":776,"slug":777,"type":13},{"name":9,"slug":8,"type":13},"2026-04-27T05:46:14.554016",{"slug":1023,"name":1023,"fn":1024,"description":1025,"org":1026,"tags":1027,"stars":26,"repoUrl":27,"updatedAt":1037},"error-tracking-android","track Android errors with PostHog","PostHog error tracking for Android",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1028,1031,1032,1035,1036],{"name":1029,"slug":1030,"type":13},"Android","android",{"name":830,"slug":831,"type":13},{"name":1033,"slug":1034,"type":13},"Mobile","mobile",{"name":776,"slug":777,"type":13},{"name":9,"slug":8,"type":13},"2026-04-06T18:46:26.982494",110]