posthog-core-workflow-a
Implement PostHog product analytics: event capture, user identification, group analytics, and property management using posthog-js and posthog-node. "posthog identify", "posthog group analytics", "product analytics". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill posthog-core-workflow-a --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PostHog Core Workflow A — Product Analytics ## Overview Primary PostHog workflow covering event capture, user identification, group analytics, and person properties. This is the foundation for all PostHog analytics: capturing what users do, linking events to identified users, and grouping users by company/team for B2B analytics. ## Prerequisites - Completed `posthog-install-auth` setup - `postho
What does the posthog-core-workflow-a skill do?
Implement PostHog product analytics: event capture, user identification, group analytics, and property management using posthog-js and posthog-node. "posthog identify", "posthog group analytics", "product analytics". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill posthog-core-workflow-a --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.