posthog
194 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
posthogdiagnosing-missing-recordings
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.
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogdiagnosing-stacktrace-symbolication
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM). The PostHog symbol-set lookup flow is universal across platforms; build-tool and artifact details live in per-platform references (JavaScript is fleshed out, others come as we encounter them). Use when stack frames stay minified or obfuscated after symbols are uploaded, PostHog symbol sets show lastused bu
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogdownloading-batch-export-files
Export PostHog events, persons, sessions, or the results of a HogQL query on demand and download the resulting files. Use when the user asks to download/export raw PostHog data, export HogQL query results, create a one-off file export, fetch a Parquet or JSONLines export, or use the filedownloadbatchexports API. Covers starting the export with MCP, polling completion, and downloading via the existing REST redirect endpoint.
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogexploring-autocapture-events
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 elementschain, wants to build a trend or funnel filtered by clicks or other autocapture interactions, asks which properties autoc
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogexploring-endpoint-execution-logs
Explore and diagnose a PostHog endpoint's execution logs — error messages, failed runs, cache misses, slow runs, or unexpected row counts during endpoint invocations. Use when the user says "my endpoint is failing", "show me the logs for endpoint X", "what error did endpoint Y produce", "why did endpoint Z return no rows", "is this endpoint hitting cache", or "check the last N runs". Focused on a single named endpoint's runtime log entries, not project-wide auditing or query performance profilin
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogexploring-llm-costs
Investigate LLM spend in PostHog — total cost over time, cost by model, provider, user, trace, or custom dimension, token and cache-hit economics, and cost regressions. Use when the user asks "how much are we spending on LLMs?", "which model / user / feature is most expensive?", "why did cost spike?", wants to build a cost dashboard or alert, or pastes a trace URL and asks about its cost.
- instalaciones
- 1
- GitHub Stars
- 81
- Actualizado
- 10 sept
posthogexploring-llm-evaluations
Investigate AI observability evaluations — hog (deterministic code-based), llmjudge (LLM-prompt-based), and sentiment (user-message sentiment). Find existing evaluations, inspect their configuration, run them against specific generations, query individual results, and set up scheduled reports on an evaluation. 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 LLM-judge prompt, inspe
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogexploring-llm-traces
Debug and inspect LLM/AI agent traces using PostHog's MCP tools. Use when the user pastes a trace or session URL (e.g. /ai-observability/traces/ or /ai-observability/sessions/ ), asks to debug a trace, figure out what went wrong, check if an agent used a tool correctly, verify context/files were surfaced, inspect subagent behavior, investigate LLM decisions, or analyze token usage and costs. Also use when raw SQL/HogQL against events.properties.$aiinput / $aioutputchoices returns empty — message
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogexploring-mcp-intent-clusters
Explore PostHog MCP intent clusters — agent goals grouped by semantic similarity, with each cluster's tool distribution and error rates, plus the tool-centric pivot (capture rate per intent, discovery rate against the advertised catalog, description fit, tool overlaps). Use when the user asks "what are agents trying to do with the MCP?", "group the intents", "which goals fail most?", "what does each cluster route to?", "when agents have this intent do they find my tool?", "which tools get mixed
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogexploring-mcp-tool-quality
Investigate the quality of PostHog MCP tool calls — error rates, latency, reach, and which tools are failing or slow. Use when the user asks "which MCP tool has the highest error rate?", "what's the slowest tool?", "which tools fail most often?", "how reliable is tool X?", wants a tool-quality matrix, or pastes an MCP analytics tool-quality / dashboard URL and asks what it shows.
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogexploring-mcp-tool-usage
Starting point for exploring how a PostHog MCP server's tools are used — routes a broad question to the typed tool that answers it. Use when the user asks "how is my MCP doing?", "what should I look at?", "explore my tool calls", "who uses my MCP tools?", "what are agents doing with the MCP?", or pastes an MCP analytics URL without a specific question. Offers a menu of questions, each backed by a query tool, then hands off to the focused skill.
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogexploring-replay-vision-observations
Guides agents through pulling a Replay Vision scanner's observations, reading the findings, and acting on them — summarizing patterns across sessions, drilling into individual recordings, and turning real, corroborated issues into PostHog tasks, insights, or an investigating-replay hand-off.\nTRIGGER when: user wants to pull/read/triage Replay Vision observations, asks \"what has my scanner found\", wants to act on or summarize scanner findings, turn observations into tasks/work, or points at a
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogexploring-scouts
How to explore and make sense of PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to understand what scouts they have, how each one is behaving, and whether the fleet is actually working. Covers surveying the fleet and its schedules, reading recent scout runs and drilling into a single run's reasoning, inspecting the durable scratchpad memory the fleet has built up, tracing a run to the reports it wrote or edited, a
- instalaciones
- 1
- GitHub Stars
- 81
- Actualizado
- 10 sept
posthogfeature-usage-feed
Set up an LLM-judge evaluation that extracts canonical use cases for a PostHog feature at scale and streams the results to a Slack channel as a live feed. Use when someone wants to understand how users are actually using a specific AI/LLM-powered feature in production — what they're investigating, what questions they're trying to answer, and what patterns surface — without manually reading hundreds of traces. Assumes the feature emits $aigeneration and $aievaluation events with $sessionid linkag
- instalaciones
- 1
- GitHub Stars
- 81
- Actualizado
- 10 sept
posthogfinding-replay-for-issue
Finds the most informative session recording linked to an error tracking issue. Use when a user has an error tracking issue ID and wants to watch a replay showing what the user was doing when the error occurred. Ranks linked sessions by recency, activity score, and journey completeness, then summarizes the pre-error context. Replaces blind session picking from potentially hundreds of linked recordings.
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogfinding-sessions-to-watch
Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching. Use when the user asks which sessions or replays to watch, wants help finding interesting / useful recordings, says they don't know where to start in session replay, or wants to watch sessions about a goal (signup, pricing, onboarding, checkout, a feature, rageclicks, errors, mobile, a specific person) without naming exact filters. Turns a vague intent into a focused
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthogformatting-insight-axes
Pick the right y-axis unit when creating or updating an insight via posthog:insight-create or posthog:insight-update — both TrendsQuery (trendsFilter.aggregationAxisFormat) and SQL insights (DataVisualizationNode, chartSettings.yAxis[].settings.formatting). Use when the agent is about to add a formula purely to convert units (e.g. dividing seconds by 60 to display minutes), when a mathproperty or SQL column is a duration, currency, ratio, or large count, or whenever the user mentions "format the
- instalaciones
- 1
- GitHub Stars
- 81
- Actualizado
- 10 sept
posthogimproving-mcp-tools
Run an improve-my-MCP campaign: an autoresearch-style loop that measures the MCP agent experience with the eval harness, picks the highest-impact tool problem from production data, makes one bounded fix, and keeps it only if before/after scores improve. Use when asked to "improve my MCP", run an MCP improvement campaign, fix tool discoverability or descriptions based on evidence, or prepare an eval-backed PR for a tool change. Every shipped change must carry eval evidence; guardrails below are h
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthoginbox-exploration
Explore PostHog's Inbox and act on what it surfaces — the place where signal reports cluster into actionable issues and trends. Use when the user asks "what's in my inbox?", "what should I look at?", "which reports are actionable?", "what's PostHog flagged recently?", asks about a specific report by ID or title, wants to act on / fix / implement a report (turn it into a PR), wants to resolve, dismiss, or snooze a report, or wants to see which signal sources are configured. Covers listing, filter
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthoginstrument-error-tracking
- Add PostHog error tracking to capture and monitor exceptions. Use after implementing features or reviewing PRs to ensure errors are tracked with stack traces and source maps. Also handles initial PostHog SDK setup if not yet installed.
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthoginstrument-feature-flags
- Add PostHog feature flags to gate new functionality. Use after implementing features or reviewing PRs to ensure safe rollouts with feature flag controls. Also handles initial PostHog SDK setup if not yet installed.
- instalaciones
- 1
- GitHub Stars
- 81
- Actualizado
- 10 sept
posthoginstrument-integration
- Add PostHog SDK integration to your application. Use when setting up PostHog for the first time or reviewing PRs that need PostHog initialization. Covers SDK installation, provider setup, and basic configuration for any framework.
- instalaciones
- 1
- GitHub Stars
- 80
- Actualizado
- 4 sept
posthoginstrument-metrics
- Add PostHog metric capture to track counters, gauges, and histograms. Use after implementing features or reviewing PRs to ensure key operations are measured, or when asked to add metrics, counters, or track a value over time. Also handles mirroring existing Prometheus/StatsD/OpenTelemetry metrics into PostHog and initial OTLP exporter setup.
- instalaciones
- 1
- GitHub Stars
- 81
- Actualizado
- 10 sept
posthoginstrument-product-analytics
- Add PostHog product analytics events to track user behavior. Use after implementing new features or reviewing PRs to ensure meaningful user actions are captured. Also handles initial PostHog SDK setup if not yet installed.
- instalaciones
- 1
- GitHub Stars
- 81
- Actualizado
- 10 sept