PostHog Debugger
0This skill helps developers and product teams understand how PostHog is configured and what data is being captured. It's ideal for anyone involved in implementing or analyzing PostHog on web platforms.
000Updated 2mo ago
Debugging Tools
Quick InstallView Source
$ npx skills add https://github.com/posthog/skills --skill posthog-debuggerOverview
About This Skill
The PostHog Debugger skill provides developers and product teams with visibility into how PostHog is configured and what data is being captured on web platforms. It helps diagnose PostHog integration issues, verify event tracking setup, and understand data flow. This skill is useful during PostHog implementation, when troubleshooting tracking problems, or when analyzing whether your analytics configuration matches your intended behavior. Teams can install it directly into their Claude Code environment to gain quick insights into their PostHog instance.
How to Use
Use the command line to install the skill with the provided npx command.
Use Cases
Inspect data capture for a PostHog implementation
Troubleshoot issues with PostHog tracking
Ensure PostHog is correctly set up for a website
View scripts and network requests related to PostHog
Tags
Setup & Installation
Quick Install
Terminal
$ npx skills add https://github.com/posthog/skills --skill posthog-debuggerAlternative Install (Git Clone)
git clone https://github.com/posthog/skillsRequirements
- Claude Code or compatible AI agent
Quick Start Guide
1
Install the Skill
Copy the install command above and run it in your terminal.
2
Open Your AI Agent
Launch Claude Code, Cursor, or your preferred AI coding agent.
3
Try It Out
Use the prompt template or examples below to test the skill.
4
Customize
Adapt the skill to your specific use case and workflow.
Usage Examples
Prompt Template
Act as a PostHog debugging assistant. Analyze the following PostHog configuration and data capture setup for [COMPANY]'s [WEBSITE_NAME] platform. Review the tracking code, events, and properties being sent to PostHog. Identify any misconfigurations, missing data, or potential issues. Provide specific recommendations to improve data accuracy and completeness. Here's the context: [POSTHOG_CONFIGURATION_JSON].
Example Output
## PostHog Debugging Report for Acme Corp's SaaS Platform
### Current Configuration Issues
**1. Missing User Identification**
- Issue: The `identify()` call is missing the user's email property
- Impact: Events are not properly linked to user profiles
- Fix: Add `posthog.identify('user123', { email: '[email protected]' })`
**2. Inconsistent Event Naming**
- Issue: `signup_completed` vs `signup_complete` in different parts of the code
- Impact: Duplicate events in PostHog
- Fix: Standardize to `signup_completed` across all tracking
**3. Property Naming Inconsistencies**
- Issue: `plan_type` vs `subscription_plan` in different events
- Impact: Difficult to filter and analyze data
- Fix: Use `plan_type` consistently
### Recommendations
**Immediate Actions (Next 24 hours):**
- Add missing user identification properties
- Standardize event naming conventions
- Implement property validation rules
**Long-term Improvements:**
- Set up automated testing for tracking code
- Create a data dictionary for your team
- Schedule monthly configuration reviewsApply to these tools
Browse all toolsCompatible MCP servers
Browse all MCP servers
Find the right skills for your stack
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan