lerobot
Hugging Face LeRobot end to end: install, hardware bring-up, dataset recording, training, and deploying robot learning policies.
Install / Use
npx skills add arpitg1304/robotics-agent-skills --skill lerobotInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OperationsSupported Platforms
Tags
Our assessment of lerobot
lerobot scores 91/100 on our quality scale, 242nd of 763 Operations skills we index (top 32%).
Its SKILL.md is 22 KB long, well organised into 25 sections with 13 code examples: 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 lerobot is actively maintained.
- 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.
lerobot compared with similar skills
All 4 of these similar skills score higher than lerobot; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| lerobot (this skill)by arpitg1304 | 91 | 405 | 3d ago | SKILL.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 |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install lerobot?
- Run
npx skills add arpitg1304/robotics-agent-skills --skill lerobot. The install tabs above show the steps for each supported agent. - Which AI agents does lerobot 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 lerobot 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 lerobot still maintained?
- The repository was last updated 3 days ago, so lerobot is actively maintained.
Skill content
View source on GitHubname: lerobot description: > Hugging Face LeRobot end to end: install, hardware bring-up, dataset recording, training, and deploying robot learning policies. Use this skill when the user mentions LeRobot, lerobot-record, lerobot-train, lerobot-rollout, lerobot-teleoperate, lerobot-calibrate, lerobot-setup-motors, lerobot-find-port, lerobot-find-cameras, lerobot-eval, lerobot-edit-dataset, LeRobotDataset, SO-100, SO-101, SO-ARM100, Koch, LeKiwi, OMX, OpenArm, Feetech STS3215 servos, leader/follower teleoperation, calibration files, ACT, Diffusion Policy, SmolVLA, pi0/pi0.5, GR00T or X-VLA fine-tuning in LeRobot, robot datasets on the Hugging Face Hub, dataset v2.1 to v3.0 conversion, RTC or remote (async) inference, or HIL-SERL in LeRobot. Also trigger on LeRobot errors such as calibration mismatch, FrameTimestampError or timestamp tolerance violations, camera or feature name mismatch between dataset and policy, missing q01/q99 stats, and Feetech "Incorrect status packet".
LeRobot Skill
Verified against LeRobot 0.7.1 (commit 7e57397), 2026-11-18.
That is the main branch. The newest PyPI release on that date was 0.7.0. LeRobot changes
quickly between minor versions, so check what is installed before trusting any flag in this file
(see Check what you have). This file marks what was read in the
source or docs as verified. It marks recommendations that come from field experience as
advice.
Use a sibling skill instead for: choosing an IL algorithm, action representation or data
budget (imitation-learning). Auditing demo quality, outliers or label noise (robot-data-quality).
RL theory and reward design (robot-reinforcement-learning). Building MuJoCo or Isaac scenes
(mujoco, isaac-sim). Full scope list, pipeline diagram and draccus flag syntax:
overview.md.
Flags (verified): every CLI is a draccus dataclass. Nested fields are dotted flags
(--robot.port, --policy.chunk_size), type fields pick a registered subclass
(--robot.type=so101_follower), and dicts and lists are passed as YAML/JSON strings.
<command> --help is the ground truth for the installed version.
Contracts Between Stages
Six things tie the stages together. When one changes, the next stage breaks:
| Contract | Set where | Breaks when |
|---|---|---|
| --robot.id / --teleop.id | every hardware command | a different id loads a different calibration file, or none |
| Calibration file | $HF_LEROBOT_HOME/calibration/... | you recalibrate after recording, so positions shift |
| Camera names | --robot.cameras dict keys | they become observation.images.<name>, and the policy expects exactly those |
| Camera resolution and fps | camera config, --dataset.fps, --fps | deployment differs from training, or the loop cannot keep the rate |
| Joint units (use_degrees) | robot/teleop config | dataset in one unit, robot in another |
| Normalisation stats | dataset meta/stats.json, copied into checkpoint processors | stats missing, or taken from the wrong dataset |
Check What You Have First
lerobot-info # LeRobot, Python, torch, CUDA/MPS, ffmpeg, torchcodec versions
pip show lerobot | head -3 # installed version
lerobot-record --help | grep -A2 streaming # does this build have the flag I'm about to use?
# Registered types. A draccus ChoiceRegistry only knows the modules that have been imported, so import the CLI module first:
python -c "import lerobot.scripts.lerobot_record; from lerobot.robots import RobotConfig; print(sorted(RobotConfig.get_known_choices()))"
python -c "import lerobot.policies; from lerobot.configs.policies import PreTrainedConfig as P; print(sorted(P.get_known_choices()))"
Changes that make older tutorials wrong (verified in 0.7.x docs and source):
- Policy deployment moved from
lerobot-record --policy.pathtolerobot-rollout. In 0.7,lerobot-recordneeds a teleop and rejects dataset names starting witheval_. The cheat sheet sayslerobot-rolloutdoes not exist in v0.5.x and earlier. - Weights & Biases was replaced by Trackio. Use
--trackio.enable=trueinstead of--wandb.enable=true. Old checkpoints with awandbsection are migrated when loaded. - Python >= 3.12 is required (
requires-python = ">=3.12"). lerobot-recordappends_YYYYMMDD_HHMMSSto--dataset.repo_idunless you pass--dataset.no_stamp=true.- The dataset format is v3.0. A v2.1 dataset must be converted before 0.4+ can read it.
- Feetech and Dynamixel buses go through
rustypot(extrasfeetech/dynamixel).
Install (verified)
conda create -y -n lerobot python=3.12 && conda activate lerobot
conda install ffmpeg -c conda-forge # TorchCodec video decoding; system ffmpeg is OK only with torch >= 2.10
pip install 'lerobot[core_scripts,training,feetech]' # SO-100/101: record + train
# Policy extras as needed: smolvla | pi (pi0/pi0.5/pi0-FAST) | diffusion | groot | xvla | ...
pip install 'lerobot[smolvla]'
# From source (for reading or patching code):
git clone https://github.com/huggingface/lerobot && cd lerobot && pip install -e ".[core_scripts,training,feetech]"
core_scripts=dataset+hardware+viz(record, replay, calibrate, Rerun/Foxglove).training=dataset+accelerate+trackio.intelrealsenseis needed for RealSense cameras. Sim envs are extras too:pusht,aloha,libero(Linux only),metaworld.- Linux torch wheels from PyPI are CUDA 13 builds and need NVIDIA driver >= 580.65. For an older
driver, install torch from the
cu126index first (seedocs/source/installation.mdx). - Apple Silicon: MPS needs macOS 15+. On macOS 14, LeRobot falls back to CPU.
- Load policies.md for the policy-to-extra table.
SO-101 Bring-Up (follower + leader, wrist + overhead camera)
Do these steps in order. Each step relies on the one before it. Keep the shared values in one env file (advice) so every command uses the same ports, ids and camera dict:
# so101.env (source it in every shell: `source so101.env`)
export FOLLOWER_PORT=/dev/ttyACM0 LEADER_PORT=/dev/ttyACM1 # fill in from step 1
export FOLLOWER_ID=so101_follower_01 LEADER_ID=so101_leader_01 # never change after calibrating
1. Ports
lerobot-find-port # unplug the board when prompted; it prints that board's port
# macOS: /dev/tty.usbmodem5A7A0185331 Linux: /dev/ttyACM0
sudo usermod -aG dialout "$USER" # Linux, then log out/in (docs show `sudo chmod 666 /dev/ttyACM0`, which resets on replug)
ls -l /dev/serial/by-id/ # Linux advice: stable names; ttyACM0/1 can swap after reboot or replug
Advice: put the /dev/serial/by-id/... path in your variables. Then the leader and follower
cannot swap ports without you noticing.
2. Motor IDs and baudrate (once per arm, when new or reused)
lerobot-setup-motors --robot.type=so101_follower --robot.port=$FOLLOWER_PORT
lerobot-setup-motors --teleop.type=so101_leader --teleop.port=$LEADER_PORT
The script asks for one motor at a time, starting with gripper (ID 6) and ending at
shoulder_pan (ID 1). Only that motor can be connected to the board. It writes the ID and
baudrate to EEPROM. Waveshare jumpers, gear ratios: so101-hardware.md.
3. Calibration
lerobot-calibrate --robot.type=so101_follower --robot.port=$FOLLOWER_PORT --robot.id=$FOLLOWER_ID
lerobot-calibrate --teleop.type=so101_leader --teleop.port=$LEADER_PORT --teleop.id=$LEADER_ID
Procedure (verified from SerialMotorsBus.record_calibration):
- Torque turns off. Move every joint to the middle of its range and press ENTER. That pose becomes the zero (half-turn homing offset).
- Sweep each joint through its full range, then press ENTER.
wrist_rollis treated as a full-turn motor and is not swept. - The result is written to the motors and saved as JSON:
- follower:
~/.cache/huggingface/lerobot/calibration/robots/so_follower/<robot.id>.json - leader:
~/.cache/huggingface/lerobot/calibration/teleoperators/so_leader/<teleop.id>.json
- follower:
Commit or back up these JSON files next to your datasets. A policy is only valid with the calibration its data was recorded under. Dir overrides, reuse prompt: so101-hardware.md.
4. Teleoperate (check calibration before adding cameras)
lerobot-teleoperate \
--robot.type=so101_follower --robot.port=$FOLLOWER_PORT --robot.id=$FOLLOWER_ID \
--teleop.type=so101_leader --teleop.port=$LEADER_PORT --teleop.id=$LEADER_ID
Things to check (advice): the follower tracks the leader with no constant offset. The gripper opens
and closes fully. Nothing buzzes at rest. lerobot-teleoperate loops at --fps=60 by default and
prints a cadence summary when it exits.
5. Cameras
lerobot-find-cameras opencv # lists ids + default profile, saves frames to outputs/captured_images
lerobot-find-cameras realsense # needs lerobot[intelrealsense]; macOS may need sudo and is unstable
Define the camera dict once and reuse it in every command. Names and resolution must stay the same from recording to deployment:
# append to so101.env. Linux paths shown; on macOS use the integer ids from lerobot-find-cameras (index_or_path: 0 / 1)
export CAMERAS='{ wrist: {type: opencv, index_or_path: /dev/video2, width: 640, height: 480, fps: 30, fourcc: MJPG}, top: {type: opencv, index_or_path: /dev/video0, width: 640, height: 480, fps: 30, fourcc: MJPG} }'
lerobot-teleoperate ... --robot.cameras="$CAMERAS" --display_data=true # Rerun viewer
- Mount both cameras rigidly and light the scene evenly. A wrist camera mount that moves between sessions is a silent distribution shift.
- Camera fields, stable
/dev/v4lnames, USB bandwidth, RealSense: so101-hardware.md. Other robots (SO-100, bimanual, Koch, OMX, LeKiwi, OpenArm, ...): robots.md.
Recording Datasets
hf auth login # write token
HF_USER=$(NO_COLOR=1 hf auth whoami | awk -F': *' 'NR==1 {print $2}')
lerobot-record \
--robot.type=so101_follower --robot.port=$FOLLOWER_PORT --robot.id=$FOLLOWER_ID \
--robot.cameras="$CAMERAS" \
--teleop.type=so101_leader --teleop.port=$LEADER_PORT --teleop.id=$LEADER_ID \
--dataset.repo_id=${HF_USER}/so101_cube_to_bowl \
--dataset.single_task="Pick up the red cube and place it in the bowl" \
--dataset.num_episodes=50 --dataset.episode_time_s=30 --dataset.reset_time_s=15 \
--dataset.fps=30 \
--dataset.streaming_encoding=true --dataset.encoder_threads=2 \
--display_data=true
- Keys (verified):
→/nends the episode or reset early.←/rre-records the episode.ESC/qstops, encodes and uploads. - The saved name is
${HF_USER}/so101_cube_to_bowl_YYYYMMDD_HHMMSS. Find it withls ~/.cache/huggingface/lerobot/${HF_USER}and use that full name for resume, train and replay. - Resume an interrupted session or add episodes. Here
num_episodesmeans additional episodes:
On resume, robot_type, fps and the feature dict must match the existing dataset. A camera rename or resolution change failslerobot-record ...same robot/teleop/cameras... --resume=true \ --dataset.repo_id=${HF_USER}/so101_cube_to_bowl_20261118_143012 \ --dataset.root=$HOME/.cache/huggingface/lerobot/${HF_USER}/so101_cube_to_bowl_20261118_143012 \ --dataset.num_episodes=10sanity_check_dataset_robot_compatibility. - Read the cadence summary printed at the end of each episode and of the session. Frame
timestamps come from the frame index, so a loop that ran at 25 Hz still produces a dataset that
claims 30 Hz. If
observetakes most of the work ti
Truncated for display — read the full file on GitHub.
Related Skills
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.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
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.
