CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnosing-missing-recordings

Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling, triggers, ad blockers, and quota/billing scenarios.

64

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/replay/skills/diagnosing-missing-recordings/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is well-structured and actionable with concrete SQL and a clear diagnostic workflow, but it is undermined by three references to a non-existent ./references/ directory, leaving the core diagnosis logic and examples unreachable.

Suggestions

Create ./references/diagnostic-signals.md, ./references/diagnosis-logic.md, and ./references/examples.md so the inline links resolve — currently the references/ directory does not exist.

Inline the essential diagnosis-logic content (the verdict interpretation rules) into SKILL.md so Step 3 does not depend entirely on a missing file, keeping only the exhaustive signal catalog and examples external.

Verify each markdown link target exists before relying on it; the examples.md link is referenced from both Step 3 and the Examples section but is absent.

DimensionReasoningScore

Conciseness

The body is largely lean, using tables, SQL, and a tight verdict list without explaining what PostHog or session replay is, with only minor over-explanation (e.g., 'The PostHog SDK emits diagnostic properties on every event...') that could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

It provides copy-paste-ready SQL and tool-call JSON plus a verdict and recommendations table, but Step 3 defers the core signal interpretation to a missing ./references/diagnosis-logic.md file, leaving a notable gap, matching 'mostly executable guidance; concrete code with minor gaps'.

4 / 5

Workflow Clarity

The five-step workflow is clearly sequenced with a decision branch in Step 1 ('If this returns data... If it returns 404, proceed') and a prioritized verdict fallback, fitting 'clear sequence with most checkpoints present'; no destructive/batch cap applies since this is read-only diagnosis.

4 / 5

Progressive Disclosure

The SKILL.md is well-organized and signals one-level-deep references to diagnostic-signals.md, diagnosis-logic.md, and examples.md, but none of those files (or the references/ directory) exist, so the navigation is broken and the deferred detail is inaccessible, matching 'references present but not clearly signaled / could be better organized'.

3 / 5

Total

15

/

20

Passed

Description

82%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 strong: it explicitly covers both what and when with natural trigger phrases and a well-scoped niche. Its only soft spot is specificity, since it lists coverage topics rather than multiple distinct concrete actions.

DimensionReasoningScore

Specificity

The description names the domain ('session recording is missing or was not captured') and one concrete action ('Diagnoses'), then enumerates coverage areas (SDK signals, sampling, triggers, ad blockers, quota/billing) rather than multiple distinct concrete actions, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

It explicitly answers what ('Diagnoses why a session recording is missing or was not captured') and when ('Use when a user asks why a session has no replay...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Phrases like 'why a session has no replay', 'why recordings aren't appearing', and 'troubleshoot session replay capture issues' are natural user language with synonyms (replay/recordings), but a few common variations are absent, fitting 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (PostHog session replay capture diagnostics) with distinct triggers ('no replay', 'recordings aren't appearing') and minimal overlap with sibling skills, matching 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

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.