signals-scout-general

Detects cross-product correlations and unmonitored surfaces in PostHog project data and files inbox reports.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-general
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signals-scout-general
Source: https://github.com/PostHog/posthog-foss/tree/main/products/signals/skills/signals-scout-general
Command: npx skills add https://github.com/PostHog/posthog-foss --skill signals-scout-general

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PostHog projects generate data across many products (error tracking, session replay, logs, web analytics, feature flags, and more), but no single person watches all of it. This Skill acts as a generalist scout that continuously explores a PostHog project, finds cross-product correlations and surfaces that specialist scouts don't cover, and files actionable findings as inbox reports for humans to review.

Core Features & Use Cases

  • Project Coverage Mapping: Builds and maintains a durable coverage map of which PostHog products have live data, using the event taxonomy and MCP tool surface, so no product goes unwatched.
  • Cross-Product Correlation Detection: Validates hypotheses with concrete queries (trends, funnels, error tracking, SQL) and authors reports pairing two correlated data series side by side.
  • Deduplication & Memory: Uses a keyed scratchpad with prefix conventions (pattern:, noise:, dedupe:, report:, reviewer:) to avoid re-filing known issues and to route reports to resolved owners via suggested reviewers.
  • Use Case: A team runs PostHog with error tracking, web analytics, and session replay but no dedicated monitoring. The scout discovers a spike in $exception events correlating with a drop in checkout funnel conversion, confirms no existing inbox report covers it, and files a report with both charts assigned to the owning engineer.

Quick Start

Ask the scout to explore this PostHog project, find anything worth surfacing across products, and file it as an inbox report.

Frequently Asked Questions about signals-scout-general

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

FAQPage Schema
How do I monitor a PostHog project across multiple products automatically?

Run this generalist scout on a schedule. It builds a coverage map of which products have live data, rotates attention across surfaces each run, and files inbox reports only for validated findings a human should act on.

How does the scout avoid filing duplicate reports?

Before authoring, it searches the inbox with inbox-reports-list and checks its scratchpad for dedupe:, noise:, and addressed: entries. If a report already covers the topic, it edits that report with new evidence instead of creating a near-duplicate.

What MCP tools does the signals scout require?

It uses the signals-scout MCP family: project-profile-get, runs-list, runs-retrieve, scratchpad-search, scratchpad-remember, scratchpad-forget, emit-report, edit-report, and members-list, plus standard read-only analytics query tools like query-trends and execute-sql.

When does the general scout run versus specialist scouts?

When specialist scouts are running, the general scout focuses on cross-product correlations and surfaces no specialist covers. When no specialists are running, it covers the entire coverage map across all live products.

What kinds of findings does the scout skip as noise?

It skips single-user single-session errors, dev-environment exception bursts, sandbox-internal Docker errors, KEA store-path errors with single-session reach, and pre-known upstream provider rate limits, unless volume or shape changes meaningfully.