--- license: apache-2.0 task_categories: - reinforcement-learning - other language: - code tags: - minecraft - expert-demonstrations - skill-segmentation - action-segmentation - object-centric pretty_name: Minecraft Skill Segmentation Dataset size_categories: - 1K groundTruth label "0": "chop_tree", "1": "craft_table", "2": "mine_stone", ... } } ``` ## Dataset Creation ### Curation Rationale This dataset was created to support research in skill discovery and temporal abstraction in complex, open-ended environments like Minecraft. The environment supports high-level goals and diverse interactions, making it suitable for testing generalizable skills. ### Source Data #### Data Collection and Processing - Expert trajectories were generated using a scripted or trained policy within the Minecraft simulation. - Skill labels were added based on environment signals (e.g., changes to inventory, task completions, block state transitions) and verified using heuristics. #### Who are the source data producers? The data was generated programmatically in the Minecraft simulation environment by expert agents using scripted or learned behavior policies. ### Annotations #### Annotation process Skill annotations were derived from internal game state events and heuristics related to player intent and task segmentation. Manual inspection was performed to ensure consistency across trajectories. #### Who are the annotators? Automated rule-based annotation systems with developer oversight during dataset development. ## Bias, Risks, and Limitations - The dataset is derived from simulation, so its findings may not generalize to real-world robotics or broader RL environments. - Skill definitions depend on domain-specific heuristics, which may not reflect all valid strategies. - Expert strategies may be biased toward specific pathways (e.g., speedrunning logic). ### Recommendations Researchers should evaluate the robustness of learned skills across diverse environments and initial conditions. Segmentations reflect task approximations and should be interpreted within the scope of the simulation constraints.