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 instrumenting your codebase with PostHog error tracking. It guides the agent through detecting your platform, installing the necessary SDK, enabling exception autocapture, and configuring manual error boundaries. It also ensures that environment variables are handled securely and that source maps are correctly configured for frontend and mobile projects, allowing for clear, actionable debugging.
What it does
- Detects your project's platform and framework automatically.
- Installs and initializes the PostHog SDK if not already present.
- Enables automatic exception capture for unhandled errors.
- Assists in adding manual error capture at critical boundaries.
- Configures source map uploads for readable stack traces.
- Sets up required environment variables for secure API communication.
When to use it
- After implementing new features to ensure robust error monitoring.
- During code reviews when you identify a need for better exception visibility.
- When setting up a new project and wanting to include error tracking from the start.
- When you need to resolve minified stack traces in your production logs.
Advantages
- Ensures consistent error tracking patterns across different platforms.
- Reduces manual setup effort by automating SDK installation and configuration.
- Promotes secure practices by enforcing the use of environment variables.
- Improves debugging efficiency by linking errors to original source code via source maps.
Usage examples
- “Set up PostHog error tracking for my React project.”
- The agent will detect the React environment, install the PostHog SDK, enable autocapture, and guide you through setting up the necessary environment variables.
- “I need to track errors in my Node.js backend using PostHog.”
- The agent will identify the Node.js environment, configure the SDK, and help you place manual capture points in your catch blocks.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/instrument-error-tracking/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip 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, PHP, Ruby, Ruby on Rails, Go, Elixir, Angular, Svelte, Nuxt, React Native, Flutter, iOS, Android, and Hono.
Instructions
Follow these steps IN ORDER:
STEP 1: Analyze the codebase and detect the platform.
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.
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.
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.
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.
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.If the PostHog project token is missing, use the PostHog MCP server's
projects-gettool to retrieve the project'sapi_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.For the PostHog host URL: check the
projects-getMCP response for aregionfield —USmaps tohttps://us.i.posthog.com,EUmaps tohttps://eu.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.Write these values to the appropriate env file using the framework's naming convention.
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, but ONLY on the files you have edited or created during this session. Never run formatting or linting across the entire project's codebase.
Reference files
references/react.md- React error tracking installationreferences/web.md- Web error tracking installationreferences/nextjs.md- Next.js error tracking installationreferences/node.md- Node.js error tracking installationreferences/python.md- Python error tracking installationreferences/django.md- Djangoreferences/flask.md- Flaskreferences/php.md- Php error tracking installationreferences/laravel.md- Laravelreferences/ruby.md- Ruby error tracking installationreferences/ruby-on-rails.md- Ruby on rails error tracking installationreferences/ruby-on-rails.md- Ruby on railsreferences/go.md- Go error tracking installationreferences/dotnet.md- .net error tracking installationreferences/dotnet.md- .netreferences/elixir.md- Elixir error tracking installationreferences/angular.md- Angular error tracking installationreferences/svelte.md- Sveltekit error tracking installationreferences/nuxt-3-7.md- Nuxt error tracking installation (v3.7 and above)references/nuxt-3-6.md- Nuxt error tracking installation (v3.6 and below)references/react-native.md- React native error tracking installationreferences/flutter.md- Flutter error tracking installationreferences/ios.md- Ios error tracking installationreferences/android.md- Android error tracking installationreferences/hono.md- Hono error tracking installationreferences/fingerprints.md- Fingerprintsreferences/alerts.md- Send error tracking alertsreferences/monitoring.md- Monitor and search issuesreferences/assigning-issues.md- Assign issues to teammatesreferences/upload-source-maps.md- Upload source mapsreferences/COMMANDMENTS.md- Framework-specific rules the integration must follow
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 AutoGineer961 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md6.9 KiB
- references/COMMANDMENTS.md1.5 KiB
- references/alerts.md4.2 KiB
- references/android.md4.8 KiB
- references/angular.md9.1 KiB
- references/assigning-issues.md6.8 KiB
- references/django.md14.9 KiB
- references/dotnet.md25.8 KiB
- references/elixir.md10.0 KiB
- references/fingerprints.md4.6 KiB
- references/flask.md8.1 KiB
- references/flutter.md13.3 KiB
- references/go.md5.9 KiB
- references/hono.md3.7 KiB
- references/ios.md7.4 KiB
- references/laravel.md13.1 KiB
- references/monitoring.md8.7 KiB
- references/nextjs.md15.8 KiB
- references/node.md4.8 KiB
- references/nuxt-3-6.md5.9 KiB
- references/nuxt-3-7.md5.3 KiB
- references/php.md6.4 KiB
- references/python.md9.0 KiB
- references/react-native.md10.4 KiB
- references/react.md6.4 KiB
- references/ruby-on-rails.md19.7 KiB
- references/ruby.md3.6 KiB
- references/svelte.md5.8 KiB
- references/upload-source-maps.md4.2 KiB
- references/web.md5.8 KiB
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 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/omnibus/instrument-error-tracking · commit a5d30e7
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by PostHog or PostHog.
Related skills
Claude API
AnthropicOfficial
Comprehensive reference for integrating Anthropic's Claude API, SDKs, and Managed Agents into your applications.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreApache-2.0Medium riskHas scriptsGitHub stars of the source repository188.6k
Transformers
K-Dense· Community
Integrate Hugging Face Transformers for model loading, inference, and fine-tuning across NLP, vision, and audio tasks.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskGitHub stars of the source repository56.4k
Open Notebook
K-Dense· Community
Integrate with the self-hosted Open Notebook platform to automate research ingestion, context-aware chat, and AI-driven analysis.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITLow riskHas scriptsGitHub stars of the source repository56.4k
Vision Sft
Seth Hobson· Community
A structured workflow for supervised fine-tuning of vision-language models, focusing on adapter configuration and silent failure prevention.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
LLM Evaluation
Seth Hobson· Community
A comprehensive framework for evaluating LLM application performance using automated metrics, human feedback, and LLM-as-a-judge techniques.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Lora Qlora Recipes
Seth Hobson· Community
Provides configuration recipes and best-practice hyperparameters for LoRA and QLoRA supervised fine-tuning.
Data and AIClaude CodeClaude appsOpenAI Codex+14 moreMITGitHub stars of the source repository42.3k
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download instrument-error-tracking.zip