Skip to content
TrustedSkillsbeta
Back to all skills

React Doctor

Official
posthog·vlatest·frontend

Diagnose and fix common PostHog React integration issues with automated code analysis and guidance.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add posthog/posthog --skill react-doctor -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

posthog

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned posthog/posthog at edc1585d12.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
edc1585d12
Manifest
.agents/skills/react-doctor/SKILL.md
Scanned
1 file, 40 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The posthog-react-doctor skill provides automated code review and suggestions specifically tailored for React applications using PostHog. It analyzes your codebase to identify potential performance bottlenecks, accessibility issues, and adherence to best practices within the context of PostHog integration. This helps ensure a smooth and efficient user experience while maximizing the value derived from PostHog's features.

When to use it

  • Performance Audits: Before deploying a React application integrated with PostHog, run this skill to proactively identify and resolve performance issues.
  • Accessibility Checks: Ensure your React components are accessible by leveraging the skill’s accessibility analysis capabilities.
  • Code Quality Reviews: Integrate this skill into your CI/CD pipeline for automated code reviews focused on PostHog-related aspects of your React codebase.
  • Refactoring Existing Code: When refactoring a legacy React application with PostHog integration, use the skill to guide improvements and identify potential problems.

Key capabilities

  • React component analysis
  • Performance bottleneck detection
  • Accessibility issue identification
  • PostHog best practices enforcement

Example prompts

  • "Analyze this React component for performance issues related to PostHog."
  • "Check the accessibility of my PostHog event tracking implementation in this file."
  • "Review this code snippet and suggest improvements based on PostHog best practices."

Tips & gotchas

This skill is most effective when used with a React application that already has PostHog integrated. The analysis focuses specifically on interactions between the React codebase and PostHog, so it won't provide general React advice.