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.

80

Quality

100%

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

100%

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

A tightly written, highly actionable skill body that combines executable tool-call examples, a clear six-step workflow with destructive-operation validation, and domain-specific gotchas Claude would not otherwise know. Organization is clean with no reference-depth issues.

DimensionReasoningScore

Conciseness

Dense with PostHog-specific knowledge Claude would not have (the $lib="web" quirk, exception-array property special-casing, custom-rule:<rule_id> routing) with no padding on generic concepts; every section earns its tokens.

3 / 3

Actionability

Provides fully executable JSON tool-call payloads with real parameter values and concrete filter operators (exact "web", icontains on $exception_sources), plus copy-paste-ready grouping-rule examples.

3 / 3

Workflow Clarity

Six clearly sequenced steps with explicit validation checkpoints ('Confirm the target with the user before calling', 'Sample the merged issue's recent events to confirm the merge succeeded') and feedback loops for the destructive merge operation.

3 / 3

Progressive Disclosure

A single well-organized SKILL.md with clearly labeled sections and one-level external references (a GitHub source link); no nested or multi-level reference chains, and no bundle files to over-fragment.

3 / 3

Total

12

/

12

Passed

Description

100%

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, specific description with explicit third-person actions, verbatim user trigger phrases, and a clear what/when structure. The explicit negative-scope clause sharply lowers conflict risk with related PostHog skills.

DimensionReasoningScore

Specificity

Names multiple concrete actions in third person ('Consolidate PostHog error tracking issues', 'Decides between a one-shot merge...and a durable grouping rule') rather than vague language.

3 / 3

Completeness

Explicitly answers both what (consolidate duplicate issues, choose merge vs grouping rule) and when via an explicit 'Use when' clause with concrete triggers.

3 / 3

Trigger Term Quality

Quotes natural user phrases verbatim ('why do I have so many TypeError issues that look the same?', 'merge these duplicates', 'stop splitting this error into new issues', 'clean up fingerprint sprawl') — terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear PostHog error-tracking niche and explicitly disambiguates scope ('Does NOT group conceptually similar bugs across different runtimes, SDKs, or call sites'), reducing conflict with adjacent skills.

3 / 3

Total

12

/

12

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.