datalisted

# data The data-sourcing umbrella for robium. Before any policy gets trained, something has to decide where the training data comes from — an existing hub dataset, data generated in simulation, or demonstrations collected via teleop on a real robot — and how it will be stored and versioned once it exists. This skill owns that selection and the cross-cutting sourcing rules; it does not own hub mechanics (`huggingface`), the LeRobotDataset format (`lerobot`), or the mechanics of generating synthetic data inside a simulator (`isaac-sim`, `gazebo`). It also does not own training itself — that is `lerobot` and `isaac-lab`'s territory. ## When to use this skill - Starting any robot-learning task and the data source isn't decided yet — this is a required early step for the manipulation vertical, the same way `environments` is a required early step for reproducibility. - The trigger phrases in the description: 'where do we get data', 'training data for the robot', 'dataset for manipulation', 'generate data in sim', 'collect demonstrations'. - Planning storage format, episode structure, or dataset versioning before a collection or generation effort starts, not after. - Cross-references — go to the sibling skill instead when the question is: - Actually pulling, pushing, or browsing a dataset on the Hub → `huggingface`. This skill decides *which* dataset or source strategy to use; it does not own hub auth or transfer mechanics. - The LeRobotDataset directory/Par