Agent Skills

designing-mcp-surfaces

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

gating-production-deploys

★ 35,336

by posthog

Use when adding or editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action) or dispatches a production deploy (a `commit_state_update` repository_dispatch to PostHog/charts). Those run from a single canonical deploy repo, gated by the CD_DEPLOY_ENABLED variable. Does NOT apply to workflows that publish GitHub releases, npm, crates, or Homebrew — those stay on the public repo.

🧰 Not standalone — use together with posthog/posthog

managing-endpoint-versions

★ 35,336

by posthog

Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without bumping the version", or anything involving the version history. Calls out today's limitations honestly: there is no pointer flip; "rollback" means forking the old query into a new

🧰 Not standalone — use together with posthog/posthog

platform-mental-model

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

querying-ai-observability

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

running-and-evaluating-tests

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

signals-scout-anomaly-detection

★ 35,336

by posthog

Signals scout that watches a project's most-viewed dashboards and insights for recent anomalies — bursts, drops, flat-lines, and trend breaks scored against each insight's own seasonality-matched baseline. Files each anomaly as a finished 1:1 inbox report on the report channel (emit_report / edit_report) rather than a weak signal.

🧰 Not standalone — use together with posthog/posthog

signals-scout-general

★ 35,336

by posthog

Cross-product Signals scout. Looks for cross-product correlations and explores the surfaces the per-product specialist scouts don't cover.

🧰 Not standalone — use together with posthog/posthog

signals-scout-health-checks

★ 35,336

by posthog

Signals scout over PostHog's own health checks. Reads the project's active health issues, bundles them by kind, weights by blast radius, and files the ones genuinely worth acting on as reports in the inbox.

🧰 Not standalone — use together with posthog/posthog

triage-playbook

★ 35,336

by posthog

Structured triage flow — phases for context gathering, hypothesis, and reporting. Load when starting an investigation.

🧰 Not standalone — use together with posthog/posthog

survey-sdk-audit

★ 35,336

by posthog

Audit PostHog survey SDK features and version requirements

🧰 Not standalone — use together with posthog/posthog

exploring-llm-evaluations

★ 35,336

by posthog

Investigate AI observability evaluations — `hog` (deterministic code-based), `llm_judge` (LLM-prompt-based), and `sentiment` (user-message sentiment). Find existing evaluations, inspect their configuration, run them against specific generations, query individual results, and generate AI-powered summaries for boolean pass/fail runs. Use when the user asks to debug why an evaluation is failing, surface common failure modes, compare results across filters, dry-run a Hog evaluator, prototype a new L

🧰 Not standalone — use together with posthog/posthog

adding-project-secret-api-key-auth

★ 35,336

by posthog

How to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential. Use when adding PSAK support to a viewset action, allowing a new scope for PSAKs, handling synthetic users (ProjectSecretAPIKeyUser), or choosing PSAK-aware rate throttles. Trigger terms: PSAK, ProjectSecretAPIKey, project secret API key, phs_ token, service auth, programmatic endpoint auth.

🧰 Not standalone — use together with posthog/posthog

assessing-heatmaps

★ 35,336

by posthog

Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click / rageclick / scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements.\nTRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap

🧰 Not standalone — use together with posthog/posthog

auditing-endpoints

★ 35,336

by posthog

Audit every endpoint in a PostHog project for staleness, failed materialisations, and unused materialised versions. Use when the user asks "what endpoints can I clean up?", "are any of my endpoints broken?", "which materialised versions are still being called?", or wants a one-shot cleanup pass over the Endpoints product. Produces a prioritised report grouped by issue type, with recommended actions but does not modify anything without explicit confirmation.

🧰 Not standalone — use together with posthog/posthog

auditing-the-fleet

★ 35,336

by posthog

The fleet-wide audit — sweep every agent, mine recent sessions for failures/anomalies, classify root causes, and branch a DRAFT proposal per fix (never freeze/promote); write a report to memory. Load when asked to audit all agents or what's underperforming.

🧰 Not standalone — use together with posthog/posthog

auditing-warehouse-source-health

★ 35,336

by posthog

Audit the health of a PostHog project's data warehouse sources and syncs — find every broken or degraded source connection, sync schema, and webhook channel. Use when the user asks "why are my imports failing?", "what's broken with my sources?", "why is my warehouse data stale?", or wants a one-shot triage of source/sync health before deciding where to dig in. Produces a prioritized report grouped by severity, with recommended next steps. For materialized-view health use `auditing-warehouse-view

🧰 Not standalone — use together with posthog/posthog

auditing-warehouse-view-health

★ 35,336

by posthog

Audit the health of a PostHog project's materialized views (saved queries) — find every failed materialization and flag unused or stale materialized views that cost storage and compute. Use when the user asks "which of my views are broken?", "why is this materialized view failing?", "are any of my views wasting compute?", or wants a one-shot triage of view health. For source/sync health use `auditing-warehouse-source-health`.

🧰 Not standalone — use together with posthog/posthog

authenticating-as-the-user

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

authoring-error-tracking-alerts

★ 35,336

by posthog

Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack/webhook/Linear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedup against existing alerts, and shipping with the canonical message body shape.

🧰 Not standalone — use together with posthog/posthog

authoring-log-alerts

★ 35,336

by posthog

Author useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination.

🧰 Not standalone — use together with posthog/posthog

authoring-new-agents

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

copying-flags-across-projects

★ 35,336

by posthog

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

🧰 Not standalone — use together with posthog/posthog

authoring-scouts

★ 35,336

by posthog

How to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak a scout's schedule or dry-run posture, or write a brand-new scout from scratch for a specific use case (a custom event, a product surface no canonical scout covers). Covers the scout SKILL.md anatomy, the report contract

🧰 Not standalone — use together with posthog/posthog

briefing-template

★ 35,336

by posthog

Pinned output schema for the morning briefing markdown file. Defines section order, what each section contains, when to omit, and how to tag individual items. Load AT THE START of every briefing build so day-to-day output looks the same. The user's eye is trained on this shape.

🧰 Not standalone — use together with posthog/posthog

building-workflows

★ 35,336

by posthog

Build, edit, test, enable, and monitor PostHog workflows over MCP. Author the action/edge graph so it runs and opens cleanly in the visual editor, then change drafts surgically with patch operations. Use when asked to build, set up, automate, change, fix, or debug a workflow, campaign, broadcast, drip sequence, or event-triggered automation in the workflows product.

🧰 Not standalone — use together with posthog/posthog

capturing-kudos

★ 35,336

by posthog

How to read a kudos out of a message — pull the recipient handle(s), the praise, and themes; decide when to ask ONE clarifying question vs record straight away. Load at the start of every capture.

🧰 Not standalone — use together with posthog/posthog

cleaning-up-stale-feature-flags

★ 35,336

by posthog

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.

🧰 Not standalone — use together with posthog/posthog

clickhouse-autoresearch-campaign

★ 35,336

by posthog

Run a ClickHouse query optimization campaign on one git branch using pi-autoresearch, dynamic lanes and hypotheses, baseline result capture, correctness checks, and stagnation-aware lane/campaign review.

🧰 Not standalone — use together with posthog/posthog

cost-and-quota-analysis

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog