CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rerun-data-model

How raw multimodal robot data maps onto the Rerun data model. Read FIRST, before modeling or converting a dataset — and whenever you are about to convert/ingest/preprocess robot data into an .rrd or build a Rerun recording, even if not asked for the data model. Resolves the entity-vs-component, property-vs-component-vs-layer, and static-vs-temporal decisions and routes to the mechanism (do it with readers and lenses, not hand-built chunks or per-message rr.log): rerun-chunk-processing and the importer skills rerun-mcap, rerun-urdf, rerun-parquet, rerun-mp4, rerun-lerobot.

Quality

88%

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

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.

An exemplary decision-focused skill body: terse, well-sectioned, and anchored by a concrete mapping-table template and a gotchas list of real failure modes. The only gaps are a slightly vague fallback branch in the mechanism decision and the absence of any executable code or a post-table validation step.

Suggestions

Tighten the third mechanism branch into a concrete check (e.g. 'if you find yourself writing a per-message loop or building chunks by hand, stop and ask which reader/lens covers it').

Add one short code snippet (or a completed minimal mapping-table row to code correspondence) to anchor the table directly to executable ingest calls.

Add an explicit post-table checkpoint: verify every row has an entity path, archetype, timeline, and static/temporal + base/layer decision before writing conversion code.

DimensionReasoningScore

Conciseness

Dense, lean declarative prose with zero padding — every line is a decision, a rule, or a concrete gotcha (e.g. "Static shadows all temporal data of that component for all time"); it assumes Claude's competence throughout.

5 / 5

Actionability

A copy-paste-ready filled mapping table, concrete archetype names, and exact flags like `send_properties=False` make the guidance mostly executable; one branch ("consider if you are about to hand-build something… ask for clarification") stays soft, and no code snippet is given even where a one-liner would anchor the pattern.

4 / 5

Workflow Clarity

The sequence (pick mechanism → model → decisions → produce the mapping table before coding) is clear and the table is an explicit reviewable checkpoint; not a destructive/batch skill, but there is no validate-and-fix loop after the table is filled in, keeping it below a 5.

4 / 5

Progressive Disclosure

Self-contained with no bundle files needed; sections are well-organized and every external pointer (rerun-chunk-processing, the importer skills, rerun-catalog-queries, rerun.io docs) is clearly signaled one level deep.

5 / 5

Total

18

/

20

Passed

Description

87%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 states a clear what, an explicit and eager trigger clause ("Read FIRST… even if not asked for the data model"), names concrete decision axes, and cleanly delimits itself from sibling mechanism skills. Only minor synonym coverage keeps trigger terms and specificity from full marks.

Suggestions

Add one or two natural synonyms users might say (e.g. rosbag, 'log robot data') to broaden trigger coverage.

Name one concrete outcome of the resolved decisions (e.g. 'produces a mapping table of source → entity/archetype/component') to sharpen the action list.

DimensionReasoningScore

Specificity

Concrete actions are named — "Resolves the entity-vs-component, property-vs-component-vs-layer, and static-vs-temporal decisions and routes to the mechanism" with specific reader mappings — but coverage of what each decision produces is slightly less enumerated than a full multi-action list.

4 / 5

Completeness

Explicitly answers both what ("How raw multimodal robot data maps onto the Rerun data model") and when ("Read FIRST, before modeling or converting a dataset — and whenever you are about to convert/ingest/preprocess robot data into an .rrd") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like "convert/ingest/preprocess robot data into an .rrd" and "build a Rerun recording" plus the `.rrd` extension give good keyword coverage; a few natural synonyms (e.g. rosbag, dataset-conversion phrasings) are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Rerun data-model decisions) with distinct triggers, and it explicitly distinguishes itself from the mechanism skills it routes to (rerun-chunk-processing, rerun-mcap, etc.), minimizing conflict risk.

5 / 5

Total

18

/

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-data-model/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.