CtrlK
BlogDocsLog inGet started
Tessl Logo

rerun-catalog-queries

Performance patterns and gotchas for querying a Rerun catalog from Python. Reach for this when a CatalogClient/dataset query is unexpectedly slow, or when shaping a per-segment / per-episode pipeline that hits the catalog from many places.

65

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/rerun-catalog-queries/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 tightly written, highly actionable catalog of performance patterns with executable code, a decision table, and a sequenced debug recipe. It avoids re-teaching basics and stays focused on non-obvious behaviors, with only minor conciseness trims possible.

DimensionReasoningScore

Conciseness

The body is dense and high-signal, focused on non-obvious catalog behaviors and round-trip economics rather than restating what DataFusion or Python are; a few sentences of motivation (e.g. the fan-out arithmetic) could be trimmed but overall it respects Claude's intelligence.

4 / 5

Actionability

It provides copy-paste-ready code blocks for the main patterns (caching, cross-segment batching, per-entity fan-out, struct null guards), a concrete decision table for count alternatives, and a numbered debug recipe with specific commands — covering the common cases fully.

5 / 5

Workflow Clarity

The 'Common debug recipe' is a clear 6-step sequence with timing checkpoints and corrective guidance (e.g. build-vs-materialize timing indicating eager materialization), though it is a diagnostic flow rather than a destructive/batch operation requiring hard validation gates.

4 / 5

Progressive Disclosure

Content is well organized into focused section headers with a clear top-of-file scope and a 'See also' pointer to the sibling datafusion-python skill; no bundle files exist to split further, and the single skill is self-contained at one level of reference depth.

4 / 5

Total

17

/

20

Passed

Description

76%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 tied to a concrete API surface with an explicit 'when' trigger and clear boundary against a sibling skill. The main gap is trigger-term breadth — phrasing leans technical and could capture more natural user phrasings.

Suggestions

Broaden the 'when' clause with more natural trigger phrases a user might say (e.g. 'Rerun queries are slow', 'catalog round-trips', 'too many reader calls').

Consider adding synonyms such as 'Rerun catalog' / 'recording queries' so users describing the problem in looser terms still surface this skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'querying a Rerun catalog from Python', 'CatalogClient/dataset query is unexpectedly slow', and 'shaping a per-segment / per-episode pipeline that hits the catalog from many places' — giving comprehensive coverage of what the skill addresses.

5 / 5

Completeness

It has a clear 'what' (performance patterns and gotchas for catalog queries) and an explicit 'when' ('Reach for this when...'), though the 'when' clause is somewhat specific to slowdown/pipeline-shaping scenarios rather than broad concrete triggers.

4 / 5

Trigger Term Quality

It names the concrete API surface (CatalogClient, dataset, per-segment/per-episode pipeline) but the trigger phrasing is fairly technical and lacks common synonyms or looser natural phrases a user might say beyond 'catalog query is slow'.

3 / 5

Distinctiveness Conflict Risk

The narrow Rerun-catalog niche with named API classes (CatalogClient, dataset.reader) and explicit handoff to the separate datafusion-python skill gives it a clear niche with minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
rerun-io/rerun
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.