Loading...
Loading...
Found 98 Skills
PostHog integration for client-side web JavaScript applications using posthog-js
PostHog logs for Java
Automatically add PostHog analytics instrumentation to code. Triggers when user asks to add tracking, instrument events, add analytics, or implement feature flags in their codebase.
Implement PostHog webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling PostHog event notifications securely. Trigger with phrases like "posthog webhook", "posthog events", "posthog webhook signature", "handle posthog events", "posthog notifications".
Complete PostHog lifecycle management. Audits current state, fixes all issues, and verifies event tracking works end-to-end. Every run does all of this. Auto-invoke when: files contain posthog/analytics/tracking, imports posthog-js package, references POSTHOG_* env vars, event tracking code modified, user mentions "analytics not working" or "events not sending".
Identify and clean up stale feature flags in a PostHog project. Use when the user wants to find unused, fully rolled out, or abandoned feature flags, review them for safety, and then disable or delete them. Covers staleness detection, dependency checking, and safe removal workflows.
Automate PostHog tasks via Rube MCP (Composio): events, feature flags, projects, user profiles, annotations. Always search tools first for current schemas.
Audit PostHog survey SDK features and version requirements
Add PostHog SDK integration to your application. Use when setting up PostHog for the first time or reviewing PRs that need PostHog initialization. Covers SDK installation, provider setup, and basic configuration for any framework.
PostHog integration. Manage Persons, Groups, Events, Experiments, Dashboards, Annotations. Use when the user wants to interact with PostHog data.
Copy a feature flag from one PostHog project to one or more target projects in the same organization. Use when the user wants to duplicate a flag, promote a flag from staging to production, sync flags across projects, or replicate a flag configuration in a different workspace. Covers cohort remapping, scheduled-change handling, encrypted payloads, and the safe defaults (disabled in target, no scheduled changes).
Resolves a PostHog experiment reference from natural language to a concrete experiment ID by browsing `experiment-list` (not feature-flag tools), with disambiguation when multiple experiments match. Use when the user names or quotes an experiment ("split test demo", "the File engagement boost experiment", "onboarding retention test", "landing page hero experiment", "pricing experiment"), describes it loosely ("the signup experiment", "my pricing test", "the one with the new checkout"), uses a relative reference ("latest", "most recent", "the one I created yesterday"), filters by status (running, draft, stopped, archived), or otherwise refers to an experiment by anything other than its concrete ID.