CtrlK
BlogDocsLog inGet started
Tessl Logo

creating-replay-vision-scanners

Guides agents through creating and safely sizing a Replay Vision scanner: choosing the scanner type (monitor/classifier/scorer/summarizer), shaping the RecordingsQuery that selects sessions, and — crucially — estimating observation volume and checking the org's monthly quota before creating, so a broad scanner doesn't exhaust the budget on its first scheduled sweep. TRIGGER when: user asks to create, set up, or configure a Replay Vision scanner, OR when you are about to call vision-scanners-create, OR when widening an existing scanner's query or sampling_rate via vision-scanners-update. DO NOT TRIGGER when: only reading scanners or observations, deleting a scanner, or running an existing scanner against a single session on demand (vision-scanners-scan-session).

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 content is executable, well-sequenced with validation checkpoints, and tightly scoped to the quota-safety rationale that motivates the skill. Organization is clean with no unnecessary external references.

DimensionReasoningScore

Conciseness

The body is lean: it skips generic tutorial prose, uses a compact table for config shapes, and every section earns its place by conveying non-obvious operational detail.

3 / 3

Actionability

Names exact tool calls, provides per-type scanner_config shapes, and includes a complete copy-paste-ready JSON create example with concrete decision branches.

3 / 3

Workflow Clarity

A clear four-step sequence with an explicit validation gut-check in Step 3 (estimate + check budget + decide) and a mandated re-check when widening scope during updates.

3 / 3

Progressive Disclosure

No bundle files exist; the single self-contained SKILL.md is organized into well-signaled sections with no nested reference chains, fitting a reference-free skill.

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.

A high-quality description: it states concrete capabilities in third person, gives explicit positive and negative triggers, and occupies a clear niche. No over-claims or fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — choosing a scanner type across four named types, shaping the RecordingsQuery, and estimating volume/checking quota — rather than vague language.

3 / 3

Completeness

Explicitly answers both what the skill does and when to use it via dedicated TRIGGER and DO NOT TRIGGER clauses.

3 / 3

Trigger Term Quality

Provides natural user-language triggers ('create, set up, or configure a Replay Vision scanner') alongside tool-call triggers and explicit DO NOT TRIGGER conditions, giving broad coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped to a specific product ('Replay Vision scanner') with named tools and negative triggers, making conflict with other skills unlikely.

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.