OPEN UTILITY · VERSION 1.2.0 RELEASE CANDIDATE
Validate robot-policy reproducibility.
Check a LeRobot policy repository before attempting reproduction on an SO-100 or SO-101 arm. The validator inventories reproducibility evidence, writes a portable robot-skill.yaml, and identifies missing metadata. Configuration comparison does not prove physical transfer or safe operation.
$ robot-skill check ./policy --strict
INCOMPLETE ./policy
Detected 4 evidence files
ERROR policy.framework_version
Pin the framework version.
ERROR hardware.gripper
Declare the end effector.
WARN evaluations
Compatibility remains unverified.01 / QUICKSTART
From repository to manifest
- 1Install
pipx install . # from the Known Robot 1.2.0 checkout - 2Inspect a policy
robot-skill check ./policy - 3Use it in CI
robot-skill check . --strict --no-write
Python 3.10–3.12 · macOS, Linux, and Windows · Apache-2.0
02 / EVIDENCE CONTRACT
One file. Eight evidence groups.
The manifest stays beside the policy on GitHub or Hugging Face. Null values are allowed structurally so the first scan can be saved; strict mode fails until every required claim is supplied.
Framework, pinned version, architecture, checkpoint
Robot family, gripper, sensors, calibration references
Control frequency, observation and action shapes
Repository, revision, feature schema, license
Resolved package versions and hashed declarations
Repository type, immutable revision, artifact version
Supported, unsupported, and untested hardware
Benchmark, trials, successes, evaluator, evidence
03 / RELIABLE AUTOMATION
Designed to fail usefully.
The scan ran. In default mode, an incomplete draft is still written so contributors can improve it.
The path, manifest, or filesystem could not be read. No misleading output is written.
Invalid evidence always fails. Strict or complete validation also fails on missing metadata; target comparison fails on mismatches or unknowns.
--format json returns stable finding codes, paths, severities, and a summary for CI.
Use --target ./target.yaml --no-write --format json to compare declared configurations. Equal shapes alone are not sufficient: feature semantics and calibration matter. A match never establishes safe physical transfer or independent reproduction.
STANDARDIZE IN THE OPEN
Use the format without joining a platform.
The schema, example, implementation, and tests are public. Keep the manifest with your policy and review it like code.