CtrlK
BlogDocsLog inGet started
Tessl Logo

grouping-noisy-errors

Consolidate PostHog error tracking issues that are the same actual error reported under different fingerprints. Use when the user asks "why do I have so many TypeError issues that look the same?", "merge these duplicates", "stop splitting this error into new issues", or wants to clean up fingerprint sprawl. Decides between a one-shot merge of existing issues and a durable grouping rule that keeps future events from creating new fingerprints. Does NOT group conceptually similar bugs across different runtimes, SDKs, or call sites.

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A well-organized, highly actionable skill body with executable examples, a sequenced workflow, and strong feedback loops for its destructive/batch operations. The only weakness is mild repetition (the $lib caveat and the boundary rationale are restated across sections) that slightly inflates token use.

Suggestions

Consolidate the repeated $lib="web" / read-data-schema warning into one callout and reference it from steps 1, 4, and 5 instead of restating it each time.

Tighten the 'What NOT to group' anti-pattern list by cross-referencing the step-1 checklist rather than re-deriving the same 'different code path' rationale at length.

Consider extracting the long grouping-rule filter example in Step 5 into a reference snippet to further trim the main body if the skill grows.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no 'what is an error' padding), but the $lib="web" caveat is repeated across steps 1, 4, and 5 and the 'What NOT to group' anti-pattern list re-derives the intro boundary at length, leaving minor trim opportunities.

4 / 5

Actionability

Provides fully executable JSON tool-call examples with concrete parameters, exact property keys and operators ($exception_types, exact, icontains), and real gotchas baked in, covering the common merge and grouping-rule cases copy-paste ready.

5 / 5

Workflow Clarity

A clearly sequenced 6-step workflow with explicit validation/feedback loops — destructive merge flagged with user confirmation and a ~50-ID batching cap, wait-and-re-query after merge, widen-or-split recovery when new fingerprints keep appearing — matching the top anchor.

5 / 5

Progressive Disclosure

Self-contained in SKILL.md with clean section headers, a tools table, and a well-signaled one-level 'Related skills' pointer; no nested or deep references to navigate.

5 / 5

Total

19

/

20

Passed

Description

95%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.

A strong, tightly-scoped description that pairs a clear statement of capability with multiple natural trigger phrases and an explicit out-of-scope boundary. The only minor weakness is that its listed actions are facets of one grouping mechanism rather than several distinct capabilities.

DimensionReasoningScore

Specificity

Names the domain (PostHog error tracking) and concrete actions — 'one-shot merge of existing issues' and 'durable grouping rule that keeps future events from creating new fingerprints' — but the actions are variations on grouping rather than distinct parallel capabilities, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (consolidate same-error duplicates; decide between merge vs grouping rule) and 'when' with concrete quoted trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Embeds multiple verbatim natural phrases users would say ('why do I have so many TypeError issues that look the same?', 'merge these duplicates', 'stop splitting this error into new issues') plus 'clean up fingerprint sprawl', giving comprehensive trigger coverage.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche (PostHog error tracking fingerprint/grouping) and adds an explicit negative boundary ('Does NOT group conceptually similar bugs across different runtimes, SDKs, or call sites'), minimizing overlap with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PostHog/posthog
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.