CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

signals-scout-error-tracking

Signals scout for PostHog error tracking. Watches `$exception` bursts, stuck loops, multi- fingerprint clusters, and status regressions.

60

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./products/signals/skills/signals-scout-error-tracking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable, well-structured scout prompt with concrete tool calls, SQL, and memory-key formats throughout, and it practices good progressive disclosure by offloading generic report mechanics to a deep reference. Its only weak spots are mild count/users-framing repetition and the absence of an explicit validate→fix→retry loop.

DimensionReasoningScore

Conciseness

The body is dense and operational (exact tool names, key-prefix formats, SQL fragments) and mostly avoids explaining concepts Claude already knows, though the count-vs-distinct_users framing is restated across the intro, the shape table, and the Explore section and could be tightened slightly.

4 / 5

Actionability

It provides copy-paste-ready, fully executable guidance — exact MCP tool calls with parameters (`query-error-tracking-issues-list` filtered to `status=active`, sort by `last_seen_at`), concrete SQL (`event = '$exception' AND properties.$exception_issue_id = '<id>'` grouped by `toStartOfHour(timestamp)`), and exact scratchpad key formats — covering the common cases.

5 / 5

Workflow Clarity

The run is a clearly sequenced cycle (Get oriented → Profile shape → Explore → Save memory → Decide → Close out) with explicit checkpoints (search the inbox and scratchpad `noise:`/`addressed:`/`dedupe:` entries before authoring, edit-vs-author rules, 'When to stop'), though there is no formal validate→fix→retry feedback loop, leaving a minor validation gap.

4 / 5

Progressive Disclosure

The body is well-sectioned and deliberately pushes generic report mechanics out to `references/report-contract.md` (clearly signaled and one level deep), keeping only error-tracking-specific framing inline; the only gap is that the referenced file lives in another skill (`authoring-scouts`) rather than this skill's own bundle, so navigation is slightly indirect.

4 / 5

Total

17

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and occupies a clear, low-conflict niche, but it omits any explicit 'Use when...' trigger guidance, which caps completeness and leaves trigger-term coverage at a moderate level. Adding a concrete trigger clause would lift the two weakest dimensions.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when investigating PostHog $exception spikes, error regressions, or fingerprint clusters.'

Soften jargon like 'multi-fingerprint clusters' with a natural synonym (e.g. 'grouped error clusters') so users are more likely to phrase a request that matches.

Consider adding common variations/synonyms (e.g. 'error tracking', 'exception monitoring', '$exception events') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('PostHog error tracking') and lists several concrete signal types ('$exception bursts, stuck loops, multi-fingerprint clusters, and status regressions'), though all hang off the single verb 'Watches' rather than multiple distinct action verbs, leaving a minor coverage gap versus the comprehensive 5 anchor.

4 / 5

Completeness

It has a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric guideline a missing 'Use when...' clause caps completeness at 3, and the 'when' is at best weakly implied.

3 / 5

Trigger Term Quality

It contains one strong natural term ('error tracking') plus domain terms like '$exception', but mixes in jargon ('multi-fingerprint clusters') and lacks common synonyms/variations a user would naturally say, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The 'PostHog error tracking' / '$exception' niche is highly specific with distinct triggers and minimal realistic overlap with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

15

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

16

Passed

Repository

PostHog/posthog

Path

products/signals/skills/signals-scout-error-tracking/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.