LabscoMCP early access ↗
REPO PACKAGECOMMUNITY

posthog posthog-for-claude

posthog · publisher12 GitHub starsListed as freegithub.com/posthog/posthog-for-claude

LABSCO SUMMARY

Summary

posthog/posthog-for-claude is a single skill, and the repository's own readme says it has moved to PostHog/ai-plugin.

The one skill still here, posthog-instrumentation, adds PostHog analytics calls to an existing codebase — event tracking, capture calls, feature-flag checks — and is written to trigger whenever someone asks to add tracking, instrument events, or implement feature flags. That is the entire content of the package: one skill, one short trigger description, nothing else.

Confusingly, the install command the readme gives — claude plugin install posthog — is written for the new repository, not this one; a reader who runs it against posthog-for-claude itself gets nothing, because the actual plugin package now lives at PostHog/ai-plugin. This page describes what ships in posthog-for-claude specifically: one skill sitting behind a deprecation notice, still reachable on GitHub, still installable by name, but not the repository PostHog wants a new user to add.

READ MORE

What the surviving skill needs.

Our capability check classifies posthog-instrumentation as needing a stored account key, which matches how PostHog works generally — writing an event needs a project API key — even though the skill's own one-sentence description doesn't mention any credential.

We have not reviewed PostHog/ai-plugin itself.

It is a separate package with its own page if one exists; nothing in that repository's content was checked to write this summary.