RADAR DE SKILLS · GITHUB / posthog

posthog · Agent Skills

194 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

posthog

Oficial

investigate-metric

Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries. Use when the user reports an anomaly, asks "why did X change?", or needs root-cause analysis for a trend, funnel, retention, stickiness, or lifecycle metric.

instalaciones: 1
GitHub Stars: 81
Actualizado: 10 sept

investigating-ci-failures

Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed. Use for "who broke master", "why did this test fail in CI", "is this failure my PR's fault or everyone's", "is this test flaky or actually broken", "when did this failure start". Works from the engineeringanalytics warehouse views (engineeringanalyticscifailures, engineeringanalyticscijobhistory) plus the CI failure logs. Not for aggregate CI health, cost, or merge bottlenecks (use d

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

investigating-metric-anomalies

Investigates server/infrastructure metric anomalies in PostHog Metrics — from "this metric is rising/dropping/spiking" or a fired alert to a probable cause with evidence. Use when asked why a metric looks wrong (ingestion lag rising, error rate spiking, latency degrading, queue depth growing, throughput dropping), when an alert fires on an OTel/Prometheus metric, or for any incident triage that starts from a metric symptom. Composes characterize-metric-anomaly, query-metrics, and metric-names-li

instalaciones: 1
GitHub Stars: 81
Actualizado: 10 sept

investigating-replay

Investigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues in one pass. Use when a user provides a recording or session ID and wants to understand what happened — who the user was, what they did, what errors occurred, and whether there are related error tracking issues. Replaces the manual chain of session-recording-get, persons-retrieve, execute-sql, and query-error-tracking-issues-list.

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

managing-endpoint-versions

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

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

managing-path-cleaning-rules

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

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

managing-reminders

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

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

managing-streamlit-apps

Create, deploy, and operate Streamlit apps in PostHog via the streamlit-apps MCP tools — create an app, set its source, start and stop its sandbox, poll status, list versions, delete, and share the app with humans via its PostHog URL. Use when asked to "create a streamlit app", "deploy a data app", "ship a dashboard app", "restart/stop my app", "why is my app not running", or "give me a link to the app".

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

managing-subscriptions

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.

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

modeling-product-usage-metrics

Build reusable product-usage and engagement models — retention, stickiness, and lifecycle — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model, define, or compute whether users come back (retention / churn), how frequently they engage (stickiness / power users / DAU-WAU-MAU ratio), or the composition of the active base (new / returning / resurrecting / dormant lifecycle). These three are one engagement family sharing a start-event/return-e

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

modeling-revenue-metrics

Build reusable revenue models — MRR, ARR, gross revenue, new/expansion/contraction/churn, ARPU, LTV, and per-customer/per-account revenue — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model, define, or compute recurring revenue, monthly/annual recurring revenue, churn or retention of revenue, lifetime value, average revenue per user, or revenue by customer, cohort, product, or currency. On PostHog, build on the managed revenueanalytics vi

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

planning-voice-agent-user-interviews

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

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

querying-canvas-data

Get PostHog data into a canvas correctly: the host-injected ph SDK (loadInsight, query, capture, state, openExternal, navigate), the data hierarchy (saved insights first, typed query nodes second, inline HogQL last), verifiability (insight-backed metrics link their saved insight in PostHog; ad-hoc queries expose the exact query that ran), per-insight-type result shapes, progressive per-query loading, date-range wiring, and event capture from a canvas. Use whenever a canvas shows metrics, charts,

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

querying-posthog-data

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). Also the first stop for a governed business or telemetry measure (MRR,

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

resolving-ingestion-warnings

Diagnoses and resolves PostHog ingestion warnings — problems recorded while ingesting events (dropped events, rejected person merges, oversized payloads, invalid data). Use when a user asks why events are missing, dropped, or undercounted, why identify/alias calls don't work or accounts stay duplicated, why person or group properties aren't updating or profiles look inflated, why recordings have gaps, heatmaps are empty, LLM token counts are missing, why cookieless events vanish, or whenever the

instalaciones: 1
GitHub Stars: 81
Actualizado: 10 sept

setting-up-a-data-warehouse-source

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 synctype selection, and the final create call. Also covers picking a good prefix and what

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

setting-up-data-catalog

Populates and maintains a project's data catalog (semantic layer): canonical metrics, trust marks (certifications) on warehouse tables/views, and reviewed table relationships. Use when asked to set up / seed / bootstrap the data catalog or semantic layer, to catalog a project's metrics, to certify or deprecate data sources, to propose or review table joins, or to work through the proposal review queue. To use an existing catalog to answer a business-number question, see querying-posthog-data ins

instalaciones: 1
GitHub Stars: 81
Actualizado: 10 sept

setting-up-support-slack-locally

Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back. Use when the user wants to test the conversations Slack integration locally, hits "Support Slack OAuth client ID is not configured", gets a white screen or "Network error" on the OAuth callback, or asks how to set SUPPORTSLACKAPPCLIENTID / a tunnel for supporthog Slack events. Covers the Slack app + scopes, the SUPPORTSLACK dynamic settings, and

instalaciones: 1
GitHub Stars: 81
Actualizado: 10 sept

signals

How to query the documentembeddings 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.

instalaciones: 1
GitHub Stars: 81
Actualizado: 10 sept

signals-scout-ai-observability

Signals scout for PostHog AI observability. Watches LLM traces for cost, latency, error, volume, and eval-performance regressions.

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

signals-scout-conversations

Signals scout for PostHog Conversations (support inbox). Watches $conversation ticket- lifecycle events for SLA breach steps, first-response latency blowouts, backlog imbalance, and channel or assignment concentration.

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

signals-scout-customer-analytics-billing-and-usage

Signals scout for per-account product-mix shifts. Watches each staked account's usage and forecasted MRR per product for one product dropping or spiking against its own baseline while the account total holds.

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

signals-scout-data-warehouse

Signals scout for warehouse imports. Watches external data sources, sync schemas, webhook push channels, and materialized views for failures, silent staleness, and row-volume cliffs, and suggests materialization candidates from recurring query-log hot spots.

instalaciones: 1
GitHub Stars: 80
Actualizado: 4 sept

signals-scout-error-tracking

Signals scout for PostHog error tracking. Watches $exception bursts, stuck loops, multi- fingerprint clusters, and status regressions.

instalaciones: 1
GitHub Stars: 81
Actualizado: 10 sept

1 Archivos

Ver detalles →