Agent Skills

auditing-experiments-flags

★ 35,336

by posthog

Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.

🧰 Not standalone — use together with posthog/posthog

diagnosing-missing-recordings

★ 35,336

by posthog

Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling, triggers, ad blockers, and quota/billing scenarios.

🧰 Not standalone — use together with posthog/posthog

exploring-autocapture-events

★ 35,336

by posthog

Guides exploration of $autocapture events captured by posthog-js to understand user interactions, find CSS selectors (especially data-attr attributes), evaluate selector uniqueness, query matching clicks ad-hoc, and create actions. Use when the user asks about autocapture data, wants to find what users are clicking, needs to build actions from click events, asks about elements_chain, wants to build a trend or funnel filtered by clicks or other autocapture interactions, asks which properties auto

🧰 Not standalone — use together with posthog/posthog

adding-personhog-rpc

★ 35,336

by posthog

Guide for adding a new RPC to personhog-replica and personhog-router. Covers eligibility checks, proto definition, code generation for Python and Node.js clients, Rust implementation (storage trait, postgres queries, service handler, router wiring), and index compatibility validation. Use when adding a new gRPC endpoint to personhog, migrating a Django ORM query to personhog, or extending the personhog service API.

🧰 Not standalone — use together with posthog/posthog

carry-over

★ 35,336

by posthog

Pulling unchecked items from yesterday's briefing forward into today's, while filtering out anything that's already resolved by the new data. Load early in the briefing build — it's step 2 of the main loop.

🧰 Not standalone — use together with posthog/posthog

check-posthog-loading

★ 35,336

by posthog

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).

🧰 Not standalone — use together with posthog/posthog

checking-deploy-timing

★ 35,336

by posthog

Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask "when was X deployed", "is my change live in the US/EU yet", "has my PR shipped", "did the fix roll out to prod-us", or otherwise want to know whether/when a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event/data volume alone — that only shows when d

🧰 Not standalone — use together with posthog/posthog

choosing-the-model

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

choosing-trend-or-slope-view

★ 35,336

by posthog

Clarify how to visualize change over a time range before building a trend. Use whenever the user asks how much something changed, grew, dropped, improved, or regressed between two points or periods — "how much did X change from A to B", "before vs after", "start vs end", "week over week", "compare this month to last", "change over time" — or mentions a "slope chart" / "slopegraph". Two readings of "change" need different charts: the whole trend (a line, every interval) versus just the two endpoi

🧰 Not standalone — use together with posthog/posthog

setting-feature-flags-in-storybook

★ 35,336

by posthog

Use when writing a Storybook story for a component gated on a feature flag — boolean flags or multivariate/experiment-arm variants. Covers the `featureFlags` story parameter and why imperatively setting flags renders the flag-off branch in visual-regression snapshots while passing in jest.

🧰 Not standalone — use together with posthog/posthog

setting-up-a-custom-rest-source

★ 35,336

by posthog

Connect an arbitrary REST API to the PostHog data warehouse as a Custom source by authoring a JSON manifest, with no per-source code. Use when the user points at an API that has no built-in PostHog connector — "import data from this REST API", "sync my internal API", "connect this API from its docs", "build a custom data warehouse source" — and gives a docs URL or a natural-language description of the endpoints. Walks through drafting the RESTAPIConfig manifest (auth — bearer, API key, HTTP basi

🧰 Not standalone — use together with posthog/posthog

setting-up-a-data-warehouse-source

★ 35,336

by posthog

Guide the user through connecting a new data warehouse source — Postgres, MySQL, Stripe, Hubspot, MongoDB, Salesforce, BigQuery, Snowflake, and so on. Use when the user wants to "connect Stripe", "import data from Postgres", "add a new data source", "sync my warehouse tables", or wants to pick sync methods for each table. Walks through source-type discovery, credential validation, table discovery, per-table sync_type selection, and the final create call. Also covers picking a good prefix and wha

🧰 Not standalone — use together with posthog/posthog

setting-up-devbox

★ 35,336

by posthog

Guide a PostHog engineer through spinning up, connecting to, running commands on, and mirroring local code to a remote devbox (a Coder workspace running the full PostHog stack). Use when asked to set up a devbox, start or connect to a devbox, configure remote dev, get gh CLI / Claude Code authed on a devbox, run a command on a devbox, sync a local checkout so you can edit locally while the stack runs remotely (devbox:sync), or diagnose why a devbox command fails. Covers the tailnet prerequisite,

🧰 Not standalone — use together with posthog/posthog

setting-up-slack-app

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

signals

★ 35,336

by posthog

How to query the document_embeddings table for raw signal data using HogQL. Use when you need to perform semantic search over signals, fetch every signal that contributed to a specific report, or list signal types. For browsing the curated report layer (the Inbox) — listing reports, filtering by status/source, drilling into a single report by ID — use the `inbox-exploration` skill first; drop into this skill afterwards if the user wants the underlying observations.

🧰 Not standalone — use together with posthog/posthog

signals-scout-ai-observability

★ 35,336

by posthog

Signals scout for PostHog AI observability. Watches LLM traces for cost, latency, error, volume, and eval-performance regressions, sliced by the dimensions it discovers over time, and files each validated regression as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-feature-flags

★ 35,336

by posthog

Signals scout for PostHog feature flags. Watches the flag roster and the `$feature_flag_called` stream for evaluation cliffs, ghost flags, response-distribution shifts, and flag debt, and files each validated contradiction as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-product-analytics

★ 35,336

by posthog

Signals scout for core product-analytics flows — funnels, retention, lifecycle, stickiness, and paths. Watches the team's saved flows for a derived-rate regression (conversion or retention sliding) while entrants hold, and files it as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-replay-vision

★ 35,336

by posthog

Signals scout for PostHog Replay Vision scanners. Watches that enabled scanners keep observing (throughput / quota cliffs) and that what they see in aggregate gets surfaced (score shifts, recurring themes across sessions), and files each validated finding as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-revenue-analytics

★ 35,336

by posthog

Signals scout for PostHog revenue analytics. Watches for upstream failures (Stripe sync stalls, capture regressions), config drift, and goal-miss escalations, and files each validated finding as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-session-replay

★ 35,336

by posthog

Signals scout for PostHog session replay. Watches that sessions keep recording (capture cliffs) and that friction inside recordings — rage/dead-click clusters, error-after-interaction cohorts — gets surfaced, and files each validated cliff or cluster as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

simulate-new-user

★ 35,336

by posthog

Send synthetic first-time-visitor traffic to a URL and confirm that PostHog $pageview events fire. Use when a customer wants to verify that anonymous visitor tracking works, after deploying instrumentation changes, or when debugging "events not arriving" reports.

🧰 Not standalone — use together with posthog/posthog

simulate-returning-user

★ 35,336

by posthog

Send synthetic single-session multi-page traffic to a URL and confirm PostHog $pageview events fire across page views. Use when verifying that cookies persist correctly, that the same distinct_id is reused across navigations, or when debugging session-stitching issues.

🧰 Not standalone — use together with posthog/posthog

slack-post-format

★ 35,336

by posthog

Project the markdown briefing into a Slack mrkdwn-friendly condensed post. Load BEFORE the final `@posthog/slack-post-message` call, NOT at briefing start — the local markdown is the source of truth and is built first. This skill is just the projection.

🧰 Not standalone — use together with posthog/posthog

slack-thread-protocol

★ 35,336

by posthog

Conventions for replying in Slack — TL;DR first, evidence next, who to tag, when to start a new top-level message. Load before posting any reply.

🧰 Not standalone — use together with posthog/posthog

suppressing-noisy-errors

★ 35,336

by posthog

Create PostHog error tracking suppression rules to drop high-volume, low-value errors at ingestion. Use when the user asks "stop capturing this error", "drop browser extension errors", "ignore ResizeObserver loops", "suppress bot-driven errors", or wants to reduce ingestion cost from noisy unactionable errors. Identifies suppression candidates, scopes the filter tightly, decides between full suppression and sampling, and confirms the rule before creating it. Suppressed errors are dropped permane

🧰 Not standalone — use together with posthog/posthog

triaging-error-issues

★ 35,336

by posthog

Triage PostHog error tracking issues during a daily or on-call review. Use when the user asks "what's broken?", "what new errors do we have?", "show me top errors today", "what should I look at this morning", or wants a prioritized list of active issues to work on. Surfaces new and high-impact issues, ranks by users affected and recency, points at linked replays, and proposes next actions (investigate, assign, suppress, merge).

🧰 Not standalone — use together with posthog/posthog

triaging-visual-review-runs

★ 35,336

by posthog

Inspects PostHog Visual Review (VR) runs that gate PR merges with screenshot regression checks. Use when the user mentions "visual review", "VR", "snapshot diff", "screenshot test", "storybook regression", "playwright snapshot", asks why a PR is blocked or what changed visually, wants to triage the VR backlog, decide whether a snapshot diff is real vs flaky, or check whether a story has been changing across runs. Also invoke when a PR has a failing `visual-review` status check, when a PR comment

🧰 Not standalone — use together with posthog/posthog

tuning-incremental-sync-config

★ 35,336

by posthog

Change the sync configuration of an existing data warehouse schema — switch sync_type, pick a different incremental_field, set primary_key_columns, choose cdc_table_mode, or change sync_frequency. Use when the user asks "switch my orders table from full refresh to incremental", "this table is syncing too slowly / too frequently", "I need to pick a different incremental column", "set up CDC for this Postgres table", or when diagnosis of a failing sync pointed to an incremental-field or PK misconf

🧰 Not standalone — use together with posthog/posthog

cost-and-quota-analysis

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog