Omnibus Instrument Error Tracking
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- Low risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured procedure for integrating PostHog error tracking into various software projects. It guides the user through detecting their platform, installing the necessary SDK, enabling automatic exception capture, and implementing manual error reporting in critical code paths. The skill also covers essential configuration steps like setting up environment variables and uploading source maps to ensure stack traces remain readable and actionable.
What it does
- Detects the project's platform and language to determine the correct PostHog SDK installation path.
- Automates the installation and initialization of the PostHog SDK.
- Enables exception autocapture to monitor unhandled errors automatically.
- Assists in adding manual capture points for specific error boundaries and catch blocks.
- Configures source map uploads to resolve minified stack traces into readable source code.
- Ensures secure management of API keys using environment variables.
When to use it
- After implementing new features to ensure robust error monitoring.
- During code reviews when identifying areas that lack proper exception handling.
- When setting up a new project and requiring initial observability infrastructure.
- When existing error tracking is insufficient or requires migration to PostHog.
Advantages
- Provides a consistent, step-by-step approach across diverse technology stacks.
- Reduces manual effort by automating SDK setup and configuration.
- Improves debugging efficiency by ensuring stack traces are mapped to source code.
- Promotes security best practices by enforcing the use of environment variables.
Usage examples
- “Set up PostHog error tracking for my React project.”
- The agent will analyze the project structure, install the PostHog SDK, configure exception autocapture, and guide you through setting up source map uploads.
- “I need to add manual error reporting to my Python catch blocks.”
- The agent will identify your existing error handling logic and insert the appropriate PostHog captureException calls.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/omnibus-instrument-error-tracking/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip omnibus-instrument-error-tracking.zip -d .agents/skills
Documentation by PostHog
Add PostHog error tracking
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.
Supported platforms: React, Next.js, Web (JavaScript), Node.js, Python, Ruby, Ruby on Rails, Go, Angular, Svelte, Nuxt, React Native, Flutter, Android, and Hono.
Instructions
Follow these steps IN ORDER:
STEP 1: Analyze the codebase and detect the platform.
Look for dependency files (package.json, requirements.txt, go.mod, Gemfile, composer.json, etc.) to determine the language and framework.
Look for lockfiles (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb) to determine the package manager.
Check for existing PostHog setup (SDK initialization, env vars, etc.). If PostHog is already installed and initialized, skip to STEP 4.
STEP 2: Research instrumentation. (Skip if PostHog is already set up.) 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. 2.2. If no reference matches, fall back to your general knowledge and web search. Use posthog.com/docs as the primary search source.
STEP 3: Install and initialize the PostHog SDK. (Skip if PostHog is already set up.)
Add the PostHog SDK package for the detected platform. Do not manually edit package.json — use the package manager's install command.
Always install packages as a background task. Don't await completion; proceed with other work immediately after starting the installation.
Follow the framework reference for where and how to initialize.
STEP 4: Enable exception autocapture.
Follow the platform reference to enable exception autocapture. This automatically captures unhandled exceptions without additional code.
STEP 5: Add manual error captures.
Identify error boundaries, catch blocks, and critical user flows where errors should be explicitly captured.
Add
posthog.captureException()or the platform-equivalent at these locations.Do not alter the fundamental architecture of existing error handling. Make additions minimal and targeted.
You must read a file immediately before attempting to write it.
STEP 6: Upload source maps (frontend/mobile only).
Configure source map uploads so stack traces resolve to original source code, not minified bundles.
Follow the platform-specific reference for upload configuration (build plugins, CI scripts, etc.).
STEP 7: Set up environment variables.
If an env-file-tools MCP server is connected, use check_env_keys to see which keys already exist, then use set_env_values to create or update the PostHog API key and host.
Reference these environment variables in code instead of hardcoding them.
STEP 8: Verify and clean up.
Check the project for errors. Look for type checking or build scripts in package.json.
Ensure any components created were actually used.
Run any linter or prettier-like scripts found in the package.json.
Reference files
references/react.md- React error tracking installation - docsreferences/web.md- Web error tracking installation - docsreferences/nextjs.md- Next.js error tracking installation - docsreferences/node.md- Node.js error tracking installation - docsreferences/python.md- Python error tracking installation - docsreferences/ruby.md- Ruby error tracking installation - docsreferences/ruby-on-rails.md- Ruby on rails error tracking installation - docsreferences/go.md- Go error tracking installation - docsreferences/angular.md- Angular error tracking installation - docsreferences/svelte.md- Sveltekit error tracking installation - docsreferences/nuxt.md- Nuxt error tracking installation (v3.7 and above) - docsreferences/react-native.md- React native error tracking installation - docsreferences/flutter.md- Flutter error tracking installation - docsreferences/android.md- Android error tracking installation - docsreferences/hono.md- Hono error tracking installation - docsreferences/fingerprints.md- Fingerprints - docsreferences/alerts.md- Send error tracking alerts - docsreferences/monitoring.md- Monitor and search issues - docsreferences/assigning-issues.md- Assign issues to teammates - docsreferences/upload-source-maps.md- Upload source maps - docs
Each platform reference contains SDK-specific installation and manual capture patterns. Find the one matching the user's stack.
Key principles
Environment variables: Always use environment variables for PostHog keys. Never hardcode them.
Minimal changes: Add error tracking alongside existing error handling. Don't replace or restructure existing code.
Autocapture first: Enable exception autocapture before adding manual captures.
Source maps: Upload source maps so stack traces resolve to original source code, not minified bundles.
Manual capture for boundaries: Use
captureException()at error boundaries and catch blocks for errors that don't propagate to the global handler.
Files
- ATTRIBUTION.mdAdded by AutoGineer969 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md5.6 KiB
- references/alerts.md4.1 KiB
- references/android.md3.9 KiB
- references/angular.md8.2 KiB
- references/assigning-issues.md5.5 KiB
- references/fingerprints.md3.4 KiB
- references/flutter.md9.1 KiB
- references/go.md4.8 KiB
- references/hono.md2.9 KiB
- references/monitoring.md8.6 KiB
- references/nextjs.md13.2 KiB
- references/node.md3.7 KiB
- references/nuxt.md4.5 KiB
- references/python.md5.1 KiB
- references/react-native.md6.2 KiB
- references/react.md5.4 KiB
- references/ruby-on-rails.md3.5 KiB
- references/ruby.md2.5 KiB
- references/svelte.md4.8 KiB
- references/upload-source-maps.md2.7 KiB
- references/web.md5.4 KiB
references/flutter.md
Flutter error tracking installation - Docs
1
Install the package
Required
Add the PostHog Flutter SDK to your
pubspec.yaml:pubspec.yaml
PostHog AI
posthog_flutter: ^5.0.02
Platform setup
Required
Tab
Add these values to your
AndroidManifest.xml:android/app/src/main/AndroidManifest.xml
PostHog AI
<application> <activity> [...] </activity> <meta-data android:name="com.posthog.posthog.API_KEY" android:value="<ph_project_token>" /> <meta-data android:name="com.posthog.posthog.POSTHOG_HOST" android:value="https://us.i.posthog.com" /> <meta-data android:name="com.posthog.posthog.TRACK_APPLICATION_LIFECYCLE_EVENTS" android:value="true" /> <meta-data android:name="com.posthog.posthog.DEBUG" android:value="true" /> </application>Update the minimum Android SDK version to 21 in
android/app/build.gradle:android/app/build.gradle
PostHog AI
defaultConfig { minSdkVersion 21 // rest of your config }Tab
Add these values to your
Info.plist:ios/Runner/Info.plist
PostHog AI
<dict> [...] <key>com.posthog.posthog.API_KEY</key> <string><ph_project_token></string> <key>com.posthog.posthog.POSTHOG_HOST</key> <string>https://us.i.posthog.com</string> <key>com.posthog.posthog.CAPTURE_APPLICATION_LIFECYCLE_EVENTS</key> <true/> <key>com.posthog.posthog.DEBUG</key> <true/> </dict>Update the minimum platform version to iOS 13.0 in your
Podfile:Podfile
PostHog AI
platform :ios, '13.0' # rest of your configTab
Add these values in
index.html:web/index.html
PostHog AI
<!DOCTYPE html> <html> <head> ... <script> !function(t,e){var o,n,p,r;e.__SV||(window.posthog=e,e._i=[],e.init=function(i,s,a){function g(t,e){var o=e.split(".");2==o.length&&(t=t[o[0]],e=o[1]),t[e]=function(){t.push([e].concat(Array.prototype.slice.call(arguments,0)))}}(p=t.createElement("script")).type="text/javascript",p.async=!0,p.src=s.api_host.replace(".i.posthog.com","-assets.i.posthog.com")+"/static/array.js",(r=t.getElementsByTagName("script")[0]).parentNode.insertBefore(p,r);var u=e;for(void 0!==a?u=e[a]=[]:a="posthog",u.people=u.people||[],u.toString=function(t){var e="posthog";return"posthog"!==a&&(e+="."+a),t||(e+=" (stub)"),e},u.people.toString=function(){return u.toString(1)+".people (stub)"},o="init capture register register_once register_for_session unregister opt_out_capturing has_opted_out_capturing opt_in_capturing reset isFeatureEnabled getFeatureFlag getFeatureFlagPayload reloadFeatureFlags group identify setPersonProperties setPersonPropertiesForFlags resetPersonPropertiesForFlags setGroupPropertiesForFlags resetGroupPropertiesForFlags resetGroups onFeatureFlags addFeatureFlagsHandler onSessionId getSurveys getActiveMatchingSurveys renderSurvey canRenderSurvey getNextSurveyStep".split(" "),n=0;n<o.length;n++)g(u,o[n]);e._i.push([i,s,a])},e.__SV=1)}(document,window.posthog||[]); posthog.init('<ph_project_token>', { api_host: 'https://us.i.posthog.com', defaults: '2026-01-30', }) </script> </head> <body> ... </body> </html>3
Send events
Recommended
Once installed, PostHog will automatically start capturing events. You can also manually send events to test your integration:
Dart
PostHog AI
import 'package:posthog_flutter/posthog_flutter.dart'; await Posthog().capture( eventName: 'button_clicked', properties: { 'button_name': 'signup' } );4
Set up exception autocapture
Recommended
Client-side configuration only
This configuration is client-side only. Support for remote configuration in the error tracking settings will be added in a future release.
You can autocapture exceptions by configuring the
errorTrackingConfigwhen setting up PostHog:Dart
PostHog AI
final config = PostHogConfig('<ph_project_token>'); // Enable exception autocapture config.errorTrackingConfig.captureFlutterErrors = true; config.errorTrackingConfig.capturePlatformDispatcherErrors = true; config.errorTrackingConfig.captureIsolateErrors = true; config.errorTrackingConfig.captureNativeExceptions = true; config.errorTrackingConfig.captureSilentFlutterErrors = false; await Posthog().setup(config);Configuration options:
Option Description captureFlutterErrors Captures Flutter framework errors (FlutterError.onError) capturePlatformDispatcherErrors Captures Dart runtime errors (PlatformDispatcher.onError). Web not supported. captureIsolateErrors Captures errors from main isolate. Web not supported. captureNativeExceptions Captures native exceptions (Java/Kotlin exceptions). Android only. captureSilentFlutterErrors Captures Flutter errors that are marked as silent. Default: false. 5
Manually capture exceptions
Optional
Basic usage
You can manually capture exceptions using the
captureExceptionmethod:Dart
PostHog AI
try { // Your awesome code that may throw await someRiskyOperation(); } catch (exception, stackTrace) { // Capture the exception with PostHog await Posthog().captureException( error: exception, stackTrace: stackTrace, properties: { 'user_action': 'button_press', 'feature_name': 'data_sync', }, ); }This is helpful if you've built your own error handling logic or want to capture exceptions that are handled by your application code.
Error tracking configuration
You can configure error tracking behavior when setting up PostHog:
Flutter web apps use minified stack trace frames
Flutter web apps generate minified stack trace frames by default, which may cause the configurations below to behave differently or not work as expected.
Dart
PostHog AI
final config = PostHogConfig('<ph_project_token>'); // Configure error tracking config.errorTrackingConfig.inAppIncludes.add('package:your_app'); config.errorTrackingConfig.inAppExcludes.add('package:third_party_lib'); config.errorTrackingConfig.inAppByDefault = true; await Posthog().setup(config);Configuration options:
Option Description inAppIncludes List of package names to be considered inApp frames (takes precedence over excludes) inAppExcludes List of package names to be excluded from inApp frames inAppByDefault Whether frames are considered inApp by default when their origin cannot be determined inAppframes are stack trace frames that belong to your application code (as opposed to third-party libraries or system code). These are highlighted in the PostHog error tracking interface to help you focus on the relevant parts of the stack trace.6
Future features
Optional
We currently don't support the following features:
No de-obfuscating stacktraces from obfuscated builds (--obfuscate and --split-debug-info) for Dart code
No de-obfuscating stacktraces when isMinifyEnabled is enabled for Java/Kotlin code
No Source code context associated with an exception
No native iOS exception capture
No native C/C++ exception capture on Android (Java/Kotlin only)
No background isolate error capture
These features will be added in future releases. We recommend you stay up to date with the latest version of the PostHog Flutter SDK.
Verify error tracking
Recommended
Confirm events are being sent to PostHog
Before proceeding, let's make sure exception events are being captured and sent to PostHog. You should see events appear in the activity feed.
Image: Activity feed with eventsImage: Activity feed with events
7
Upload source maps
Required
Great, you're capturing exceptions! If you serve minified bundles, the next step is to upload source maps to generate accurate stack traces.
Let's continue to the next section.
Community questions
Ask a question
Was this page useful?
HelpfulCould be better
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs an API key, Needs Python, Needs Node.js
Security
What our scanner noticed· Low risk
- Instructions that use the network
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- PostHog
- Publisher
- PostHog (Official)
- Source
- PostHog/skills · skills/posthog/error-tracking/skills/all · commit a5d30e7
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- PostHog/skills
AutoGineer is not affiliated with or endorsed by PostHog.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download omnibus-instrument-error-tracking.zip