CtrlK
BlogDocsLog inGet started
Tessl Logo

signals-scout-session-replay

Signals scout for PostHog session replay. Watches that sessions keep recording (capture cliffs) and that friction inside recordings — rage/dead-click clusters, error-after-interaction cohorts — gets surfaced, and files each validated cliff or cluster as a report in the inbox.

64

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./products/signals/skills/signals-scout-session-replay/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 high-quality, deeply actionable scout skill with executable SQL, precise thresholds, and a clear sequenced workflow; its only soft spots are minor framing verbosity and the absence of explicit error-recovery retry loops (less critical for a read-only reporting skill).

DimensionReasoningScore

Conciseness

Long but mostly efficient — it assumes Claude knows SQL and PostHog and adds only replay-specific footguns and judgment, with no padding about what a session replay is; a few framing sentences ('Two mechanical facts anchor everything') could be trimmed, keeping it just below the lean-and-efficient anchor.

4 / 5

Actionability

Every step ships executable SQL with exact table and column names (raw_session_replay_events.min_first_timestamp, argMinMerge(first_url)), precise volume gates (~3× prior-13-day mean, ≥10 sessions, ≥5 persons), and exact tool names with parameters — fully copy-paste ready.

5 / 5

Workflow Clarity

A clearly sequenced run (orient → explore → decide → close out) with embedded validation gates (baseline requirements, volume gates, 'require corroboration before emitting'), but no explicit validate→fix→retry feedback loops; this sits at clear-sequence-with-minor-gaps rather than the explicit-checkpoint-recovery anchor.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and a single one-level-deep reference ('authoring-scouts → references/report-contract.md') that is explicitly signaled and explicitly excluded from restatement; the inlined SQL is the core skill content and belongs in the body, so navigation is easy.

5 / 5

Total

18

/

20

Passed

Description

71%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 specific, well-scoped description with concrete actions and natural trigger vocabulary, weakened only by the absence of an explicit 'Use when…' clause, which caps completeness.

Suggestions

Add an explicit 'Use when…' clause stating when this scout should run (e.g., 'Use when monitoring PostHog session replay health, capture cliffs, or friction concentration in recordings') to lift completeness above 3.

Include a couple of natural synonyms or the product term users might say (e.g., 'session recordings', 'replay health', 'recording drop-off') to round out trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in a specific domain — 'Watches that sessions keep recording (capture cliffs)', 'rage/dead-click clusters, error-after-interaction cohorts', and 'files each validated cliff or cluster as a report in the inbox' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is clearly stated but no explicit 'when to use' clause is present — per the rubric guideline, a missing 'Use when…' clause caps completeness at 3 even though the what is concrete.

3 / 5

Trigger Term Quality

Strong natural vocabulary ('session replay', 'capture cliffs', 'rage/dead-click clusters', 'error-after-interaction cohorts', 'report in the inbox') but lacks the explicit 'Use when…' trigger phrasing and a couple of synonyms, sitting above the midpoint rather than at fully comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Distinct niche ('Signals scout for PostHog session replay') with clear triggers; minor overlap risk only with the closely related error-tracking sibling scout, fitting the mostly-distinct anchor.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

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.