CtrlK
BlogDocsLog inGet started
Tessl Logo

investigating-error-issue

Investigates a single PostHog error tracking issue end-to-end. Use when the user provides an issue ID or pastes an issue URL (`/error_tracking/<id>`) and wants to understand the error — who it affects, what triggers it, when it started, whether it correlates with a release, browser, OS, or feature flag, and what the next step should be. Pulls aggregated metrics, sample exception events, segment breakdowns, linked replays, and synthesizes a hypothesis-grade summary in one pass.

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 high-quality, dense workflow skill: executable SQL/JSON examples, a clearly sequenced 6-step investigation with decision branches and fallbacks, and well-organized sections without padded concept explanations. Content is cohesive in one file with no nested references and no need for external bundles.

DimensionReasoningScore

Conciseness

The ~350-line body is dense with non-obvious domain knowledge Claude lacks (e.g. the Nullable JSONExtract planning error, the issue_id vs $exception_issue_id distinction) and avoids explaining known concepts; tokens earn their place, so it is lean rather than padded.

3 / 3

Actionability

Provides multiple complete, copy-paste-ready SQL queries and JSON tool invocations with full parameters (e.g. the app_version breakdown query and the JSONExtract(ifNull(...)) flag query), meeting the bar for fully executable guidance.

3 / 3

Workflow Clarity

A clearly sequenced 6-step workflow with decision branches and empty-result handling ('If every row is NULL...switch to $exception_releases or fall back to a toDate timeline'); as a read-only investigation the destructive/batch cap-at-2 rule does not apply.

3 / 3

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into signaled sections with no nested references and delegates appropriately to sibling skills (e.g. 'Hand off to finding-replay-for-issue'), keeping workflow-coupled content inline rather than over-split.

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, distinctive description: it names concrete actions, gives explicit natural-language triggers including a URL pattern, answers both what and when, and stays in third person. It is specific to PostHog error tracking, so conflict risk with other skills is low.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Pulls aggregated metrics, sample exception events, segment breakdowns, linked replays, and synthesizes a hypothesis-grade summary' — matching the anchor for listing several specific actions rather than naming only a partial domain.

3 / 3

Completeness

Explicitly answers both what (investigates end-to-end, pulls metrics/samples/breakdowns/replays, synthesizes a summary) and when (an explicit 'Use when...' clause with concrete triggers), so it is not capped at 2 for a missing trigger clause.

3 / 3

Trigger Term Quality

Covers natural user phrasing — 'Use when the user provides an issue ID or pastes an issue URL (`/error_tracking/<id>`)', 'understand the error', 'who it affects, what triggers it, when it started' — giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Scoped to a 'single PostHog error tracking issue' with a URL-shaped trigger (`/error_tracking/<id>`), giving it a clear niche unlikely to fire for unrelated skills; voice is third person throughout ('Investigates', 'Pulls').

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.