Agent Skills

managing-path-cleaning-rules

★ 35,336

by posthog

Inspects URL paths and proposes, tests, orders, and applies project-level path cleaning rules so dynamic segments (numeric IDs, UUIDs, slugs, dates) collapse into readable aliases. Use when the user says "clean the paths", "normalize URLs", "group similar pages", "too many distinct paths", "/users/123 and /users/456 are the same page", "set up path cleaning", or asks why a Web analytics or Paths breakdown is fragmented across thousands of nearly-identical URLs. Covers regex syntax (re2), alias p

🧰 Not standalone — use together with posthog/posthog

managing-reminders

★ 35,336

by posthog

Create and manage PostHog reminders — private, human-paced nudges that fire as in-app notifications on a schedule, optionally linked to a PostHog resource. Use when the user says "remind me to…", wants a one-off or recurring nudge (daily/weekly/monthly/yearly, a cron schedule, or a specific date/time), wants to be reminded to look at a dashboard, insight, experiment, feature flag, survey, notebook, replay, or error, or wants to list, change, or cancel their reminders. Covers when to pick a remin

🧰 Not standalone — use together with posthog/posthog

managing-subscriptions

★ 35,336

by posthog

Manage PostHog subscriptions — scheduled email, Slack, or webhook deliveries of insight or dashboard snapshots, optionally with an AI-written summary attached to each delivery. Use when the user wants to subscribe to an insight or dashboard, get an AI summary attached to those deliveries, check existing subscriptions, change delivery frequency, add or remove recipients, or stop receiving updates.

🧰 Not standalone — use together with posthog/posthog

optimizing-clickhouse-and-hogql-queries

★ 35,336

by posthog

Workflow for optimizing ClickHouse and HogQL queries. Use when a HogQL query, query runner, insight, or report is too slow; when a hand-written ClickHouse query (via `sync_execute` or in a migration) is too slow; when ClickHouse times out or hits memory limits; when investigating a slow `system.query_log` row; or when reviewing a proposed HogQL printer change for performance. Covers extracting the ClickHouse SQL, common smells (`FROM ... FINAL`, `JSONExtract` over properties, missing skip indexe

🧰 Not standalone — use together with posthog/posthog

planning-voice-agent-user-interviews

★ 35,336

by posthog

Plan a round of user interviews conducted by PostHog''s AI voice agent (a "robo interviewer") — the automated voice-agent interview product. Captures a UserInterviewTopic (who to target, what to ask, framing context, question list) and calls user-interview-topics-create. ONLY trigger when the user clearly wants an AI voice agent to actually run the interview calls (e.g. "set up robo user interviews", "have the voice agent interview these users"). Do NOT trigger for ordinary user research that do

🧰 Not standalone — use together with posthog/posthog

proposing-changes

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

querying-local-postgres

★ 35,336

by posthog

Run read-only SQL against the local Postgres app database (SELECT, EXPLAIN, EXPLAIN ANALYZE on SELECT). Default local URL postgres://posthog:posthog@localhost:5432/posthog; else DATABASE_URL. Use when querying the local DB, inspecting tables, debugging data, or analyzing query plans. Mutations are strictly forbidden.

🧰 Not standalone — use together with posthog/posthog

security-audit

★ 35,336

by posthog

Focused security audit of code, calibrated to surface real exploitable bugs and suppress theoretical findings. Use when the user asks to "audit", "security-audit", "find vulnerabilities", "check for IDOR/SSRF/XSS/injection", or wants a security review of a file, directory, branch diff, or PR. Covers access control, injection, auth/secrets, sensitive data, business logic, web boundary, and AI agent/LLM trifecta risks. Produces calibrated findings with data flow, exploit request, fix, and confiden

🧰 Not standalone — use together with posthog/posthog

querying-posthog-data

★ 35,336

by posthog

Required reading before writing any HogQL/SQL or calling execute-sql against PostHog. Use whenever the user wants to search, find, or do complex aggregations PostHog entities (insights, dashboards, cohorts, feature flags, experiments, surveys, hog flows, data warehouse, persons, etc.) and query analytics data (trends, funnels, retention, lifecycle, paths, stickiness, web analytics, error tracking, logs, sessions, LLM traces). Covers HogQL syntax differences from ClickHouse SQL, system table sche

🧰 Not standalone — use together with posthog/posthog

reading-an-agent

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

run-posthog

★ 35,336

by posthog

Start, inspect, and drive the PostHog dev stack. Use for /run and /verify on this repo — when asked to launch PostHog, check whether the stack is healthy, inspect a running process, or verify a UI change against the live app.

🧰 Not standalone — use together with posthog/posthog

runbook-memory

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

running-ci-preflight

★ 35,336

by posthog

Catch the deterministic CI failures reachable from your diff before pushing, with `hogli ci:preflight`. Use when the pre-push hook blocks a push, before reporting a task done, or after editing Python, serializers, migrations, workflows, or dependency manifests — to avoid burning a CI matrix on a failure you could catch locally (formatting, lint, broken lockfiles, OpenAPI drift, migration conflict, stale branch). Trigger terms: ci:preflight, preflight, pre-push checks, pre-push hook failed, "will

🧰 Not standalone — use together with posthog/posthog

safety-and-boundaries

★ 35,336

by posthog

Hard rules — what the Agent Builder MUST NOT do regardless of user request. Load IMMEDIATELY if a request feels like it crosses into raw-secret handling, unprompted promotion, irreversible deletion, or impersonation of another user.

🧰 Not standalone — use together with posthog/posthog

scene-menu-bar

★ 35,336

by posthog

Conventions for adding or editing the SceneMenuBar above a scene's <SceneTitleSection>. Use when adding new menu items, moving items between menus, gating behind feature flags, building a new scene's menubar, or wiring rich inputs (tags, combobox) into the bar.

🧰 Not standalone — use together with posthog/posthog

secrets-and-integrations

★ 35,336

by posthog

🧰 Not standalone — use together with posthog/posthog

signals-scout-apm

★ 35,336

by posthog

Signals scout for PostHog distributed tracing (APM / OpenTelemetry spans). Watches RED metrics per (service, operation) — error rate, p95 latency, request volume — for regressions, new error signatures, and traffic cliffs, and files each validated regression as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-csp-violations

★ 35,336

by posthog

Signals scout for Content Security Policy violation reports. Watches `$csp_violation` events for blocked-URL clusters, per-directive bursts, post-deploy regressions, and suspicious third-party domains, and files each validated cluster as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-customer-analytics

★ 35,336

by posthog

Signals scout for PostHog Customer analytics (Accounts). Watches per-account engagement for churn-risk shapes — engagement cliffs, dormancy, champion departure — and the expansion inverse, weighted by commercial ownership, and files each validated risk as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-data-pipelines

★ 35,336

by posthog

Signals scout for PostHog data pipelines — CDP destinations and transformations, batch exports, and hog flows. Watches for delivery failures, degraded functions, and stalled exports against each pipeline's baseline, and files each validated delivery contradiction as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-data-warehouse

★ 35,336

by posthog

Focused Signals scout for PostHog projects importing external data into the warehouse. Watches the import side — external data sources, their per-table sync schemas, webhook push channels, and materialized views — for the moments an import quietly stops keeping its promise: a source connection in Error (cascading to every table under it), a schema Failed or stuck Running, a schema that reads Completed but has fallen behind its own sync cadence (a silent, growing data gap), a webhook push channel

🧰 Not standalone — use together with posthog/posthog

signals-scout-error-tracking

★ 35,336

by posthog

Signals scout for PostHog error tracking. Watches `$exception` bursts, stuck loops, multi-fingerprint clusters, and status regressions, and files each validated issue as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-experiments

★ 35,336

by posthog

Signals scout for PostHog A/B experiments. Watches running experiments for validity threats (sample ratio mismatch, contamination, exposure stalls, mid-run flag mutations) and lifecycle drift (zombies, decided-but-running), and files each validated validity threat as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog

signals-scout-inbox-validation

★ 35,336

by posthog

Follow-up Signals scout for the inbox itself. After a deployment soak window, re-measures the problems behind recently resolved reports and files a report when a fix didn't hold, plus a gated escalation check on dismissed reports.

🧰 Not standalone — use together with posthog/posthog

signals-scout-insight-alerts

★ 35,336

by posthog

Signals scout over a project's own configured insight alerts. Reads each alert's recent firing history and files a report for the firings a human likely missed — especially ones the standard notification path stayed silent on.

🧰 Not standalone — use together with posthog/posthog

signals-scout-logs

★ 35,336

by posthog

Signals scout for PostHog logs. Watches for volume bursts, severity-distribution shifts, service silence, fresh message patterns, and trace-correlated bursts.

🧰 Not standalone — use together with posthog/posthog

signals-scout-mcp-tool-calls

★ 35,336

by posthog

Signals scout for PostHog MCP tool calls. Watches $mcp_tool_call telemetry for tools that need improvement — high, broad-reach failure rates, retry/hammering that betrays a confusing schema, slow or context-bloating responses — and files each validated tool-quality finding as a report in the inbox; otherwise writes durable memory and closes out empty. Adapts to which fields the project actually captures.

🧰 Not standalone — use together with posthog/posthog

signals-scout-observability-gaps

★ 35,336

by posthog

Signals scout for observability gaps — significant event volumes with no insight, dashboard, or alert coverage. Files a report recommending new insights, dashboards, or alerts as the team's product evolves.

🧰 Not standalone — use together with posthog/posthog

signals-scout-skills-store

★ 35,336

by posthog

Skill-hygiene scout for the team's PostHog skills store, read entirely via the MCP skill tools. Watches recently-changed skills — plus a slow rotation over the most-used, highest-leverage ones — for statically-verifiable authoring violations: vague descriptions, bloated bodies, dead bundled-file links, kitchen-sink scope, committed secrets. Files each non-compliant skill as a report in the inbox, with the copy-ready fix inside.

🧰 Not standalone — use together with posthog/posthog

signals-scout-surveys

★ 35,336

by posthog

Signals scout for PostHog surveys. Watches active surveys for score regressions, response-volume drops, abandonment spikes, and targeting drift, and aggregates open-text responses into recurring themes — filing each as a report in the inbox.

🧰 Not standalone — use together with posthog/posthog