CtrlK
BlogDocsLog inGet started
Tessl Logo

exploring-replay-vision-observations

Guides agents through pulling a Replay Vision scanner's observations, reading the findings, and acting on them — summarizing patterns across sessions, drilling into individual recordings, and turning real, corroborated issues into PostHog tasks, insights, or an investigating-replay hand-off. TRIGGER when: user wants to pull/read/triage Replay Vision observations, asks "what has my scanner found", wants to act on or summarize scanner findings, turn observations into tasks/work, or points at a /replay-vision/<scanner-id> URL. DO NOT TRIGGER when: creating or sizing a scanner (use creating-replay-vision-scanners), running a one-off scan you don't then analyse, or authoring a signals scout.

76

Quality

95%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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, highly actionable skill body with a clear sequenced workflow, explicit validation checkpoints, and concrete tooling throughout. The only slack is mild verbosity in the conceptual prose and the lack of any progressive-disclosure file split for a skill this long.

Suggestions

Tighten the Mental Model and rating-guidance paragraphs to the actionable minimum — the safety rationale for not inventing ratings can be stated in one sentence.

Consider moving the status triage table and the recording-URL formatting detail into a short references file so the main body stays a navigable overview, which would also let progressive_disclosure reach 5.

The Quota gotcha buries credit pricing ($0.01/credit) in prose — surface only the actionable 'check vision-quota-retrieve before a batch' check and move pricing to a reference.

DimensionReasoningScore

Conciseness

Dense and mostly lean — every section earns its place with concrete tool names and parameters — though the Mental Model block and some explanatory prose (e.g. elaborating why a rating must come from the user) could be trimmed slightly without losing the actionable core.

4 / 5

Actionability

Fully executable guidance throughout: specific MCP tool names (vision-scanners-observations-list, vision-scanners-impact-retrieve) with exact parameters, filters, order_by values, and ISO 8601 / '-7d' / 'now' date formats, plus a copy-paste recording URL template.

5 / 5

Workflow Clarity

A clearly sequenced 4-step workflow (Anchor → Pull → Read → Act) with explicit validation checkpoints — 'corroborate before you act', the status triage table, and 'check vision-quota-retrieve before triggering a batch' — plus feedback loops for the credit-spending batch/on-demand operations.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level cross-skill links ([[creating-replay-vision-scanners]], [[investigating-replay]], [[inbox-exploration]]), but it is a single 167-line file with no bundle split, so reference-like material (the status table, URL format) is inlined rather than factored out.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete capabilities, natural trigger phrases, explicit what/when guidance, and clear boundary routing to sibling skills. Nothing vague or padded.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'pulling a Replay Vision scanner's observations, reading the findings', 'summarizing patterns across sessions, drilling into individual recordings, and turning real, corroborated issues into PostHog tasks, insights, or an investigating-replay hand-off' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (the pulling/reading/acting verb chain) and 'when' via dedicated 'TRIGGER when:' and 'DO NOT TRIGGER when:' clauses with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say — 'what has my scanner found', 'pull/read/triage Replay Vision observations', 'turn observations into tasks/work', plus the concrete '/replay-vision/<scanner-id> URL' trigger — covering synonyms and a URL form.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (exploring Replay Vision observations) with distinct triggers and an explicit 'DO NOT TRIGGER' clause that routes scanner creation to a sibling skill, minimizing conflict risk.

5 / 5

Total

20

/

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.

Validation — 16 / 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.