robot-data-quality
Judge and improve the quality of robot-learning datasets (teleoperated demonstrations, episodes) and use forge, the Robotics Data Toolkit, to inspect, lint, score, visualise, filter, dedup, and convert them.
Install / Use
npx skills add arpitg1304/robotics-agent-skills --skill robot-data-qualityInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Education & ResearchSupported Platforms
Tags
Our assessment of robot-data-quality
robot-data-quality scores 88/100 on our quality scale, 196th of 416 Education & Research skills we index (top 48%).
Its SKILL.md is 17 KB long, well organised into 16 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
It has 405 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 3 days ago, so robot-data-quality is actively maintained.
- Our last check on 2026-11-22 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-22. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
robot-data-quality compared with similar skills
All 4 of these similar skills score higher than robot-data-quality; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| robot-data-quality (this skill)by arpitg1304 | 88 | 405 | 3d ago | SKILL.md |
| last30days-skillby mvanhorn | 100 | 72.6k | today | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install robot-data-quality?
- Run
npx skills add arpitg1304/robotics-agent-skills --skill robot-data-quality. The install tabs above show the steps for each supported agent. - Which AI agents does robot-data-quality work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is robot-data-quality safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is robot-data-quality still maintained?
- The repository was last updated 3 days ago, so robot-data-quality is actively maintained.
Skill content
View source on GitHubname: robot-data-quality description: > Judge and improve the quality of robot-learning datasets (teleoperated demonstrations, episodes) and use forge, the Robotics Data Toolkit, to inspect, lint, score, visualise, filter, dedup, and convert them. Use this skill when the user mentions dataset quality, data cleaning or curation, episode inspection, bad or noisy demos, idle frames, jerky or spiky actions, gripper chatter, timestamp gaps or frame drops, camera blur or exposure, duplicate episodes, task-string hygiene, normalisation stats, train/val splits by episode, coverage or diversity of demonstrations, or why a policy will not start, stalls, or averages modes because of its data. Also trigger on forge commands (forge inspect, lint, stats, quality, filter, dedup, visualize, convert, catalog, ingest, curate) and on conversion between RLDS, LeRobot v2/v3, Zarr, HDF5, MCAP, rosbag, or RoboDM, including hf:// datasets on the Hugging Face Hub.
Robot Data Quality Skill
Verified against forge 0.2.0 (commit 12a3167), 2026-11-18. The version is from
pyproject.toml; forge version prints v0.1.0 at this commit because forge/__init__.py
was not bumped. Every forge command and flag here was checked against the Typer definitions in
forge/cli.py and forge/catalog/cli.py and against forge <cmd> --help from an editable
install of that commit.
When to Use This Skill
- Auditing a teleoperated dataset before training (LeRobot, ACT, Diffusion Policy, VLA fine-tuning)
- Explaining a policy failure that might come from the data (won't start, hesitates, jitters, averages between strategies, ignores the language instruction)
- Deciding which episodes to drop, trim, relabel, or re-collect
- Running
forgeto inspect, lint, score, review, filter, or dedup a dataset - Converting between RLDS, LeRobot, Zarr, HDF5, MCAP, rosbag and checking nothing was lost
- Writing a data-quality report for a collection team
Hand off: recording and training commands go to lerobot; algorithm choice, action chunking
and why demonstrations need to be consistent go to imitation-learning; reward and rollout
data go to robot-reinforcement-learning; simulated data generation goes to mujoco and
isaac-sim.
Mental Model
A behaviour-cloning policy learns the conditional distribution of actions given observations exactly as recorded. It cannot tell an operator's hesitation from a deliberate wait, a logging glitch from a real correction, or a mislabelled camera from a different viewpoint. Data quality is therefore about three things:
- Integrity: is the recorded signal what happened? (timestamps, sync, decode, units, camera mapping, NaNs, conversion losses). Integrity bugs are silent and systematic; fix them first, because they invalidate every later check.
- Behaviour quality: is each demonstration something you want imitated? (idle spans, aborted takes, jerk, regrasps, saturation, failures). These are per-episode decisions.
- Distribution: does the set cover what the policy will see, consistently? (initial conditions, object positions, operator strategies, task balance, task strings, splits, normalisation stats). These are dataset-level and often need new data, not filtering.
Three rules follow:
- Scores are triage, not verdicts. forge's 0-10 score is a heuristic over motion signals; it says nothing about task success. Every flag is a review candidate.
- Look at the episode before deleting it. Ten minutes in a viewer beats any threshold.
- Filtering cannot create coverage. If a region of the workspace has no demos, the fix is collection, not cleaning.
Quality Checklist: What to Check and the Failure It Prevents
Thresholds are starting points to calibrate on your robot, task and FPS, not standards.
Print the distribution first, then choose the cut. Recipes for checks forge does not run are in
references/custom-checks.md.
Episode-level (most important)
| Check | How (forge or recipe) | Starting-point threshold | Downstream failure it prevents |
|---|---|---|---|
| Length outliers | forge stats distribution; robust z-score recipe | abs robust z > 3.5 | Aborted takes teach "stop midway"; marathon takes teach dithering |
| Idle head/tail | motion_pause events; active_span recipe | head idle > 1 s or > 10% of episode | Policy that never starts: initial observation maps to "do nothing" |
| Idle mid-episode | motion_pause, mostly_static flag (> 50% observed time) | review if pause > 1-2 s not explained by the task | Hesitation, freezing mid-task |
| Gripper events | --gripper-dims, gripper_chatter (> 2 transitions/s); event-count recipe | pick-place: about 1 close + 1 open | Chatter -> oscillating grasp; regrasps -> hesitant grasps |
| Jerk and spikes | jerky (LDLJ < -25), psd_high_band_chatter (> 20% energy above 8 Hz); spike recipe | step > 8x median step | Jittery policy, controller faults, normalisation blow-up |
| Action-state alignment and lag | --tracking-pairs, tracking_stall_candidate; estimate_lag recipe | lag stable across sessions | Off-by-k shift makes the policy react late or "predict the past" |
| Timestamp monotonicity, gaps | invalid_timestamps, timestamp_gaps (dt > 2x period), timestamp_jitter (std/mean > 0.1), sample_rate_mismatch (> 10%) | any invalid; gaps > 1-2 frames | Wrong velocities, misaligned chunks, corrupted temporal context |
| NaN / non-finite | nan_in_actions, nan_in_states, nan_in_timestamps | any | Training NaNs, corrupted stats |
| Duplicates | forge dedup (pHash, 0.10 default) | inspect clusters | Leakage across splits, over-weighted takes |
Full episode-level table (held commands, truncated takes, success labels, saturation, joint
limits, camera-proprio sync), the visual table (blur, exposure, frozen frames, cuts, camera
mapping) and the dataset-level table (coverage, operator multimodality, task strings,
balance, splits, normalisation stats, units): references/quality-checklist.md.
How data defects show up in policy behaviour
| Policy symptom | Look for in the data |
|---|---|
| Will not start, waits forever at the home pose | Idle heads; many motion_pause events starting at frame 0 |
| Starts then freezes midway | Mid-episode pauses, operator hesitation, aborted takes left in |
| Jitters or buzzes at standstill | Spikes, psd_high_band_chatter, teleop noise, gripper chatter |
| Goes to the average of two places | Multimodal strategies (left vs right approach) with few demos each |
| Grasps late or overshoots | Action-state lag, camera-proprio offset, wrong FPS |
| Works in one session's lighting only | Exposure differences, camera moved, session imbalance |
| Ignores the language instruction | Generic or missing task strings, one string for several tasks |
| Hits joint limits | Saturated state/actions in demos, min/max stats set by outliers |
| Great val loss, bad on robot | Frame-level split, duplicates across splits, val from same sessions |
Drop, trim, relabel, or re-collect
- Trim: idle head/tail, operator setup motion before the task. Keep a few static frames at the start so the initial observation is represented. forge has no trim command; trim by index in your writer or data loader.
- Drop: integrity failures (NaN, invalid timestamps, decode failures, black frames), aborted or failed takes (unless you train failure-aware or RL methods), exact duplicates, episodes with an unfixable camera mapping.
- Relabel: wrong or generic task strings, swapped camera names, success labels. Cheaper than deleting.
- Re-collect: coverage holes, a camera that moved, a systematic sync or calibration error, inconsistent operator strategies (agree a protocol first), too few demos per variation.
- Keep: legitimate waits (pouring, settling), deliberate slow approaches, contact-induced tracking error. These look "bad" to motion heuristics and are often essential.
As a rule of thumb, dropping more than about 20% of a dataset by heuristics means the collection process is the problem; report that instead of silently filtering.
forge Workflow (core sequence)
forge inspect ./ds --output json > inspect.json # format, dims, cameras, fps, language coverage
forge lint ./ds --export lint.json # hygiene; non-zero exit on errors
forge stats ./ds --output stats.json # lengths, per-dim action/state stats, coverage
# Configured run for a 7-DoF arm + gripper at action column 7, actions in [-1, 1]:
forge quality ./ds \
--gripper-dims 7 --action-bounds=-1,1 \
--state-dims 0,1,2,3,4,5,6 \
--pause-speed 0.01 --event-min-duration 0.5 \
--fps 15 --workers 8 \
--export quality.json --export-flagged flagged.json
forge quality ./ds --video --video-stride 4 --export quality.json
forge export-video ./ds -e 12 -o ep12.mp4 --grid # non-interactive: produce a file to view
forge filter ./ds ./ds_clean --from-report quality.json \
--exclude-flags nan_in_actions,nan_in_states,invalid_timestamps,video_decode_failure \
--exclude-episodes 3,17,42
forge dedup ./ds # dry-run: clusters
Install (pip install forge-robotics plus extras), path arguments (hf://, s3://), write
support, configuration rules for forge quality, reading the JSON export, video thresholds,
viewers, dedup details and the catalog: references/forge-workflows.md. Every flag, default
and JSON field: references/forge-cli-reference.md.
forge behaviours that bite
overall_scorecan benull(invalid data, irregular timebase, no evaluable motion). Treat null as "needs review", never as "fine".--min-qualitykeeps null-score episodes, and episodes missing from the report pass quality filters with a warning. Exclude unscored ids explicitly if you want them out.- The quality recommendations may print
forge filter --max-gripper-chatter; that flag does not exist. Use--exclude-flags gripper_chatter. --visualizeandforge visualize --backend webserve a local page and block until Ctrl+C. In a non-interactive agent session, run them in the background or useexport-video,--plot, and the JSON exports instead.- YAML
fields:mapping is parsed but not applied; YAMLvideo:settings are not applied either (usewriter_config: {video_crf: 20}). - Without
--from-report, filter re-scores with only--gripper-dim,--fpsand--action-bounds: your state dims, scales, tracking pairs and event thresholds are lost, so flags differ from the report you reviewed. --fpsis only a fallback when timestamps are missing (Zarr, HDF5, RLDS, RoboDM). If you leave it at 30 on a 10 Hz dataset, every duration and rate threshold is wrong.--sample Nand--quick(= 50) take the first N episodes, not a random subset.- Video flags never change the proprioception score; filter on them explicitly.
filteranddedupwrite the source format, so convert first when the source is read-only.
Checks forge does not provide at commit 12a3167 (trimming, lag estimation, joint-limit
saturation, success detection, splits, and more): "Gaps" in references/forge-workflows.md.
Conversion Pitfalls
forge converts through one canonical Episode/Frame model: one state vector, one action
vector, images, timestamps, language, and a few flags per frame. Anything else is dropped,
and the reader decides which source keys become state and action by name heuristics. forge
performs no unit, rotation or frame-convention conversion. Before converting, load
references/forge-format-notes.md (pitfalls table, per-format behaviour, a working
conversion.yaml, and the round-trip verification to run after every conversion).
Triage Workflow (brief)
Run in this order; each step can invalidate the next.
- Pin provenance. Work on a copy; never filter in place.
- Integrity. `forge inspec
Truncated for display — read the full file on GitHub.
Related Skills
last30days-skill
72.6kAI agent skill that researches any topic across Reddit, X, YouTube, HN, Polymarket, and the web - then synthesizes a grounded summary
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
