The body is lean and operational — a tool table, a signal quick-reference, five sequenced steps with complete SQL/JSON, a verdict priority list, and a recommendation table — with no padding explaining concepts Claude already knows; it does not reach the verbosity of the level-2 anchor.

It provides fully executable, copy-paste-ready SQL with exact property names and a concrete JSON tool call, plus a verdict-to-action recommendation table — matching the executable, specific-examples anchor.

The five steps are clearly sequenced with explicit decision gates ('If this returns data... If it returns 404, proceed'), a priority-ordered verdict list, and pattern-based branching; the read-only diagnostic context does not trigger the destructive/batch feedback-loop cap.

The body is a concise overview that links to three real, one-level-deep reference files (diagnostic-signals.md, diagnosis-logic.md, examples.md), each clearly signaled with purpose, and the referenced paths resolve to actual files.

The description names the domain ('session recording is missing or was not captured') and enumerates concrete diagnostic areas ('SDK diagnostic signals, project settings, sampling, triggers, ad blockers, and quota/billing'), but the core action is a single verb ('Diagnoses') rather than a list of multiple distinct actions as the level-3 anchor requires.

It explicitly answers both what ('Diagnoses why a session recording is missing or was not captured') and when ('Use when a user asks...') with an explicit trigger clause.

Phrases like 'why a session has no replay', 'why recordings aren't appearing', and 'troubleshoot session replay capture issues' are exactly the natural terms a user would say, matching the good-coverage anchor.

The narrow focus on missing session-recordings plus PostHog SDK diagnostic signals gives it a clear niche with distinct triggers unlikely to fire for unrelated skills.