[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-omnibus-instrument-logs":3,"mdc--93ko7-key":34,"related-org-posthog-omnibus-instrument-logs":416,"related-repo-posthog-omnibus-instrument-logs":589},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":29,"sourceUrl":32,"mdContent":33},"omnibus-instrument-logs","instrument applications with PostHog log capture","Add PostHog log capture to track application logs. Use after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. Also handles initial OTLP exporter setup if not yet configured.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"posthog","PostHog","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fposthog.png",[12,16,19,20],{"name":13,"slug":14,"type":15},"Observability","observability","tag",{"name":17,"slug":18,"type":15},"Logs","logs",{"name":9,"slug":8,"type":15},{"name":21,"slug":22,"type":15},"Integrations","integrations",56,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills","2026-04-06T18:44:19.025129",null,4,[],{"repoUrl":24,"stars":23,"forks":27,"topics":30,"description":31},[],"PostHog skills (under construction)","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002Fposthog\u002Flogs\u002Fskills\u002Fall","---\nname: omnibus-instrument-logs\ndescription: >-\n  Add PostHog log capture to track application logs. Use after implementing\n  features or reviewing PRs to ensure meaningful log events are captured with\n  structured properties. Also handles initial OTLP exporter setup if not yet\n  configured.\nmetadata:\n  author: PostHog\n  version: 1.9.4\n---\n\n# Add PostHog log capture\n\nUse this skill to add PostHog log capture for new or changed code. Use it after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. If PostHog log export is not yet configured, this skill also covers initial OTLP exporter setup. Supports any platform or language.\n\nSupported platforms: Next.js, Node.js, Python, Go, Java, Datadog, and any language via OpenTelemetry.\n\n## Instructions\n\nFollow these steps IN ORDER:\n\nSTEP 1: Analyze the codebase and detect the platform.\n  - Detect the language, framework, and existing logging setup.\n  - Look for log libraries (winston, pino, logging module, logrus, log4j, serilog, etc.).\n  - Look for lockfiles to determine the package manager.\n  - Check for existing PostHog log export setup. If the OTLP exporter is already configured, skip to STEP 5 to add log capture for new code.\n\nSTEP 2: Research log capture. (Skip if PostHog log export is already configured.)\n  2.1. Find the reference file below that matches the detected platform — it is the source of truth for OTLP exporter configuration and integration with existing logging. Read it now.\n  2.2. If no reference matches, use the \"Other Languages\" reference as a fallback — it covers the generic OpenTelemetry approach.\n\nSTEP 3: Install dependencies. (Skip if PostHog log export is already configured.)\n  - Install the OpenTelemetry SDK and OTLP exporter packages for the detected platform.\n  - Do not manually edit dependency files — use the package manager's install command.\n  - Always install packages as a background task. Don't await completion; proceed with other work immediately.\n\nSTEP 4: Configure the OTLP exporter. (Skip if PostHog log export is already configured.)\n  - PostHog logs use the OpenTelemetry protocol. Set up an OTLP exporter pointed at PostHog's ingest endpoint.\n  - Follow the platform-specific reference for the exact configuration.\n\nSTEP 5: Integrate with existing logging.\n  - Add the PostHog log exporter alongside existing logging. Don't replace existing log handlers or outputs.\n  - Do not alter the fundamental architecture of existing files. Make additions minimal and targeted.\n  - You must read a file immediately before attempting to write it.\n\nSTEP 6: Add structured properties.\n  - Ensure logs include structured key-value properties for filtering and search in PostHog.\n  - Prefer structured log formats with key-value properties over plain text messages.\n\nSTEP 7: Set up environment variables.\n  - If an env-file-tools MCP server is connected, use check_env_keys then set_env_values to configure the PostHog API key, host, and OpenTelemetry endpoint.\n  - Reference these environment variables in code instead of hardcoding them.\n\n## Reference files\n\n- `references\u002Fnextjs.md` - Next.js logs installation - docs\n- `references\u002Fnodejs.md` - Node.js logs installation - docs\n- `references\u002Fpython.md` - Python logs installation - docs\n- `references\u002Fgo.md` - Go logs installation - docs\n- `references\u002Fjava.md` - Java logs installation - docs\n- `references\u002Fdatadog.md` - Datadog logs installation - docs\n- `references\u002Fother.md` - Other languages logs installation - docs\n- `references\u002Fstart-here.md` - Getting started with logs - docs\n- `references\u002Fsearch.md` - Search logs - docs\n- `references\u002Fbest-practices.md` - Logging best practices - docs\n- `references\u002Ftroubleshooting.md` - Logs troubleshooting - docs\n- `references\u002Flink-session-replay.md` - Link session replay - docs\n- `references\u002Fdebug-logs-mcp.md` - Debug logs with mcp - docs\n\nEach platform reference contains specific OTLP configuration, SDK setup, and integration patterns. Find the one matching the user's stack.\n\n## Key principles\n\n- **Environment variables**: Always use environment variables for PostHog keys and OpenTelemetry endpoints. Never hardcode them.\n- **Minimal changes**: Add log export alongside existing logging. Don't replace or restructure existing logging code.\n- **OpenTelemetry**: PostHog logs use the OpenTelemetry protocol. Configure an OTLP exporter pointed at PostHog's ingest endpoint.\n- **Structured logging**: Prefer structured log formats with key-value properties over plain text messages.",{"data":35,"body":38},{"name":4,"description":6,"metadata":36},{"author":9,"version":37},"1.9.4",{"type":39,"children":40},"root",[41,50,56,61,68,73,78,103,108,113,131,136,149,154,172,177,190,195,208,214,361,366,372],{"type":42,"tag":43,"props":44,"children":46},"element","h1",{"id":45},"add-posthog-log-capture",[47],{"type":48,"value":49},"text","Add PostHog log capture",{"type":42,"tag":51,"props":52,"children":53},"p",{},[54],{"type":48,"value":55},"Use this skill to add PostHog log capture for new or changed code. Use it after implementing features or reviewing PRs to ensure meaningful log events are captured with structured properties. If PostHog log export is not yet configured, this skill also covers initial OTLP exporter setup. Supports any platform or language.",{"type":42,"tag":51,"props":57,"children":58},{},[59],{"type":48,"value":60},"Supported platforms: Next.js, Node.js, Python, Go, Java, Datadog, and any language via OpenTelemetry.",{"type":42,"tag":62,"props":63,"children":65},"h2",{"id":64},"instructions",[66],{"type":48,"value":67},"Instructions",{"type":42,"tag":51,"props":69,"children":70},{},[71],{"type":48,"value":72},"Follow these steps IN ORDER:",{"type":42,"tag":51,"props":74,"children":75},{},[76],{"type":48,"value":77},"STEP 1: Analyze the codebase and detect the platform.",{"type":42,"tag":79,"props":80,"children":81},"ul",{},[82,88,93,98],{"type":42,"tag":83,"props":84,"children":85},"li",{},[86],{"type":48,"value":87},"Detect the language, framework, and existing logging setup.",{"type":42,"tag":83,"props":89,"children":90},{},[91],{"type":48,"value":92},"Look for log libraries (winston, pino, logging module, logrus, log4j, serilog, etc.).",{"type":42,"tag":83,"props":94,"children":95},{},[96],{"type":48,"value":97},"Look for lockfiles to determine the package manager.",{"type":42,"tag":83,"props":99,"children":100},{},[101],{"type":48,"value":102},"Check for existing PostHog log export setup. If the OTLP exporter is already configured, skip to STEP 5 to add log capture for new code.",{"type":42,"tag":51,"props":104,"children":105},{},[106],{"type":48,"value":107},"STEP 2: Research log capture. (Skip if PostHog log export is already configured.)\n2.1. Find the reference file below that matches the detected platform — it is the source of truth for OTLP exporter configuration and integration with existing logging. Read it now.\n2.2. If no reference matches, use the \"Other Languages\" reference as a fallback — it covers the generic OpenTelemetry approach.",{"type":42,"tag":51,"props":109,"children":110},{},[111],{"type":48,"value":112},"STEP 3: Install dependencies. (Skip if PostHog log export is already configured.)",{"type":42,"tag":79,"props":114,"children":115},{},[116,121,126],{"type":42,"tag":83,"props":117,"children":118},{},[119],{"type":48,"value":120},"Install the OpenTelemetry SDK and OTLP exporter packages for the detected platform.",{"type":42,"tag":83,"props":122,"children":123},{},[124],{"type":48,"value":125},"Do not manually edit dependency files — use the package manager's install command.",{"type":42,"tag":83,"props":127,"children":128},{},[129],{"type":48,"value":130},"Always install packages as a background task. Don't await completion; proceed with other work immediately.",{"type":42,"tag":51,"props":132,"children":133},{},[134],{"type":48,"value":135},"STEP 4: Configure the OTLP exporter. (Skip if PostHog log export is already configured.)",{"type":42,"tag":79,"props":137,"children":138},{},[139,144],{"type":42,"tag":83,"props":140,"children":141},{},[142],{"type":48,"value":143},"PostHog logs use the OpenTelemetry protocol. Set up an OTLP exporter pointed at PostHog's ingest endpoint.",{"type":42,"tag":83,"props":145,"children":146},{},[147],{"type":48,"value":148},"Follow the platform-specific reference for the exact configuration.",{"type":42,"tag":51,"props":150,"children":151},{},[152],{"type":48,"value":153},"STEP 5: Integrate with existing logging.",{"type":42,"tag":79,"props":155,"children":156},{},[157,162,167],{"type":42,"tag":83,"props":158,"children":159},{},[160],{"type":48,"value":161},"Add the PostHog log exporter alongside existing logging. Don't replace existing log handlers or outputs.",{"type":42,"tag":83,"props":163,"children":164},{},[165],{"type":48,"value":166},"Do not alter the fundamental architecture of existing files. Make additions minimal and targeted.",{"type":42,"tag":83,"props":168,"children":169},{},[170],{"type":48,"value":171},"You must read a file immediately before attempting to write it.",{"type":42,"tag":51,"props":173,"children":174},{},[175],{"type":48,"value":176},"STEP 6: Add structured properties.",{"type":42,"tag":79,"props":178,"children":179},{},[180,185],{"type":42,"tag":83,"props":181,"children":182},{},[183],{"type":48,"value":184},"Ensure logs include structured key-value properties for filtering and search in PostHog.",{"type":42,"tag":83,"props":186,"children":187},{},[188],{"type":48,"value":189},"Prefer structured log formats with key-value properties over plain text messages.",{"type":42,"tag":51,"props":191,"children":192},{},[193],{"type":48,"value":194},"STEP 7: Set up environment variables.",{"type":42,"tag":79,"props":196,"children":197},{},[198,203],{"type":42,"tag":83,"props":199,"children":200},{},[201],{"type":48,"value":202},"If an env-file-tools MCP server is connected, use check_env_keys then set_env_values to configure the PostHog API key, host, and OpenTelemetry endpoint.",{"type":42,"tag":83,"props":204,"children":205},{},[206],{"type":48,"value":207},"Reference these environment variables in code instead of hardcoding them.",{"type":42,"tag":62,"props":209,"children":211},{"id":210},"reference-files",[212],{"type":48,"value":213},"Reference files",{"type":42,"tag":79,"props":215,"children":216},{},[217,229,240,251,262,273,284,295,306,317,328,339,350],{"type":42,"tag":83,"props":218,"children":219},{},[220,227],{"type":42,"tag":221,"props":222,"children":224},"code",{"className":223},[],[225],{"type":48,"value":226},"references\u002Fnextjs.md",{"type":48,"value":228}," - Next.js logs installation - docs",{"type":42,"tag":83,"props":230,"children":231},{},[232,238],{"type":42,"tag":221,"props":233,"children":235},{"className":234},[],[236],{"type":48,"value":237},"references\u002Fnodejs.md",{"type":48,"value":239}," - Node.js logs installation - docs",{"type":42,"tag":83,"props":241,"children":242},{},[243,249],{"type":42,"tag":221,"props":244,"children":246},{"className":245},[],[247],{"type":48,"value":248},"references\u002Fpython.md",{"type":48,"value":250}," - Python logs installation - docs",{"type":42,"tag":83,"props":252,"children":253},{},[254,260],{"type":42,"tag":221,"props":255,"children":257},{"className":256},[],[258],{"type":48,"value":259},"references\u002Fgo.md",{"type":48,"value":261}," - Go logs installation - docs",{"type":42,"tag":83,"props":263,"children":264},{},[265,271],{"type":42,"tag":221,"props":266,"children":268},{"className":267},[],[269],{"type":48,"value":270},"references\u002Fjava.md",{"type":48,"value":272}," - Java logs installation - docs",{"type":42,"tag":83,"props":274,"children":275},{},[276,282],{"type":42,"tag":221,"props":277,"children":279},{"className":278},[],[280],{"type":48,"value":281},"references\u002Fdatadog.md",{"type":48,"value":283}," - Datadog logs installation - docs",{"type":42,"tag":83,"props":285,"children":286},{},[287,293],{"type":42,"tag":221,"props":288,"children":290},{"className":289},[],[291],{"type":48,"value":292},"references\u002Fother.md",{"type":48,"value":294}," - Other languages logs installation - docs",{"type":42,"tag":83,"props":296,"children":297},{},[298,304],{"type":42,"tag":221,"props":299,"children":301},{"className":300},[],[302],{"type":48,"value":303},"references\u002Fstart-here.md",{"type":48,"value":305}," - Getting started with logs - docs",{"type":42,"tag":83,"props":307,"children":308},{},[309,315],{"type":42,"tag":221,"props":310,"children":312},{"className":311},[],[313],{"type":48,"value":314},"references\u002Fsearch.md",{"type":48,"value":316}," - Search logs - docs",{"type":42,"tag":83,"props":318,"children":319},{},[320,326],{"type":42,"tag":221,"props":321,"children":323},{"className":322},[],[324],{"type":48,"value":325},"references\u002Fbest-practices.md",{"type":48,"value":327}," - Logging best practices - docs",{"type":42,"tag":83,"props":329,"children":330},{},[331,337],{"type":42,"tag":221,"props":332,"children":334},{"className":333},[],[335],{"type":48,"value":336},"references\u002Ftroubleshooting.md",{"type":48,"value":338}," - Logs troubleshooting - docs",{"type":42,"tag":83,"props":340,"children":341},{},[342,348],{"type":42,"tag":221,"props":343,"children":345},{"className":344},[],[346],{"type":48,"value":347},"references\u002Flink-session-replay.md",{"type":48,"value":349}," - Link session replay - docs",{"type":42,"tag":83,"props":351,"children":352},{},[353,359],{"type":42,"tag":221,"props":354,"children":356},{"className":355},[],[357],{"type":48,"value":358},"references\u002Fdebug-logs-mcp.md",{"type":48,"value":360}," - Debug logs with mcp - docs",{"type":42,"tag":51,"props":362,"children":363},{},[364],{"type":48,"value":365},"Each platform reference contains specific OTLP configuration, SDK setup, and integration patterns. Find the one matching the user's stack.",{"type":42,"tag":62,"props":367,"children":369},{"id":368},"key-principles",[370],{"type":48,"value":371},"Key principles",{"type":42,"tag":79,"props":373,"children":374},{},[375,386,396,406],{"type":42,"tag":83,"props":376,"children":377},{},[378,384],{"type":42,"tag":379,"props":380,"children":381},"strong",{},[382],{"type":48,"value":383},"Environment variables",{"type":48,"value":385},": Always use environment variables for PostHog keys and OpenTelemetry endpoints. Never hardcode them.",{"type":42,"tag":83,"props":387,"children":388},{},[389,394],{"type":42,"tag":379,"props":390,"children":391},{},[392],{"type":48,"value":393},"Minimal changes",{"type":48,"value":395},": Add log export alongside existing logging. Don't replace or restructure existing logging code.",{"type":42,"tag":83,"props":397,"children":398},{},[399,404],{"type":42,"tag":379,"props":400,"children":401},{},[402],{"type":48,"value":403},"OpenTelemetry",{"type":48,"value":405},": PostHog logs use the OpenTelemetry protocol. Configure an OTLP exporter pointed at PostHog's ingest endpoint.",{"type":42,"tag":83,"props":407,"children":408},{},[409,414],{"type":42,"tag":379,"props":410,"children":411},{},[412],{"type":48,"value":413},"Structured logging",{"type":48,"value":415},": Prefer structured log formats with key-value properties over plain text messages.",{"items":417,"total":588},[418,435,447,460,473,488,504,521,535,550,560,578],{"slug":419,"name":419,"fn":420,"description":421,"org":422,"tags":423,"stars":432,"repoUrl":433,"updatedAt":434},"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},[424,427,430,431],{"name":425,"slug":426,"type":15},"Analytics","analytics",{"name":428,"slug":429,"type":15},"Cost Optimization","cost-optimization",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-28T05:34:11.117757",{"slug":436,"name":436,"fn":437,"description":438,"org":439,"tags":440,"stars":432,"repoUrl":433,"updatedAt":446},"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},[441,442,445],{"name":425,"slug":426,"type":15},{"name":443,"slug":444,"type":15},"Audit","audit",{"name":9,"slug":8,"type":15},"2026-06-08T08:08:33.693989",{"slug":448,"name":448,"fn":449,"description":450,"org":451,"tags":452,"stars":432,"repoUrl":433,"updatedAt":459},"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},[453,454,457,458],{"name":443,"slug":444,"type":15},{"name":455,"slug":456,"type":15},"Data Warehouse","data-warehouse",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:22:57.67984",{"slug":461,"name":461,"fn":462,"description":463,"org":464,"tags":465,"stars":432,"repoUrl":433,"updatedAt":472},"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},[466,467,468,471],{"name":443,"slug":444,"type":15},{"name":455,"slug":456,"type":15},{"name":469,"slug":470,"type":15},"Performance","performance",{"name":9,"slug":8,"type":15},"2026-06-18T08:25:10.936787",{"slug":474,"name":474,"fn":475,"description":476,"org":477,"tags":478,"stars":432,"repoUrl":433,"updatedAt":487},"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},[479,482,485,486],{"name":480,"slug":481,"type":15},"Alerting","alerting",{"name":483,"slug":484,"type":15},"Debugging","debugging",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:24:40.318583",{"slug":489,"name":489,"fn":490,"description":491,"org":492,"tags":493,"stars":432,"repoUrl":433,"updatedAt":503},"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},[494,495,498,499,502],{"name":425,"slug":426,"type":15},{"name":496,"slug":497,"type":15},"Monitoring","monitoring",{"name":13,"slug":14,"type":15},{"name":500,"slug":501,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-07-18T05:10:54.430898",{"slug":505,"name":505,"fn":506,"description":507,"org":508,"tags":509,"stars":432,"repoUrl":433,"updatedAt":520},"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},[510,513,516,517],{"name":511,"slug":512,"type":15},"Automation","automation",{"name":514,"slug":515,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},{"name":518,"slug":519,"type":15},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",{"slug":522,"name":522,"fn":523,"description":524,"org":525,"tags":526,"stars":432,"repoUrl":433,"updatedAt":534},"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},[527,528,529,532,533],{"name":425,"slug":426,"type":15},{"name":483,"slug":484,"type":15},{"name":530,"slug":531,"type":15},"Frontend","frontend",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-05-07T05:56:19.828048",{"slug":536,"name":536,"fn":537,"description":538,"org":539,"tags":540,"stars":432,"repoUrl":433,"updatedAt":549},"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},[541,544,545,546],{"name":542,"slug":543,"type":15},"API Development","api-development",{"name":530,"slug":531,"type":15},{"name":9,"slug":8,"type":15},{"name":547,"slug":548,"type":15},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":551,"name":551,"fn":552,"description":553,"org":554,"tags":555,"stars":432,"repoUrl":433,"updatedAt":559},"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},[556,557,558],{"name":542,"slug":543,"type":15},{"name":500,"slug":501,"type":15},{"name":9,"slug":8,"type":15},"2026-07-15T05:29:58.442727",{"slug":561,"name":561,"fn":562,"description":563,"org":564,"tags":565,"stars":432,"repoUrl":433,"updatedAt":577},"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},[566,567,570,571,574],{"name":511,"slug":512,"type":15},{"name":568,"slug":569,"type":15},"Email","email",{"name":9,"slug":8,"type":15},{"name":572,"slug":573,"type":15},"Reporting","reporting",{"name":575,"slug":576,"type":15},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":579,"name":579,"fn":580,"description":581,"org":582,"tags":583,"stars":432,"repoUrl":433,"updatedAt":587},"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},[584,585,586],{"name":425,"slug":426,"type":15},{"name":542,"slug":543,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:29.624498",231,{"items":590,"total":693},[591,608,624,638,654,666,677],{"slug":592,"name":592,"fn":593,"description":594,"org":595,"tags":596,"stars":23,"repoUrl":24,"updatedAt":607},"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},[597,600,603,604],{"name":598,"slug":599,"type":15},"Communications","communications",{"name":601,"slug":602,"type":15},"CRM","crm",{"name":9,"slug":8,"type":15},{"name":605,"slug":606,"type":15},"Sales","sales","2026-04-16T05:13:00.172732",{"slug":609,"name":609,"fn":610,"description":611,"org":612,"tags":613,"stars":23,"repoUrl":24,"updatedAt":623},"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},[614,615,618,621,622],{"name":443,"slug":444,"type":15},{"name":616,"slug":617,"type":15},"Data Engineering","data-engineering",{"name":619,"slug":620,"type":15},"Data Quality","data-quality",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-21T08:19:05.85849",{"slug":625,"name":625,"fn":626,"description":627,"org":628,"tags":629,"stars":23,"repoUrl":24,"updatedAt":637},"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},[630,633,636],{"name":631,"slug":632,"type":15},"Deployment","deployment",{"name":634,"slug":635,"type":15},"Feature Flags","feature-flags",{"name":9,"slug":8,"type":15},"2026-05-04T05:56:44.484909",{"slug":639,"name":639,"fn":640,"description":641,"org":642,"tags":643,"stars":23,"repoUrl":24,"updatedAt":653},"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},[644,647,648,651,652],{"name":645,"slug":646,"type":15},"A\u002FB Testing","a-b-testing",{"name":425,"slug":426,"type":15},{"name":649,"slug":650,"type":15},"Data Analysis","data-analysis",{"name":483,"slug":484,"type":15},{"name":9,"slug":8,"type":15},"2026-05-22T06:59:58.103867",{"slug":655,"name":655,"fn":656,"description":657,"org":658,"tags":659,"stars":23,"repoUrl":24,"updatedAt":665},"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},[660,661,662,663,664],{"name":425,"slug":426,"type":15},{"name":483,"slug":484,"type":15},{"name":530,"slug":531,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-04-22T05:06:51.989772",{"slug":667,"name":667,"fn":668,"description":669,"org":670,"tags":671,"stars":23,"repoUrl":24,"updatedAt":676},"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},[672,673,674,675],{"name":425,"slug":426,"type":15},{"name":483,"slug":484,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-04-27T05:46:14.554016",{"slug":678,"name":678,"fn":679,"description":680,"org":681,"tags":682,"stars":23,"repoUrl":24,"updatedAt":692},"error-tracking-android","track Android errors with PostHog","PostHog error tracking for Android",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[683,686,687,690,691],{"name":684,"slug":685,"type":15},"Android","android",{"name":483,"slug":484,"type":15},{"name":688,"slug":689,"type":15},"Mobile","mobile",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-04-06T18:46:26.982494",110]