Agent Skills

signals-scout-web-analytics

★ 35,336

by posthog

Signals scout for PostHog web traffic. Watches per-channel session volume, attribution breakage, and landing-page health (bounce / 404 steps) against the site's own baseline, and files each validated divergence as a report in the inbox. Per-page web vitals have their own dedicated `signals-scout-web-vitals`.

🧰 Not standalone — use together with posthog/posthog

signals-scout-web-vitals

★ 35,336

by posthog

Focused Signals scout for PostHog projects capturing Core Web Vitals (`$web_vitals`). Watches each page's p75 LCP / INP / CLS / FCP against the absolute Google thresholds (good / needs-improvement / poor) and against its own history: pages standing in the poor band, pages crossing a band boundary after a deploy, and sharp in-band regressions. Reads the historical trajectory — not just the moment a value changes — so a page that is steadily slow surfaces even when nothing moved today. Every findi

🧰 Not standalone — use together with posthog/posthog

using-kea-disposables

★ 35,336

by posthog

Use when adding timers (`setInterval`, `setTimeout`), event listeners (`window.addEventListener`, `document.addEventListener`, `MediaQueryList.addEventListener`), or any other resource that needs cleanup inside a kea logic. Every logic has `cache.disposables.add(setup, key?, options?)` and `cache.disposables.dispose(key)` available via the globally registered `disposablesPlugin` (`frontend/src/kea-disposables.ts`). Replaces the bare `cache.foo = setInterval(...)` + `beforeUnmount: clearInterval(

🧰 Not standalone — use together with posthog/posthog

using-the-console-ui

★ 35,336

by posthog

How to drive PostHog Code's read panel as the user works with you — focus_* etiquette, when to call toast, how to handle 'follow mode' being off. Load when the session client kind is `posthog-code`.

🧰 Not standalone — use together with posthog/posthog

verify-posthog-instrumentation

★ 35,336

by posthog

Use this skill to verify that PostHog instrumentation is firing correctly on a website. Drives a real browser at one or more URLs, observes which PostHog events actually arrive, and reports a pass/fail summary. Use after installing the PostHog SDK on a site, after a deploy that touches tracking code, or when events appear missing in the PostHog dashboard.

🧰 Not standalone — use together with posthog/posthog

visualizing-change-over-time

★ 35,336

by posthog

Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with @posthog/quill-charts (dashboards, reports, the mcp_analytics frontend, custom visualizations). Use when a user asks how something "changed", "moved", "grew", "dropped", "improved", or "regressed" between two points or periods, or mentions "before/after", "period over period", "week over week", "delta", "slop

🧰 Not standalone — use together with posthog/posthog

weekly-summary

★ 35,336

by posthog

The Monday digest — how to query last week's kudos, group by recipient, format the celebratory mrkdwn post, and what to do on a quiet week. Load when the weekly cron fires or someone asks for a summary.

🧰 Not standalone — use together with posthog/posthog

working-outside-the-console

★ 35,336

by posthog

Operating without a UI — MCP / IDE / Slack mode. How to compensate for missing client tools, how to be useful in a text-only chat. Load when the session client kind is NOT `posthog-code`.

🧰 Not standalone — use together with posthog/posthog

working-with-skills

★ 35,336

by posthog

Best practices for agents managing PostHog skills via the MCP `skill-*` tools — how to discover, read, create, update, and refactor skills efficiently, especially large skills with many bundled files. Use whenever you are about to call any `skill-*` tool, asked to author or edit a shared skill, or troubleshoot why a skill write was rejected. Pairs with `skills-store` (which covers the raw tool surface) by adding the decision-tree, efficiency, and pitfall guidance.

🧰 Not standalone — use together with posthog/posthog

writing-clickhouse-queries

★ 35,336

by posthog

Guide for writing performant ClickHouse queries in PostHog product code. Use when writing HogQL query runners, designing a ClickHouse table for a new product, adding materialized columns or skip indexes, or choosing a row ID format. For optimizing an existing query that is already too slow, use `/optimizing-clickhouse-and-hogql-queries` instead.

🧰 Not standalone — use together with posthog/posthog

writing-kea-logics

★ 35,336

by posthog

Guide for writing or reviewing PostHog kea logic files (`*Logic.ts` / `*Logic.tsx`). Use when creating a new logic, adding actions/reducers/selectors/listeners/loaders/forms/router bindings, choosing between reducer vs selector vs cache, deciding between listeners and `kea-subscriptions`, wiring React with `useValues`/`useActions`/`BindLogic`, or onboarding to kea conventions. Read keajs.org for upstream API; this skill captures PostHog-specific conventions and idioms.

🧰 Not standalone — use together with posthog/posthog

writing-tests

★ 35,336

by posthog

Gates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before adding or substantially changing any pytest, Jest, or Playwright test — whenever an agent or engineer is about to write tests for a new feature, bugfix, or PR. Front-loads the value bar (every test must catch a realistic regression no existing test already catches; test behavior through the public interface, not implementation details; collapse near-duplicates into parameteriz

🧰 Not standalone — use together with posthog/posthog

react-doctor

★ 35,336

by posthog

Diagnose and fix React codebase health issues. Use when reviewing React code, fixing performance problems, auditing security, or improving code quality.

🧰 Not standalone — use together with posthog/posthog

finding-experiments

★ 35,336

by posthog

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 re

🧰 Not standalone — use together with posthog/posthog

suggesting-data-imports

★ 35,336

by posthog

Use when the user asks about revenue, payments, subscriptions, billing, CRM deals, support tickets, ad spend, production database tables, or other data PostHog does not collect natively — or wants to join or correlate PostHog product events with that external business data. Also use when a query fails because a table does not exist or returns no results for expected external data. The data warehouse can import from SaaS tools (Stripe, Hubspot, Zendesk, etc.), ad platforms, production databases (

🧰 Not standalone — use together with posthog/posthog