skills.rest
PostHog
PostHogOFFICIAL
Explore all skills by this author →
Website𝕏@PostHogGitHub

signals-scout-health-checks

Bundles PostHog health-check issues by root cause and files prioritized review reports.

713|118|Updated Aug 11, 2020
Search Tags:#health checks#issue triage#Root Cause Analysis#PostHog#alert deduplication#analytics monitoring#report authoring
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-health-checks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: signals-scout-health-checks
Source: https://github.com/PostHog/posthog-foss/tree/main/products/signals/skills/signals-scout-health-checks
Command: npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-health-checks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PostHog projects accumulate dozens of active health-check issues (broken capture, outdated SDKs, failing warehouse syncs), and raw per-issue alerting drowns reviewers in noise. This Skill reads the active health issues and distills them into a small number of well-framed, deduplicated reports a reviewer can act on.

Core Features & Use Cases

  • Issue triage and bundling: Reads active health issues via health-issues-summary / health-issues-list / health-issues-get, groups them by kind and root cause, and weights them by severity, blast radius, and agent-fixability.
  • Report authoring with dedupe: Authors or edits inbox reports through scout-emit-report / scout-edit-report, using scratchpad keys (dedupe:health:*, report:health:*) so persistent issues become edits rather than duplicates.
  • Blast-radius corroboration: Confirms real impact with query-trends and execute-sql (e.g. checking $pageview volume or SDK version share) before assigning priority.
  • Use Case: A project shows 95 external_data_failure issues; the scout traces them to one invalidated replication slot and files a single human-framed report instead of 95 separate alerts.

Quick Start

Run the signals-scout-health-checks skill to review this project's active health issues and file reports for the findings worth acting on.

Frequently Asked Questions about signals-scout-health-checks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage PostHog health-check issues without alert noise?▼

Run this scout to read active health issues and bundle them by kind and root cause into a few reports. It weights findings by severity, real traffic impact, and whether an agent can fix them, so dozens of related issues collapse into one actionable finding.

How does the scout avoid filing duplicate health reports?▼

It writes scratchpad entries keyed on stable issue IDs and kinds, and checks the inbox before authoring. A still-active issue or a growing cluster becomes an edit to the existing report rather than a new one.

Which PostHog health issues does the scout skip?▼

It skips dismissed issues, transient flicker that auto-resolves between runs, low-traffic web-instrumentation warnings, and bulk external_data_failure clusters that need human-held credentials, except a single high-impact shared root cause.

Can the scout verify whether a health warning actually matters?▼

Yes. It corroborates blast radius with query-trends and execute-sql, for example checking recent $pageview volume before reporting a reverse_proxy warning or measuring traffic share on an outdated SDK version before prioritizing it.

What permissions does the health-checks scout need?▼

It needs read-only analytics and health-issues MCP tools plus signal_scout_internal:write for the scratchpad and signal_scout_report:write for the report channel. It runs inside the PostHog Signals agent sandbox and cannot modify project configuration.

Related Skills

Explore More Data & Analytics Skills→
phrazzldphrazzld
13

posthog

Audits and fixes PostHog event tracking, environment checks, and integration health.

Community
Advanced
videogorlvideogorl
3

known-issues

Catalog known issues and technical debt across Ensemble project components.

Community
Advanced
langwatchlangwatch
3.5k

debug-with-langwatch

Diagnose production LLM agent failures by inspecting LangWatch traces, spans, and monitor scores.

Official
Intermediate
iblaiiblai
15

iblai-notification

Add a notification bell and Inbox/Alerts center to Next.js apps using iblai SDK components.

Official
Intermediate