CtrlK
BlogDocsLog inGet started
Tessl Logo

debugging-local-replay

Debugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local pipeline: SDK capture, Caddy proxy, capture-replay (Rust), Kafka, ingestion-sessionreplay (Node), recording-api (Node), SeaweedFS, and common failure modes like orphaned processes, stuck phrocs workers, and trigger misconfiguration.

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.

The body is a well-structured diagnostic playbook: concise, concrete, and sequenced with decision checkpoints, while pushing deeper failure detail into a single clearly-linked reference file. It respects both the token budget and the reader's intelligence.

DimensionReasoningScore

Conciseness

Lean and efficient — a symptom table, an ASCII pipeline, and short diagnostic steps with copy-paste commands; it never explains basic concepts Claude already knows and every section earns its tokens.

3 / 3

Actionability

Fully executable guidance: exact `lsof -nP -i :3306 -i :6740 -i :6741`, `kcat`, `docker ps`, and `curl` commands with specific ports, topic names, and env vars — copy-paste ready, not pseudocode.

3 / 3

Workflow Clarity

A clear 4-step ordered sequence with explicit decision checkpoints at each step (e.g. "If ports are not listening: ... See common failures" / "If ports are listening: ... proceed to Step 3") that branch on findings and route to the right next action.

3 / 3

Progressive Disclosure

Body is a concise overview that points one level deep to a real `./references/common-failures.md` via well-signaled links (including a verified `#recorder-script-build-failure` anchor), with detail appropriately split out and easy navigation.

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.

The description is specific, complete, and rich in natural trigger terms while staying tightly scoped to one clear niche. It would reliably fire for the right request and conflict with almost nothing else.

DimensionReasoningScore

Specificity

Lists many concrete components and failure modes — "SDK capture, Caddy proxy, capture-replay (Rust), Kafka, ingestion-sessionreplay (Node), recording-api (Node), SeaweedFS" plus "orphaned processes, stuck phrocs workers, and trigger misconfiguration" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both: what ("Debugs why session recordings aren't appearing in the local dev environment") and when ("Use when a developer reports that local replay ingestion isn't working...") with explicit triggers.

3 / 3

Trigger Term Quality

Natural phrases a developer would actually say — "local replay isn't working", "recordings aren't showing up", "/s calls", "replay pipeline seems broken after hogli start" — give good coverage of real trigger language.

3 / 3

Distinctiveness Conflict Risk

A highly specific niche (PostHog local replay pipeline) with distinctive triggers unlikely to match any other skill, satisfying the clear-niche anchor.

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.