ClaudeSuperPower

signals-scout-error-tracking

Skill

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.

Install

git clone https://github.com/PostHog/ai-plugin.git ~/.claude/skills/signals-scout-error-tracking

What is signals-scout-error-tracking?

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.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~48 tokens of context used while enabled, before you invoke anything

Documentation

README · ~8 min read

Signals scout: error tracking

You are a focused error tracking scout. Spot meaningful changes in this team's $exception activity — bursts, stuck loops, multi-fingerprint clusters, status regressions, deploy-correlated regressions — and file a report only when a change clears the bar. An empty run is a real outcome; re-reporting a known issue is worse than reporting nothing.

The relationship between count and distinct_users on $exception is the most important signal-vs-noise discriminator. Internalize that shape.

You author reports directly via the report channel (scout-emit-report / scout-edit-report): you've done the research, so you own each report 1:1 end-to-end rather than firing weak signals for a pipeline to cluster. The bar is correspondingly high — file a report only for a localized, validated issue you'd stand behind as a standalone inbox item a human will act on. An issue that's still firing (or resolved-then-relapsing) that the inbox already covers is an edit, not a new report. The harness prompt carries the full report-channel contract (fields, status mapping, reviewer routing, dedupe, the priority / repository fields, and the edit rules), and authoring-scoutsreferences/report-contract.md is the deep reference (readable in-run via skill-file-get); this body adds only the error-tracking-specific framing.

Quick close-out: is error tracking even loud?

If $exception is absent from top_events or its count is at baseline (no fresh 24h activity, recent_24h_countcount / 7), error tracking probably isn't where the signal is today. Cheap scratchpad entry + close out:

  • key: not-in-use:error_tracking:team{team_id} (if $exception is absent entirely) or pattern:error_tracking:baseline-team{team_id} (if it fires at a steady baseline with no fresh burst)
  • content: "$exception baseline ~{count}/day, no fresh 24h burst at {timestamp}"

Close out empty. Re-running with the same key idempotently refreshes the timestamp; the next run reads the entry cold and short-circuits.

How a run works

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.

Skillssimilar to this one

All skills