> 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).
npx skills add https://github.com/PostHog/posthog --skill check-posthog-loading
For each URL, navigates a real browser to the page, waits for PostHog to
initialize, and reports:
window.posthog is defined and __loaded.head_snippet, snippet, array_js_only, or none.head / body).api_key, api_host, person_profiles.distinct_id.api_host or api_key than others?
Call the check_posthog_loading MCP tool with:
urls (required) — list of URLs to inspect.posthog_host (default https://us.i.posthog.com).Returns a structured summary with which URLs loaded successfully, which
didn't, and the load-method distribution.
Look for these red flags:
loaded list, full not_loaded list — snippet not presentanywhere. Re-run install or check that the layout includes the snippet.
loaded / not_loaded — snippet missing from some pages.Common cause: a page rendered by a different template or layout.
api_key values across pages — a page is pointingat the wrong PostHog project.
api_host values — a page is pointing at the wrongingestion endpoint (e.g. EU cloud vs US cloud, or vs a self-hosted reverse
proxy). This causes events to land in different projects than expected.
load_method: array_js_only with no init config — array.js wasloaded but posthog.init() was never called. Common with manual installs
that miss the second half.
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take posthog/check-posthog-loading from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.