signals-scout-error-tracking
SkillSignals 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-trackingWhat 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 readSignals 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-scouts → references/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_count ≪ count / 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$exceptionis absent entirely) orpattern: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 →cardputer-buddy
Iterate on the Cardputer-Adv MicroPython app bundle (Claude Buddy, Snake, Hello) after the device is already provisioned via m5-onboard. Use when the user wants to add a new app, push a single changed .py without re-flashing, watch device serial logs, or run a one-shot REPL command. Trigger on "add
32.8K stars
planning-with-files
Persistent file-based planning for AI coding agents and long-running tasks. Crash-proof markdown plans, session recovery after /clear and compaction, per-turn re-injection against context rot, deterministic completion gate. Manus-style. Claude Code, Codex, Cursor, Kiro, OpenCode and 60+ agents via the Agent Skills standard.
25.8K stars
troubleshoot
Diagnose and fix a failing or misbehaving Atomic Agents app — import errors, schema validation failures, empty or malformed LLM output, provider role/mode errors, history and context problems, MCP transport errors. Use when the user reports an error, traceback, or wrong behavior in atomic-agents cod
6.1K stars
Subagents
All subagents →code-explorer
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development
32.8K stars
retro-analyst
Reliability pattern analyst for retrospectives, recurring-incident clustering, and systemic improvement recommendations.
1 stars
incident-investigator
Deep production-incident investigator for root-cause analysis, evidence gathering, and remediation planning beyond the initial response brief.
1 stars
Plugins
All plugins →chrome-devtools-mcp
Control and inspect a live Chrome browser from your coding agent. Record performance traces, analyze network requests, check console messages with source-mapped stack traces, and automate browser actions with Puppeteer.
47.9K stars
deepeval
Skills for adding DeepEval evaluations, tracing, datasets, Confident AI reports, and iterative improvement loops to AI applications.
17.3K stars
aws-agents-for-devsecops
Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent.
2.2K stars
MCP Servers
All mcp servers →monitor
BetterDB MCP server - Valkey observability for Claude Code and other MCP clients
1.2K stars
MikroMCP
MCP server for MikroTik RouterOS: typed tools, dry-run, RBAC, audit logs, and rollback.
42 stars
suitecrm-mcp
Open-source MCP gateway for SuiteCRM - 24 CRM tools, OAuth2/OIDC auth, multi-entity, observability.
1 stars
Commands
All commands →help
Get help with FiftyOne skills, understand available workflows, and troubleshoot setup issues
32.8K stars
troubleshoot-connector
Troubleshoot ZPA App Connector issues -- enrollment, connectivity, upgrades, and resource utilization.
investigate-sandbox
Investigate ZIA Sandbox file analysis -- check sandbox reports, quota, SSL prerequisite, and diagnose file block/quarantine issues.