CtrlK
BlogDocsLog inGet started
Tessl Logo

investigating-replay

Investigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues in one pass. Use when a user provides a recording or session ID and wants to understand what happened — who the user was, what they did, what errors occurred, and whether there are related error tracking issues. Replaces the manual chain of session-recording-get, persons-retrieve, execute-sql, and query-error-tracking-issues-list.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

A well-structured, actionable skill with concrete SQL and tool examples and a clear multi-step workflow. Slight room to tighten prose and offload reference material for better token efficiency.

Suggestions

Trim framing sentences like 'Start with the recording to get metadata and the person's distinct ID' to lean imperatives to lift conciseness toward 5.

Consider moving the extended Replay Vision scanner-creation procedure into a referenced file (e.g. VISION.md) so the core investigation workflow stays scannable.

Add an explicit verification step after the parallel queries in Steps 1–3 (e.g. confirm distinct_id resolved and events returned) to add a light checkpoint to the main workflow.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence — no padding about what PostHog or a session recording is — but a few framing sentences ('Start with the recording to get metadata...') could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready tool calls and SQL queries with parameter placeholders covering the common investigation cases.

5 / 5

Workflow Clarity

Clear Step 1–4 sequence with conditional logic and a polling feedback loop in the Vision section, but the core read-only steps lack explicit validation checkpoints.

4 / 5

Progressive Disclosure

Well-organized with clear sections (tools, workflow, tips, related skills) and no nested references, though the ~230-line body is somewhat long for a single file with no offloaded reference material.

4 / 5

Total

17

/

20

Passed

Description

92%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, concrete description that clearly states what it does and when to use it with natural trigger phrases. Minor trigger-synonym gaps keep it just short of perfect on keyword coverage.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions — 'gathering metadata, person profile, same-session events, and linked error tracking issues in one pass' — covering the investigation comprehensively.

5 / 5

Completeness

Explicitly answers both what ('Investigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues') and when ('Use when a user provides a recording or session ID and wants to understand what happened') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases like 'recording or session ID', 'what happened', and 'who the user was', but omits a few synonyms (e.g. 'replay', 'HogHunt') a user might say.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — investigating a specific PostHog recording in one pass — and the 'Replaces the manual chain of session-recording-get...' clause sharply distinguishes it from 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.