CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rerun-catalog-queries

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

Quality

87%

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

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.

An excellent patterns skill: highly actionable code, a genuinely diagnostic debug workflow with validation checkpoints, and tight non-obvious content throughout. The only real gap is structural — everything lives in one 340-line file with no reference bundle, and a couple of sections (the DataFusion struct gotcha) sit at the edge of the skill's stated scope.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, experience-derived information ("Every materialization of a dataset.reader(...) DataFrame is one cloud round-trip") and assumes Claude's competence, delegating DataFrame basics to the datafusion-python skill. It is not a 5 because a few sections could be trimmed or moved — the struct-null gotcha section self-describes as "A DataFusion gotcha" that partially belongs in the companion skill, and the debug recipe recapitulates patterns already covered — but it is well above the 'mostly efficient with some unnecessary explanation' anchor.

4 / 5

Actionability

Fully executable, copy-paste-ready code covers the common cases: connecting via CatalogClient, the cache() pattern, cross-segment grouping by rerun_segment_id, per-entity is_not_null() filters, dataset.info() and schema() probing, and the null-guard projection, plus a concrete alternatives table for count(). This matches the top anchor; there are only minor gaps, not the missing key details of the 4 anchor.

5 / 5

Workflow Clarity

The 'Common debug recipe' is a clearly sequenced 6-step diagnostic workflow with explicit checkpoints (wrap materializations in time.perf_counter(), split build vs materialize timing, measure tbl.nbytes) and interpretation feedback at each step ("If 'build' takes seconds, something inside is materializing eagerly"). The skill is read-only querying, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

Good structure: well-titled self-contained sections, deliberate one-level delegation to the datafusion-python skill ('The DataFusion side of the stack is covered by the datafusion-python skill'), and no nested references. No bundle files exist, so all ~340 lines of pattern detail live in SKILL.md; a reference file for the longer pattern sections would be a minor improvement toward the 5 anchor, but this sits above the 'content that should be separate is inline with weak signaling' anchor.

4 / 5

Total

18

/

20

Passed

Description

82%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 strong description: it explicitly states both what the skill provides and three concrete trigger scenarios, uses natural user phrasing, and carves out a distinct niche. The only weakness is that the capability statement is a single composite action rather than an enumerated list of specific capabilities.

Suggestions

Enumerate 2-3 concrete capabilities in the what clause (e.g. '...batch cross-segment and cross-entity queries into one round-trip, apply pushdown filters, and debug slow catalog queries') to lift specificity.

Add one or two natural synonyms users might say (e.g. 'rerun.io', 'REDAP', 'query performance') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain precisely ("querying a Rerun catalog from Python", "CatalogClient/dataset query") and states 1-2 concrete actions (applying performance patterns and gotchas to catalog queries), which matches the anchor for domain plus 1-2 concrete actions without comprehensive coverage. It is not a 4 because it does not list several specific actions, and not a 2 because the actions named are concrete rather than generic.

3 / 5

Completeness

The what is explicit ("Performance patterns and gotchas for querying a Rerun catalog from Python") and the when is explicit with multiple concrete trigger phrases ("Reach for this when exploring an unfamiliar dataset, when a CatalogClient/dataset query is unexpectedly slow, or when shaping a per-segment / per-episode pipeline"), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say are present: "exploring an unfamiliar dataset", "a CatalogClient/dataset query is unexpectedly slow", "per-segment / per-episode pipeline". It falls short of the 5 anchor because a few natural synonyms are missing (e.g. rerun.io, REDAP, query performance), but coverage is clearly good rather than partial.

4 / 5

Distinctiveness Conflict Risk

"Rerun catalog" is a clear niche with distinct triggers (CatalogClient, per-segment/per-episode pipelines) and minimal conflict risk; the only adjacent skill (datafusion-python) covers a distinctly different layer of the stack and the description does not overlap it.

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.

Validation — 14 / 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

Path

skills/rerun-catalog-queries/SKILL.md

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.