[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-error-tracking-nextjs":3,"mdc--gqm0e0-key":40,"related-repo-posthog-error-tracking-nextjs":267,"related-org-posthog-error-tracking-nextjs":376},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":29,"repoUrl":30,"updatedAt":31,"license":32,"forks":33,"topics":34,"repo":35,"sourceUrl":38,"mdContent":39},"error-tracking-nextjs","track Next.js errors with PostHog","PostHog error tracking for Next.js",{"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,23,26],{"name":13,"slug":14,"type":15},"Observability","observability","tag",{"name":17,"slug":18,"type":15},"React","react",{"name":9,"slug":8,"type":15},{"name":21,"slug":22,"type":15},"Next.js","next-js",{"name":24,"slug":25,"type":15},"Frontend","frontend",{"name":27,"slug":28,"type":15},"Debugging","debugging",56,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills","2026-04-06T18:46:21.860109",null,4,[],{"repoUrl":30,"stars":29,"forks":33,"topics":36,"description":37},[],"PostHog skills (under construction)","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002Fposthog\u002Ferror-tracking\u002Fskills\u002Fnextjs","---\nname: error-tracking-nextjs\ndescription: PostHog error tracking for Next.js\nmetadata:\n  author: PostHog\n  version: 1.9.4\n---\n\n# PostHog error tracking for Next.js\n\nThis skill helps you add PostHog error tracking to Next.js applications.\n\n## Reference files\n\n- `references\u002Fnextjs.md` - Next.js 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\nConsult the documentation for API details and framework-specific patterns.\n\n## Key principles\n\n- **Environment variables**: Always use environment variables for PostHog keys and host URLs. Never hardcode them.\n- **Minimal changes**: Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.\n- **Autocapture first**: Enable exception autocapture in the SDK initialization 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\n## Framework guidelines\n\n- For Next.js 15.3+, initialize PostHog in instrumentation-client.ts for the simplest setup\n- For feature flags, use useFeatureFlagEnabled() or useFeatureFlagPayload() hooks - they handle loading states and external sync automatically\n- Add analytics capture in event handlers where user actions occur, NOT in useEffect reacting to state changes\n- Do NOT use useEffect for data transformation - calculate derived values during render instead\n- Do NOT use useEffect to respond to user events - put that logic in the event handler itself\n- Do NOT use useEffect to chain state updates - calculate all related updates together in the event handler\n- Do NOT use useEffect to notify parent components - call the parent callback alongside setState in the event handler\n- To reset component state when a prop changes, pass the prop as the component's key instead of using useEffect\n- useEffect is ONLY for synchronizing with external systems (non-React widgets, browser APIs, network subscriptions)\n",{"data":41,"body":44},{"name":4,"description":6,"metadata":42},{"author":9,"version":43},"1.9.4",{"type":45,"children":46},"root",[47,55,61,68,140,145,151,213,219],{"type":48,"tag":49,"props":50,"children":52},"element","h1",{"id":51},"posthog-error-tracking-for-nextjs",[53],{"type":54,"value":6},"text",{"type":48,"tag":56,"props":57,"children":58},"p",{},[59],{"type":54,"value":60},"This skill helps you add PostHog error tracking to Next.js applications.",{"type":48,"tag":62,"props":63,"children":65},"h2",{"id":64},"reference-files",[66],{"type":54,"value":67},"Reference files",{"type":48,"tag":69,"props":70,"children":71},"ul",{},[72,85,96,107,118,129],{"type":48,"tag":73,"props":74,"children":75},"li",{},[76,83],{"type":48,"tag":77,"props":78,"children":80},"code",{"className":79},[],[81],{"type":54,"value":82},"references\u002Fnextjs.md",{"type":54,"value":84}," - Next.js error tracking installation - docs",{"type":48,"tag":73,"props":86,"children":87},{},[88,94],{"type":48,"tag":77,"props":89,"children":91},{"className":90},[],[92],{"type":54,"value":93},"references\u002Ffingerprints.md",{"type":54,"value":95}," - Fingerprints - docs",{"type":48,"tag":73,"props":97,"children":98},{},[99,105],{"type":48,"tag":77,"props":100,"children":102},{"className":101},[],[103],{"type":54,"value":104},"references\u002Falerts.md",{"type":54,"value":106}," - Send error tracking alerts - docs",{"type":48,"tag":73,"props":108,"children":109},{},[110,116],{"type":48,"tag":77,"props":111,"children":113},{"className":112},[],[114],{"type":54,"value":115},"references\u002Fmonitoring.md",{"type":54,"value":117}," - Monitor and search issues - docs",{"type":48,"tag":73,"props":119,"children":120},{},[121,127],{"type":48,"tag":77,"props":122,"children":124},{"className":123},[],[125],{"type":54,"value":126},"references\u002Fassigning-issues.md",{"type":54,"value":128}," - Assign issues to teammates - docs",{"type":48,"tag":73,"props":130,"children":131},{},[132,138],{"type":48,"tag":77,"props":133,"children":135},{"className":134},[],[136],{"type":54,"value":137},"references\u002Fupload-source-maps.md",{"type":54,"value":139}," - Upload source maps - docs",{"type":48,"tag":56,"props":141,"children":142},{},[143],{"type":54,"value":144},"Consult the documentation for API details and framework-specific patterns.",{"type":48,"tag":62,"props":146,"children":148},{"id":147},"key-principles",[149],{"type":54,"value":150},"Key principles",{"type":48,"tag":69,"props":152,"children":153},{},[154,165,175,185,195],{"type":48,"tag":73,"props":155,"children":156},{},[157,163],{"type":48,"tag":158,"props":159,"children":160},"strong",{},[161],{"type":54,"value":162},"Environment variables",{"type":54,"value":164},": Always use environment variables for PostHog keys and host URLs. Never hardcode them.",{"type":48,"tag":73,"props":166,"children":167},{},[168,173],{"type":48,"tag":158,"props":169,"children":170},{},[171],{"type":54,"value":172},"Minimal changes",{"type":54,"value":174},": Add error tracking alongside existing error handling. Don't replace or restructure existing error handling code.",{"type":48,"tag":73,"props":176,"children":177},{},[178,183],{"type":48,"tag":158,"props":179,"children":180},{},[181],{"type":54,"value":182},"Autocapture first",{"type":54,"value":184},": Enable exception autocapture in the SDK initialization before adding manual captures.",{"type":48,"tag":73,"props":186,"children":187},{},[188,193],{"type":48,"tag":158,"props":189,"children":190},{},[191],{"type":54,"value":192},"Source maps",{"type":54,"value":194},": Upload source maps so stack traces resolve to original source code, not minified bundles.",{"type":48,"tag":73,"props":196,"children":197},{},[198,203,205,211],{"type":48,"tag":158,"props":199,"children":200},{},[201],{"type":54,"value":202},"Manual capture for boundaries",{"type":54,"value":204},": Use ",{"type":48,"tag":77,"props":206,"children":208},{"className":207},[],[209],{"type":54,"value":210},"captureException()",{"type":54,"value":212}," at error boundaries and catch blocks for errors that don't propagate to the global handler.",{"type":48,"tag":62,"props":214,"children":216},{"id":215},"framework-guidelines",[217],{"type":54,"value":218},"Framework guidelines",{"type":48,"tag":69,"props":220,"children":221},{},[222,227,232,237,242,247,252,257,262],{"type":48,"tag":73,"props":223,"children":224},{},[225],{"type":54,"value":226},"For Next.js 15.3+, initialize PostHog in instrumentation-client.ts for the simplest setup",{"type":48,"tag":73,"props":228,"children":229},{},[230],{"type":54,"value":231},"For feature flags, use useFeatureFlagEnabled() or useFeatureFlagPayload() hooks - they handle loading states and external sync automatically",{"type":48,"tag":73,"props":233,"children":234},{},[235],{"type":54,"value":236},"Add analytics capture in event handlers where user actions occur, NOT in useEffect reacting to state changes",{"type":48,"tag":73,"props":238,"children":239},{},[240],{"type":54,"value":241},"Do NOT use useEffect for data transformation - calculate derived values during render instead",{"type":48,"tag":73,"props":243,"children":244},{},[245],{"type":54,"value":246},"Do NOT use useEffect to respond to user events - put that logic in the event handler itself",{"type":48,"tag":73,"props":248,"children":249},{},[250],{"type":54,"value":251},"Do NOT use useEffect to chain state updates - calculate all related updates together in the event handler",{"type":48,"tag":73,"props":253,"children":254},{},[255],{"type":54,"value":256},"Do NOT use useEffect to notify parent components - call the parent callback alongside setState in the event handler",{"type":48,"tag":73,"props":258,"children":259},{},[260],{"type":54,"value":261},"To reset component state when a prop changes, pass the prop as the component's key instead of using useEffect",{"type":48,"tag":73,"props":263,"children":264},{},[265],{"type":54,"value":266},"useEffect is ONLY for synchronizing with external systems (non-React widgets, browser APIs, network subscriptions)",{"items":268,"total":375},[269,286,304,318,336,348,359],{"slug":270,"name":270,"fn":271,"description":272,"org":273,"tags":274,"stars":29,"repoUrl":30,"updatedAt":285},"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},[275,278,281,282],{"name":276,"slug":277,"type":15},"Communications","communications",{"name":279,"slug":280,"type":15},"CRM","crm",{"name":9,"slug":8,"type":15},{"name":283,"slug":284,"type":15},"Sales","sales","2026-04-16T05:13:00.172732",{"slug":287,"name":287,"fn":288,"description":289,"org":290,"tags":291,"stars":29,"repoUrl":30,"updatedAt":303},"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},[292,295,298,301,302],{"name":293,"slug":294,"type":15},"Audit","audit",{"name":296,"slug":297,"type":15},"Data Engineering","data-engineering",{"name":299,"slug":300,"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":305,"name":305,"fn":306,"description":307,"org":308,"tags":309,"stars":29,"repoUrl":30,"updatedAt":317},"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},[310,313,316],{"name":311,"slug":312,"type":15},"Deployment","deployment",{"name":314,"slug":315,"type":15},"Feature Flags","feature-flags",{"name":9,"slug":8,"type":15},"2026-05-04T05:56:44.484909",{"slug":319,"name":319,"fn":320,"description":321,"org":322,"tags":323,"stars":29,"repoUrl":30,"updatedAt":335},"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},[324,327,330,333,334],{"name":325,"slug":326,"type":15},"A\u002FB Testing","a-b-testing",{"name":328,"slug":329,"type":15},"Analytics","analytics",{"name":331,"slug":332,"type":15},"Data Analysis","data-analysis",{"name":27,"slug":28,"type":15},{"name":9,"slug":8,"type":15},"2026-05-22T06:59:58.103867",{"slug":337,"name":337,"fn":338,"description":339,"org":340,"tags":341,"stars":29,"repoUrl":30,"updatedAt":347},"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},[342,343,344,345,346],{"name":328,"slug":329,"type":15},{"name":27,"slug":28,"type":15},{"name":24,"slug":25,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-04-22T05:06:51.989772",{"slug":349,"name":349,"fn":350,"description":351,"org":352,"tags":353,"stars":29,"repoUrl":30,"updatedAt":358},"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},[354,355,356,357],{"name":328,"slug":329,"type":15},{"name":27,"slug":28,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-04-27T05:46:14.554016",{"slug":360,"name":360,"fn":361,"description":362,"org":363,"tags":364,"stars":29,"repoUrl":30,"updatedAt":374},"error-tracking-android","track Android errors with PostHog","PostHog error tracking for Android",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[365,368,369,372,373],{"name":366,"slug":367,"type":15},"Android","android",{"name":27,"slug":28,"type":15},{"name":370,"slug":371,"type":15},"Mobile","mobile",{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-04-06T18:46:26.982494",110,{"items":377,"total":540},[378,393,403,416,429,442,458,475,487,502,512,530],{"slug":379,"name":379,"fn":380,"description":381,"org":382,"tags":383,"stars":390,"repoUrl":391,"updatedAt":392},"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},[384,385,388,389],{"name":328,"slug":329,"type":15},{"name":386,"slug":387,"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":394,"name":394,"fn":395,"description":396,"org":397,"tags":398,"stars":390,"repoUrl":391,"updatedAt":402},"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},[399,400,401],{"name":328,"slug":329,"type":15},{"name":293,"slug":294,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:33.693989",{"slug":404,"name":404,"fn":405,"description":406,"org":407,"tags":408,"stars":390,"repoUrl":391,"updatedAt":415},"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},[409,410,413,414],{"name":293,"slug":294,"type":15},{"name":411,"slug":412,"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":417,"name":417,"fn":418,"description":419,"org":420,"tags":421,"stars":390,"repoUrl":391,"updatedAt":428},"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},[422,423,424,427],{"name":293,"slug":294,"type":15},{"name":411,"slug":412,"type":15},{"name":425,"slug":426,"type":15},"Performance","performance",{"name":9,"slug":8,"type":15},"2026-06-18T08:25:10.936787",{"slug":430,"name":430,"fn":431,"description":432,"org":433,"tags":434,"stars":390,"repoUrl":391,"updatedAt":441},"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},[435,438,439,440],{"name":436,"slug":437,"type":15},"Alerting","alerting",{"name":27,"slug":28,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:24:40.318583",{"slug":443,"name":443,"fn":444,"description":445,"org":446,"tags":447,"stars":390,"repoUrl":391,"updatedAt":457},"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},[448,449,452,453,456],{"name":328,"slug":329,"type":15},{"name":450,"slug":451,"type":15},"Monitoring","monitoring",{"name":13,"slug":14,"type":15},{"name":454,"slug":455,"type":15},"Operations","operations",{"name":9,"slug":8,"type":15},"2026-07-18T05:10:54.430898",{"slug":459,"name":459,"fn":460,"description":461,"org":462,"tags":463,"stars":390,"repoUrl":391,"updatedAt":474},"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},[464,467,470,471],{"name":465,"slug":466,"type":15},"Automation","automation",{"name":468,"slug":469,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},{"name":472,"slug":473,"type":15},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",{"slug":476,"name":476,"fn":477,"description":478,"org":479,"tags":480,"stars":390,"repoUrl":391,"updatedAt":486},"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},[481,482,483,484,485],{"name":328,"slug":329,"type":15},{"name":27,"slug":28,"type":15},{"name":24,"slug":25,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-05-07T05:56:19.828048",{"slug":488,"name":488,"fn":489,"description":490,"org":491,"tags":492,"stars":390,"repoUrl":391,"updatedAt":501},"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},[493,496,497,498],{"name":494,"slug":495,"type":15},"API Development","api-development",{"name":24,"slug":25,"type":15},{"name":9,"slug":8,"type":15},{"name":499,"slug":500,"type":15},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":503,"name":503,"fn":504,"description":505,"org":506,"tags":507,"stars":390,"repoUrl":391,"updatedAt":511},"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},[508,509,510],{"name":494,"slug":495,"type":15},{"name":454,"slug":455,"type":15},{"name":9,"slug":8,"type":15},"2026-07-15T05:29:58.442727",{"slug":513,"name":513,"fn":514,"description":515,"org":516,"tags":517,"stars":390,"repoUrl":391,"updatedAt":529},"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},[518,519,522,523,526],{"name":465,"slug":466,"type":15},{"name":520,"slug":521,"type":15},"Email","email",{"name":9,"slug":8,"type":15},{"name":524,"slug":525,"type":15},"Reporting","reporting",{"name":527,"slug":528,"type":15},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":531,"name":531,"fn":532,"description":533,"org":534,"tags":535,"stars":390,"repoUrl":391,"updatedAt":539},"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},[536,537,538],{"name":328,"slug":329,"type":15},{"name":494,"slug":495,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:29.624498",231]