[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-instrument-error-tracking":3,"mdc--dgorre-key":38,"related-repo-posthog-instrument-error-tracking":748,"related-org-posthog-instrument-error-tracking":868},{"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":33,"sourceUrl":36,"mdContent":37},"instrument-error-tracking","instrument applications with PostHog error tracking","Add PostHog error tracking to capture and monitor exceptions. Use after implementing features or reviewing PRs to ensure errors are tracked with stack traces and source maps. Also handles initial PostHog SDK setup if not yet installed.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"posthog","PostHog","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fposthog.png",[12,16,17,20],{"name":13,"slug":14,"type":15},"Observability","observability","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"Integrations","integrations",{"name":21,"slug":22,"type":15},"Debugging","debugging",59,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fai-plugin","2026-07-28T05:33:42.496857",null,11,[29,30,31,32],"claude-code-plugin","codex-plugin","cursor-plugin","gemini-cli-extension",{"repoUrl":24,"stars":23,"forks":27,"topics":34,"description":35},[29,30,31,32],"Official PostHog plugin for Claude Code, Cursor, Gemini, Codex and other AI coding tools","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fai-plugin\u002Ftree\u002FHEAD\u002Fskills\u002Finstrument-error-tracking","---\nname: instrument-error-tracking\ndescription: >-\n  Add PostHog error tracking to capture and monitor exceptions. Use after\n  implementing features or reviewing PRs to ensure errors are tracked with stack\n  traces and source maps. Also handles initial PostHog SDK setup if not yet\n  installed.\nmetadata:\n  author: PostHog\n---\n\n# Add PostHog error tracking\n\nUse this skill to add PostHog error tracking that captures and monitors exceptions in your application. Use it after implementing features or reviewing PRs to ensure errors are tracked with full stack traces and source maps. If PostHog is not yet installed, this skill also covers initial SDK setup. Supports any platform or language.\n\nSupported platforms: React, Next.js, Web (JavaScript), Node.js, Python, PHP, Ruby, Ruby on Rails, Go, Elixir, Angular, Svelte, Nuxt, React Native, Flutter, iOS, Android, and Hono.\n\n## Instructions\n\nFollow these steps IN ORDER:\n\nSTEP 1: Analyze the codebase and detect the platform.\n  -\n Look for dependency files (package.json, pubspec.yaml, Podfile, Package.swift, requirements.txt, go.mod, Gemfile, composer.json, mix.exs, etc.) to determine the language and framework.\n  -\n Look for lockfiles (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb, go.sum, pubspec.lock, Podfile.lock, Package.resolved, mix.lock) to determine the package manager.\n  - Check for existing PostHog setup (SDK initialization, env vars, etc.). If PostHog is already installed and initialized, skip to STEP 4.\n\nSTEP 2: Research instrumentation. (Skip if PostHog is already set up.)\n  2.1. Find the reference file below that matches the detected platform — it is the source of truth for SDK initialization, exception autocapture, and framework-specific error tracking patterns. Read it now.\n  2.2. If no reference matches, fall back to your general knowledge and web search. Use posthog.com\u002Fdocs as the primary search source.\n\nSTEP 3: Install and initialize the PostHog SDK. (Skip if PostHog is already set up.)\n  - Add the PostHog SDK package for the detected platform. Do not manually edit package.json — use the package manager's install command.\n  - Follow the framework reference for where and how to initialize.\n\nSTEP 4: Enable exception autocapture.\n  - Follow the platform reference to enable exception autocapture. This automatically captures unhandled exceptions without additional code.\n\nSTEP 5: Add manual error captures.\n  - Identify error boundaries, catch blocks, and critical user flows where errors should be explicitly captured.\n  - Add `posthog.captureException()` or the platform-equivalent at these locations.\n  - Do not alter the fundamental architecture of existing error handling. Make additions minimal and targeted.\n  - You must read a file immediately before attempting to write it.\n\nSTEP 6: Upload source maps (frontend\u002Fmobile only).\n  - Configure source map uploads so stack traces resolve to original source code, not minified bundles.\n  - Follow the platform-specific reference for upload configuration (build plugins, CI scripts, etc.).\n\nSTEP 7: Set up environment variables.\n  - Check if the project already has PostHog environment variables configured (e.g. in `.env`, `.env.local`, or framework-specific env files). If valid values already exist, skip this step.\n  - If the PostHog project token is missing, use the PostHog MCP server's `projects-get` tool to retrieve the project's `api_token`. If multiple projects are returned, ask the user which project to use. If the MCP server is not connected or not authenticated, ask the user for their PostHog project token instead.\n  - For the PostHog host URL: check the `projects-get` MCP response for a `region` field — `US` maps to `https:\u002F\u002Fus.i.posthog.com`, `EU` maps to `https:\u002F\u002Feu.i.posthog.com`. If the region is not available from the MCP response or from existing project configuration, ask the user: \"Are you on PostHog US Cloud or EU Cloud?\" Do not assume US Cloud.\n  - Write these values to the appropriate env file using the framework's naming convention.\n  - Reference these environment variables in code instead of hardcoding them.\n\nSTEP 8: Verify and clean up.\n  - Check the project for errors. Look for type checking or build scripts in package.json.\n  - Ensure any components created were actually used.\n  - Run any linter or prettier-like scripts found in the package.json, but ONLY on the files you have edited or created during this session. Never run formatting or linting across the entire project's codebase.\n\n## Reference files\n\n- `references\u002Freact.md` - React error tracking installation - docs\n- `references\u002Fweb.md` - Web error tracking installation - docs\n- `references\u002Fnextjs.md` - Next.js error tracking installation - docs\n- `references\u002Fnode.md` - Node.js error tracking installation - docs\n- `references\u002Fpython.md` - Python error tracking installation - docs\n- `references\u002Fdjango.md` - Django - docs\n- `references\u002Fflask.md` - Flask - docs\n- `references\u002Fphp.md` - Php error tracking installation - docs\n- `references\u002Flaravel.md` - Laravel - docs\n- `references\u002Fruby.md` - Ruby error tracking installation - docs\n- `references\u002Fruby-on-rails.md` - Ruby on rails error tracking installation - docs\n- `references\u002Fruby-on-rails.md` - Ruby on rails - docs\n- `references\u002Fgo.md` - Go error tracking installation - docs\n- `references\u002Fdotnet.md` - .net error tracking installation - docs\n- `references\u002Fdotnet.md` - .net - docs\n- `references\u002Felixir.md` - Elixir error tracking installation - docs\n- `references\u002Fangular.md` - Angular error tracking installation - docs\n- `references\u002Fsvelte.md` - Sveltekit error tracking installation - docs\n- `references\u002Fnuxt-3-7.md` - Nuxt error tracking installation (v3.7 and above) - docs\n- `references\u002Fnuxt-3-6.md` - Nuxt error tracking installation (v3.6 and below) - docs\n- `references\u002Freact-native.md` - React native error tracking installation - docs\n- `references\u002Fflutter.md` - Flutter error tracking installation - docs\n- `references\u002Fios.md` - Ios error tracking installation - docs\n- `references\u002Fandroid.md` - Android error tracking installation - docs\n- `references\u002Fhono.md` - Hono error tracking installation - docs\n- `references\u002Ffingerprints.md` - Fingerprints - docs\n- `references\u002Falerts.md` - Send error tracking alerts - docs\n- `references\u002Fmonitoring.md` - Monitor and search issues - docs\n- `references\u002Fassigning-issues.md` - Assign issues to teammates - docs\n- `references\u002Fupload-source-maps.md` - Upload source maps - docs\n- `references\u002FCOMMANDMENTS.md` - Framework-specific rules the integration must follow\n\nEach platform reference contains SDK-specific installation and manual capture patterns. Find the one matching the user's stack.\n\n## Key principles\n\n- **Environment variables**: Always use environment variables for PostHog keys. Never hardcode them.\n- **Minimal changes**: Add error tracking alongside existing error handling. Don't replace or restructure existing code.\n- **Autocapture first**: Enable exception autocapture before adding manual captures.\n- **Source maps**: Upload source maps so stack traces resolve to original source code, not minified bundles.\n- **Manual capture for boundaries**: Use `captureException()` at error boundaries and catch blocks for errors that don't propagate to the global handler.\n",{"data":39,"body":41},{"name":4,"description":6,"metadata":40},{"author":9},{"type":42,"children":43},"root",[44,53,59,64,71,76,82,88,93,103,108,113,126,131,139,144,176,181,194,199,304,309,327,333,675,680,686],{"type":45,"tag":46,"props":47,"children":49},"element","h1",{"id":48},"add-posthog-error-tracking",[50],{"type":51,"value":52},"text","Add PostHog error tracking",{"type":45,"tag":54,"props":55,"children":56},"p",{},[57],{"type":51,"value":58},"Use this skill to add PostHog error tracking that captures and monitors exceptions in your application. Use it after implementing features or reviewing PRs to ensure errors are tracked with full stack traces and source maps. If PostHog is not yet installed, this skill also covers initial SDK setup. Supports any platform or language.",{"type":45,"tag":54,"props":60,"children":61},{},[62],{"type":51,"value":63},"Supported platforms: React, Next.js, Web (JavaScript), Node.js, Python, PHP, Ruby, Ruby on Rails, Go, Elixir, Angular, Svelte, Nuxt, React Native, Flutter, iOS, Android, and Hono.",{"type":45,"tag":65,"props":66,"children":68},"h2",{"id":67},"instructions",[69],{"type":51,"value":70},"Instructions",{"type":45,"tag":54,"props":72,"children":73},{},[74],{"type":51,"value":75},"Follow these steps IN ORDER:",{"type":45,"tag":65,"props":77,"children":79},{"id":78},"step-1-analyze-the-codebase-and-detect-the-platform",[80],{"type":51,"value":81},"STEP 1: Analyze the codebase and detect the platform.",{"type":45,"tag":65,"props":83,"children":85},{"id":84},"look-for-dependency-files-packagejson-pubspecyaml-podfile-packageswift-requirementstxt-gomod-gemfile-composerjson-mixexs-etc-to-determine-the-language-and-framework",[86],{"type":51,"value":87},"Look for dependency files (package.json, pubspec.yaml, Podfile, Package.swift, requirements.txt, go.mod, Gemfile, composer.json, mix.exs, etc.) to determine the language and framework.",{"type":45,"tag":54,"props":89,"children":90},{},[91],{"type":51,"value":92},"Look for lockfiles (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb, go.sum, pubspec.lock, Podfile.lock, Package.resolved, mix.lock) to determine the package manager.",{"type":45,"tag":94,"props":95,"children":96},"ul",{},[97],{"type":45,"tag":98,"props":99,"children":100},"li",{},[101],{"type":51,"value":102},"Check for existing PostHog setup (SDK initialization, env vars, etc.). If PostHog is already installed and initialized, skip to STEP 4.",{"type":45,"tag":54,"props":104,"children":105},{},[106],{"type":51,"value":107},"STEP 2: Research instrumentation. (Skip if PostHog is already set up.)\n2.1. Find the reference file below that matches the detected platform — it is the source of truth for SDK initialization, exception autocapture, and framework-specific error tracking patterns. Read it now.\n2.2. If no reference matches, fall back to your general knowledge and web search. Use posthog.com\u002Fdocs as the primary search source.",{"type":45,"tag":54,"props":109,"children":110},{},[111],{"type":51,"value":112},"STEP 3: Install and initialize the PostHog SDK. (Skip if PostHog is already set up.)",{"type":45,"tag":94,"props":114,"children":115},{},[116,121],{"type":45,"tag":98,"props":117,"children":118},{},[119],{"type":51,"value":120},"Add the PostHog SDK package for the detected platform. Do not manually edit package.json — use the package manager's install command.",{"type":45,"tag":98,"props":122,"children":123},{},[124],{"type":51,"value":125},"Follow the framework reference for where and how to initialize.",{"type":45,"tag":54,"props":127,"children":128},{},[129],{"type":51,"value":130},"STEP 4: Enable exception autocapture.",{"type":45,"tag":94,"props":132,"children":133},{},[134],{"type":45,"tag":98,"props":135,"children":136},{},[137],{"type":51,"value":138},"Follow the platform reference to enable exception autocapture. This automatically captures unhandled exceptions without additional code.",{"type":45,"tag":54,"props":140,"children":141},{},[142],{"type":51,"value":143},"STEP 5: Add manual error captures.",{"type":45,"tag":94,"props":145,"children":146},{},[147,152,166,171],{"type":45,"tag":98,"props":148,"children":149},{},[150],{"type":51,"value":151},"Identify error boundaries, catch blocks, and critical user flows where errors should be explicitly captured.",{"type":45,"tag":98,"props":153,"children":154},{},[155,157,164],{"type":51,"value":156},"Add ",{"type":45,"tag":158,"props":159,"children":161},"code",{"className":160},[],[162],{"type":51,"value":163},"posthog.captureException()",{"type":51,"value":165}," or the platform-equivalent at these locations.",{"type":45,"tag":98,"props":167,"children":168},{},[169],{"type":51,"value":170},"Do not alter the fundamental architecture of existing error handling. Make additions minimal and targeted.",{"type":45,"tag":98,"props":172,"children":173},{},[174],{"type":51,"value":175},"You must read a file immediately before attempting to write it.",{"type":45,"tag":54,"props":177,"children":178},{},[179],{"type":51,"value":180},"STEP 6: Upload source maps (frontend\u002Fmobile only).",{"type":45,"tag":94,"props":182,"children":183},{},[184,189],{"type":45,"tag":98,"props":185,"children":186},{},[187],{"type":51,"value":188},"Configure source map uploads so stack traces resolve to original source code, not minified bundles.",{"type":45,"tag":98,"props":190,"children":191},{},[192],{"type":51,"value":193},"Follow the platform-specific reference for upload configuration (build plugins, CI scripts, etc.).",{"type":45,"tag":54,"props":195,"children":196},{},[197],{"type":51,"value":198},"STEP 7: Set up environment variables.",{"type":45,"tag":94,"props":200,"children":201},{},[202,223,244,294,299],{"type":45,"tag":98,"props":203,"children":204},{},[205,207,213,215,221],{"type":51,"value":206},"Check if the project already has PostHog environment variables configured (e.g. in ",{"type":45,"tag":158,"props":208,"children":210},{"className":209},[],[211],{"type":51,"value":212},".env",{"type":51,"value":214},", ",{"type":45,"tag":158,"props":216,"children":218},{"className":217},[],[219],{"type":51,"value":220},".env.local",{"type":51,"value":222},", or framework-specific env files). If valid values already exist, skip this step.",{"type":45,"tag":98,"props":224,"children":225},{},[226,228,234,236,242],{"type":51,"value":227},"If the PostHog project token is missing, use the PostHog MCP server's ",{"type":45,"tag":158,"props":229,"children":231},{"className":230},[],[232],{"type":51,"value":233},"projects-get",{"type":51,"value":235}," tool to retrieve the project's ",{"type":45,"tag":158,"props":237,"children":239},{"className":238},[],[240],{"type":51,"value":241},"api_token",{"type":51,"value":243},". If multiple projects are returned, ask the user which project to use. If the MCP server is not connected or not authenticated, ask the user for their PostHog project token instead.",{"type":45,"tag":98,"props":245,"children":246},{},[247,249,254,256,262,264,270,272,278,279,285,286,292],{"type":51,"value":248},"For the PostHog host URL: check the ",{"type":45,"tag":158,"props":250,"children":252},{"className":251},[],[253],{"type":51,"value":233},{"type":51,"value":255}," MCP response for a ",{"type":45,"tag":158,"props":257,"children":259},{"className":258},[],[260],{"type":51,"value":261},"region",{"type":51,"value":263}," field — ",{"type":45,"tag":158,"props":265,"children":267},{"className":266},[],[268],{"type":51,"value":269},"US",{"type":51,"value":271}," maps to ",{"type":45,"tag":158,"props":273,"children":275},{"className":274},[],[276],{"type":51,"value":277},"https:\u002F\u002Fus.i.posthog.com",{"type":51,"value":214},{"type":45,"tag":158,"props":280,"children":282},{"className":281},[],[283],{"type":51,"value":284},"EU",{"type":51,"value":271},{"type":45,"tag":158,"props":287,"children":289},{"className":288},[],[290],{"type":51,"value":291},"https:\u002F\u002Feu.i.posthog.com",{"type":51,"value":293},". If the region is not available from the MCP response or from existing project configuration, ask the user: \"Are you on PostHog US Cloud or EU Cloud?\" Do not assume US Cloud.",{"type":45,"tag":98,"props":295,"children":296},{},[297],{"type":51,"value":298},"Write these values to the appropriate env file using the framework's naming convention.",{"type":45,"tag":98,"props":300,"children":301},{},[302],{"type":51,"value":303},"Reference these environment variables in code instead of hardcoding them.",{"type":45,"tag":54,"props":305,"children":306},{},[307],{"type":51,"value":308},"STEP 8: Verify and clean up.",{"type":45,"tag":94,"props":310,"children":311},{},[312,317,322],{"type":45,"tag":98,"props":313,"children":314},{},[315],{"type":51,"value":316},"Check the project for errors. Look for type checking or build scripts in package.json.",{"type":45,"tag":98,"props":318,"children":319},{},[320],{"type":51,"value":321},"Ensure any components created were actually used.",{"type":45,"tag":98,"props":323,"children":324},{},[325],{"type":51,"value":326},"Run any linter or prettier-like scripts found in the package.json, but ONLY on the files you have edited or created during this session. Never run formatting or linting across the entire project's codebase.",{"type":45,"tag":65,"props":328,"children":330},{"id":329},"reference-files",[331],{"type":51,"value":332},"Reference files",{"type":45,"tag":94,"props":334,"children":335},{},[336,347,358,369,380,391,402,413,424,435,446,457,467,478,489,499,510,521,532,543,554,565,576,587,598,609,620,631,642,653,664],{"type":45,"tag":98,"props":337,"children":338},{},[339,345],{"type":45,"tag":158,"props":340,"children":342},{"className":341},[],[343],{"type":51,"value":344},"references\u002Freact.md",{"type":51,"value":346}," - React error tracking installation - docs",{"type":45,"tag":98,"props":348,"children":349},{},[350,356],{"type":45,"tag":158,"props":351,"children":353},{"className":352},[],[354],{"type":51,"value":355},"references\u002Fweb.md",{"type":51,"value":357}," - Web error tracking installation - docs",{"type":45,"tag":98,"props":359,"children":360},{},[361,367],{"type":45,"tag":158,"props":362,"children":364},{"className":363},[],[365],{"type":51,"value":366},"references\u002Fnextjs.md",{"type":51,"value":368}," - Next.js error tracking installation - docs",{"type":45,"tag":98,"props":370,"children":371},{},[372,378],{"type":45,"tag":158,"props":373,"children":375},{"className":374},[],[376],{"type":51,"value":377},"references\u002Fnode.md",{"type":51,"value":379}," - Node.js error tracking installation - docs",{"type":45,"tag":98,"props":381,"children":382},{},[383,389],{"type":45,"tag":158,"props":384,"children":386},{"className":385},[],[387],{"type":51,"value":388},"references\u002Fpython.md",{"type":51,"value":390}," - Python error tracking installation - docs",{"type":45,"tag":98,"props":392,"children":393},{},[394,400],{"type":45,"tag":158,"props":395,"children":397},{"className":396},[],[398],{"type":51,"value":399},"references\u002Fdjango.md",{"type":51,"value":401}," - Django - docs",{"type":45,"tag":98,"props":403,"children":404},{},[405,411],{"type":45,"tag":158,"props":406,"children":408},{"className":407},[],[409],{"type":51,"value":410},"references\u002Fflask.md",{"type":51,"value":412}," - Flask - docs",{"type":45,"tag":98,"props":414,"children":415},{},[416,422],{"type":45,"tag":158,"props":417,"children":419},{"className":418},[],[420],{"type":51,"value":421},"references\u002Fphp.md",{"type":51,"value":423}," - Php error tracking installation - docs",{"type":45,"tag":98,"props":425,"children":426},{},[427,433],{"type":45,"tag":158,"props":428,"children":430},{"className":429},[],[431],{"type":51,"value":432},"references\u002Flaravel.md",{"type":51,"value":434}," - Laravel - docs",{"type":45,"tag":98,"props":436,"children":437},{},[438,444],{"type":45,"tag":158,"props":439,"children":441},{"className":440},[],[442],{"type":51,"value":443},"references\u002Fruby.md",{"type":51,"value":445}," - Ruby error tracking installation - docs",{"type":45,"tag":98,"props":447,"children":448},{},[449,455],{"type":45,"tag":158,"props":450,"children":452},{"className":451},[],[453],{"type":51,"value":454},"references\u002Fruby-on-rails.md",{"type":51,"value":456}," - Ruby on rails error tracking installation - docs",{"type":45,"tag":98,"props":458,"children":459},{},[460,465],{"type":45,"tag":158,"props":461,"children":463},{"className":462},[],[464],{"type":51,"value":454},{"type":51,"value":466}," - Ruby on rails - docs",{"type":45,"tag":98,"props":468,"children":469},{},[470,476],{"type":45,"tag":158,"props":471,"children":473},{"className":472},[],[474],{"type":51,"value":475},"references\u002Fgo.md",{"type":51,"value":477}," - Go error tracking installation - docs",{"type":45,"tag":98,"props":479,"children":480},{},[481,487],{"type":45,"tag":158,"props":482,"children":484},{"className":483},[],[485],{"type":51,"value":486},"references\u002Fdotnet.md",{"type":51,"value":488}," - .net error tracking installation - docs",{"type":45,"tag":98,"props":490,"children":491},{},[492,497],{"type":45,"tag":158,"props":493,"children":495},{"className":494},[],[496],{"type":51,"value":486},{"type":51,"value":498}," - .net - docs",{"type":45,"tag":98,"props":500,"children":501},{},[502,508],{"type":45,"tag":158,"props":503,"children":505},{"className":504},[],[506],{"type":51,"value":507},"references\u002Felixir.md",{"type":51,"value":509}," - Elixir error tracking installation - docs",{"type":45,"tag":98,"props":511,"children":512},{},[513,519],{"type":45,"tag":158,"props":514,"children":516},{"className":515},[],[517],{"type":51,"value":518},"references\u002Fangular.md",{"type":51,"value":520}," - Angular error tracking installation - docs",{"type":45,"tag":98,"props":522,"children":523},{},[524,530],{"type":45,"tag":158,"props":525,"children":527},{"className":526},[],[528],{"type":51,"value":529},"references\u002Fsvelte.md",{"type":51,"value":531}," - Sveltekit error tracking installation - docs",{"type":45,"tag":98,"props":533,"children":534},{},[535,541],{"type":45,"tag":158,"props":536,"children":538},{"className":537},[],[539],{"type":51,"value":540},"references\u002Fnuxt-3-7.md",{"type":51,"value":542}," - Nuxt error tracking installation (v3.7 and above) - docs",{"type":45,"tag":98,"props":544,"children":545},{},[546,552],{"type":45,"tag":158,"props":547,"children":549},{"className":548},[],[550],{"type":51,"value":551},"references\u002Fnuxt-3-6.md",{"type":51,"value":553}," - Nuxt error tracking installation (v3.6 and below) - docs",{"type":45,"tag":98,"props":555,"children":556},{},[557,563],{"type":45,"tag":158,"props":558,"children":560},{"className":559},[],[561],{"type":51,"value":562},"references\u002Freact-native.md",{"type":51,"value":564}," - React native error tracking installation - docs",{"type":45,"tag":98,"props":566,"children":567},{},[568,574],{"type":45,"tag":158,"props":569,"children":571},{"className":570},[],[572],{"type":51,"value":573},"references\u002Fflutter.md",{"type":51,"value":575}," - Flutter error tracking installation - docs",{"type":45,"tag":98,"props":577,"children":578},{},[579,585],{"type":45,"tag":158,"props":580,"children":582},{"className":581},[],[583],{"type":51,"value":584},"references\u002Fios.md",{"type":51,"value":586}," - Ios error tracking installation - docs",{"type":45,"tag":98,"props":588,"children":589},{},[590,596],{"type":45,"tag":158,"props":591,"children":593},{"className":592},[],[594],{"type":51,"value":595},"references\u002Fandroid.md",{"type":51,"value":597}," - Android error tracking installation - docs",{"type":45,"tag":98,"props":599,"children":600},{},[601,607],{"type":45,"tag":158,"props":602,"children":604},{"className":603},[],[605],{"type":51,"value":606},"references\u002Fhono.md",{"type":51,"value":608}," - Hono error tracking installation - docs",{"type":45,"tag":98,"props":610,"children":611},{},[612,618],{"type":45,"tag":158,"props":613,"children":615},{"className":614},[],[616],{"type":51,"value":617},"references\u002Ffingerprints.md",{"type":51,"value":619}," - Fingerprints - docs",{"type":45,"tag":98,"props":621,"children":622},{},[623,629],{"type":45,"tag":158,"props":624,"children":626},{"className":625},[],[627],{"type":51,"value":628},"references\u002Falerts.md",{"type":51,"value":630}," - Send error tracking alerts - docs",{"type":45,"tag":98,"props":632,"children":633},{},[634,640],{"type":45,"tag":158,"props":635,"children":637},{"className":636},[],[638],{"type":51,"value":639},"references\u002Fmonitoring.md",{"type":51,"value":641}," - Monitor and search issues - docs",{"type":45,"tag":98,"props":643,"children":644},{},[645,651],{"type":45,"tag":158,"props":646,"children":648},{"className":647},[],[649],{"type":51,"value":650},"references\u002Fassigning-issues.md",{"type":51,"value":652}," - Assign issues to teammates - docs",{"type":45,"tag":98,"props":654,"children":655},{},[656,662],{"type":45,"tag":158,"props":657,"children":659},{"className":658},[],[660],{"type":51,"value":661},"references\u002Fupload-source-maps.md",{"type":51,"value":663}," - Upload source maps - docs",{"type":45,"tag":98,"props":665,"children":666},{},[667,673],{"type":45,"tag":158,"props":668,"children":670},{"className":669},[],[671],{"type":51,"value":672},"references\u002FCOMMANDMENTS.md",{"type":51,"value":674}," - Framework-specific rules the integration must follow",{"type":45,"tag":54,"props":676,"children":677},{},[678],{"type":51,"value":679},"Each platform reference contains SDK-specific installation and manual capture patterns. Find the one matching the user's stack.",{"type":45,"tag":65,"props":681,"children":683},{"id":682},"key-principles",[684],{"type":51,"value":685},"Key principles",{"type":45,"tag":94,"props":687,"children":688},{},[689,700,710,720,730],{"type":45,"tag":98,"props":690,"children":691},{},[692,698],{"type":45,"tag":693,"props":694,"children":695},"strong",{},[696],{"type":51,"value":697},"Environment variables",{"type":51,"value":699},": Always use environment variables for PostHog keys. Never hardcode them.",{"type":45,"tag":98,"props":701,"children":702},{},[703,708],{"type":45,"tag":693,"props":704,"children":705},{},[706],{"type":51,"value":707},"Minimal changes",{"type":51,"value":709},": Add error tracking alongside existing error handling. Don't replace or restructure existing code.",{"type":45,"tag":98,"props":711,"children":712},{},[713,718],{"type":45,"tag":693,"props":714,"children":715},{},[716],{"type":51,"value":717},"Autocapture first",{"type":51,"value":719},": Enable exception autocapture before adding manual captures.",{"type":45,"tag":98,"props":721,"children":722},{},[723,728],{"type":45,"tag":693,"props":724,"children":725},{},[726],{"type":51,"value":727},"Source maps",{"type":51,"value":729},": Upload source maps so stack traces resolve to original source code, not minified bundles.",{"type":45,"tag":98,"props":731,"children":732},{},[733,738,740,746],{"type":45,"tag":693,"props":734,"children":735},{},[736],{"type":51,"value":737},"Manual capture for boundaries",{"type":51,"value":739},": Use ",{"type":45,"tag":158,"props":741,"children":743},{"className":742},[],[744],{"type":51,"value":745},"captureException()",{"type":51,"value":747}," at error boundaries and catch blocks for errors that don't propagate to the global handler.",{"items":749,"total":867},[750,767,785,802,817,831,849],{"slug":751,"name":751,"fn":752,"description":753,"org":754,"tags":755,"stars":23,"repoUrl":24,"updatedAt":766},"analyzing-experiment-session-replays","analyze session replays for PostHog experiments","Analyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with different experiment variants, identify usability issues, compare behavior patterns between control and test groups, or get qualitative insights to complement quantitative experiment results.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[756,759,762,763],{"name":757,"slug":758,"type":15},"Analytics","analytics",{"name":760,"slug":761,"type":15},"Design","design",{"name":9,"slug":8,"type":15},{"name":764,"slug":765,"type":15},"User Research","user-research","2026-04-06T18:44:38.291781",{"slug":768,"name":768,"fn":769,"description":770,"org":771,"tags":772,"stars":23,"repoUrl":24,"updatedAt":784},"assessing-heatmaps","analyze page heatmaps and suggest improvements","Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click \u002F rageclick \u002F scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements.\nTRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap\u002Fclick data, or to 'analyze\u002Fassess\u002Freview the heatmap' for a URL.\nDO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[773,774,777,778,781],{"name":757,"slug":758,"type":15},{"name":775,"slug":776,"type":15},"Frontend","frontend",{"name":9,"slug":8,"type":15},{"name":779,"slug":780,"type":15},"Product Management","product-management",{"name":782,"slug":783,"type":15},"UX Design","ux-design","2026-06-05T07:40:43.37798",{"slug":786,"name":786,"fn":787,"description":788,"org":789,"tags":790,"stars":23,"repoUrl":24,"updatedAt":801},"auditing-experiments-flags","audit PostHog experiments and feature flags","Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[791,794,797,798],{"name":792,"slug":793,"type":15},"Audit","audit",{"name":795,"slug":796,"type":15},"Feature Flags","feature-flags",{"name":9,"slug":8,"type":15},{"name":799,"slug":800,"type":15},"QA","qa","2026-04-06T18:44:30.657553",{"slug":803,"name":803,"fn":804,"description":805,"org":806,"tags":807,"stars":23,"repoUrl":24,"updatedAt":816},"authoring-scouts","author and edit PostHog Signals scouts","How to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak a scout's schedule or dry-run posture, or write a brand-new scout from scratch for a specific use case (a custom event, a product surface no canonical scout covers), or steer a scout without editing it at all by leaving it a note. Covers the scout SKILL.md anatomy, the report contract, the dedupe + scratchpad-memory conventions, the scout-notes steering channel, the per-team skills-store path vs the canonical in-repo path, and the write-and-inspect test loop (with dry-run as an optional safety net). Trigger on \"write\u002Fedit\u002Fcustomize a signals scout\", \"new scout for X\", \"tune my scout schedule\", \"make a scout that watches \u003Cevent>\", \"leave a note for \u002F give feedback to a scout\", \"tell the scouts about X\".\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[808,811,814,815],{"name":809,"slug":810,"type":15},"Agents","agents",{"name":812,"slug":813,"type":15},"Automation","automation",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-07-28T05:33:45.509154",{"slug":818,"name":818,"fn":819,"description":820,"org":821,"tags":822,"stars":23,"repoUrl":24,"updatedAt":830},"building-a-dashboard","build and update PostHog dashboards","Build a new dashboard, or update an existing one, from a set of insights — the same job the in-app assistant does with its upsert-dashboard tool, but over MCP. Use when a user asks to create a dashboard, put several metrics\u002Fcharts together on one page, assemble a dashboard for a topic (product analytics, retention, revenue, activation, etc.), or add\u002Fremove\u002Freplace insights on a dashboard they already have. Covers deciding create vs update, reusing existing insights vs creating new ones, and using PostHog's vetted dashboard templates as reference for what a strong dashboard on a topic looks like.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[823,824,827],{"name":757,"slug":758,"type":15},{"name":825,"slug":826,"type":15},"Dashboards","dashboards",{"name":828,"slug":829,"type":15},"MCP","mcp","2026-07-21T06:07:38.060598",{"slug":832,"name":832,"fn":833,"description":834,"org":835,"tags":836,"stars":23,"repoUrl":24,"updatedAt":848},"checking-deploy-timing","correlate PostHog deployments with GitHub commits","Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask \"when was X deployed\", \"is my change live in the US\u002FEU yet\", \"has my PR shipped\", \"did the fix roll out to prod-us\", or otherwise want to know whether\u002Fwhen a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event\u002Fdata volume alone — that only shows when data changed, not when code shipped.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[837,840,843,846,847],{"name":838,"slug":839,"type":15},"Deployment","deployment",{"name":841,"slug":842,"type":15},"Git","git",{"name":844,"slug":845,"type":15},"GitHub","github",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-28T07:46:59.53536",{"slug":850,"name":850,"fn":851,"description":852,"org":853,"tags":854,"stars":23,"repoUrl":24,"updatedAt":866},"choosing-trend-or-slope-view","visualize trends and growth over time","Clarify how to visualize change over a time range before building a trend. Use whenever the user asks how much something changed, grew, dropped, improved, or regressed between two points or periods — \"how much did X change from A to B\", \"before vs after\", \"start vs end\", \"week over week\", \"compare this month to last\", \"change over time\" — or mentions a \"slope chart\" \u002F \"slopegraph\". Two readings of \"change\" need different charts: the whole trend (a line, every interval) versus just the two endpoints (a slope, start vs end). Ask which they want, then render it. Not for choosing a saved insight ChartDisplayType in the insight editor.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[855,856,859,862,863],{"name":757,"slug":758,"type":15},{"name":857,"slug":858,"type":15},"Charts","charts",{"name":860,"slug":861,"type":15},"Data Visualization","data-visualization",{"name":9,"slug":8,"type":15},{"name":864,"slug":865,"type":15},"Reporting","reporting","2026-06-18T08:18:57.960157",56,{"items":869,"total":1026},[870,885,895,908,921,934,950,963,975,990,1000,1016],{"slug":871,"name":871,"fn":872,"description":873,"org":874,"tags":875,"stars":882,"repoUrl":883,"updatedAt":884},"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},[876,877,880,881],{"name":757,"slug":758,"type":15},{"name":878,"slug":879,"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":886,"name":886,"fn":887,"description":888,"org":889,"tags":890,"stars":882,"repoUrl":883,"updatedAt":894},"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},[891,892,893],{"name":757,"slug":758,"type":15},{"name":792,"slug":793,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:33.693989",{"slug":896,"name":896,"fn":897,"description":898,"org":899,"tags":900,"stars":882,"repoUrl":883,"updatedAt":907},"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},[901,902,905,906],{"name":792,"slug":793,"type":15},{"name":903,"slug":904,"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":909,"name":909,"fn":910,"description":911,"org":912,"tags":913,"stars":882,"repoUrl":883,"updatedAt":920},"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},[914,915,916,919],{"name":792,"slug":793,"type":15},{"name":903,"slug":904,"type":15},{"name":917,"slug":918,"type":15},"Performance","performance",{"name":9,"slug":8,"type":15},"2026-06-18T08:25:10.936787",{"slug":922,"name":922,"fn":923,"description":924,"org":925,"tags":926,"stars":882,"repoUrl":883,"updatedAt":933},"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},[927,930,931,932],{"name":928,"slug":929,"type":15},"Alerting","alerting",{"name":21,"slug":22,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:24:40.318583",{"slug":935,"name":935,"fn":936,"description":937,"org":938,"tags":939,"stars":882,"repoUrl":883,"updatedAt":949},"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},[940,941,944,945,948],{"name":757,"slug":758,"type":15},{"name":942,"slug":943,"type":15},"Monitoring","monitoring",{"name":13,"slug":14,"type":15},{"name":946,"slug":947,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-07-18T05:10:54.430898",{"slug":951,"name":951,"fn":952,"description":953,"org":954,"tags":955,"stars":882,"repoUrl":883,"updatedAt":962},"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},[956,957,958,959],{"name":812,"slug":813,"type":15},{"name":828,"slug":829,"type":15},{"name":9,"slug":8,"type":15},{"name":960,"slug":961,"type":15},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",{"slug":964,"name":964,"fn":965,"description":966,"org":967,"tags":968,"stars":882,"repoUrl":883,"updatedAt":974},"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},[969,970,971,972,973],{"name":757,"slug":758,"type":15},{"name":21,"slug":22,"type":15},{"name":775,"slug":776,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-05-07T05:56:19.828048",{"slug":976,"name":976,"fn":977,"description":978,"org":979,"tags":980,"stars":882,"repoUrl":883,"updatedAt":989},"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},[981,984,985,986],{"name":982,"slug":983,"type":15},"API Development","api-development",{"name":775,"slug":776,"type":15},{"name":9,"slug":8,"type":15},{"name":987,"slug":988,"type":15},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":991,"name":991,"fn":992,"description":993,"org":994,"tags":995,"stars":882,"repoUrl":883,"updatedAt":999},"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},[996,997,998],{"name":982,"slug":983,"type":15},{"name":946,"slug":947,"type":15},{"name":9,"slug":8,"type":15},"2026-07-15T05:29:58.442727",{"slug":1001,"name":1001,"fn":1002,"description":1003,"org":1004,"tags":1005,"stars":882,"repoUrl":883,"updatedAt":1015},"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},[1006,1007,1010,1011,1012],{"name":812,"slug":813,"type":15},{"name":1008,"slug":1009,"type":15},"Email","email",{"name":9,"slug":8,"type":15},{"name":864,"slug":865,"type":15},{"name":1013,"slug":1014,"type":15},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":1017,"name":1017,"fn":1018,"description":1019,"org":1020,"tags":1021,"stars":882,"repoUrl":883,"updatedAt":1025},"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},[1022,1023,1024],{"name":757,"slug":758,"type":15},{"name":982,"slug":983,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:29.624498",231]