Embodied Task Decomposition
/install embodied-task-decomposition
Embodied Task Decomposition
This skill decomposes high-level natural language instructions into atomic subtasks that a robot can execute.
When to Use
- User provides an image AND a task instruction
- User asks to "decompose", "break down", or "split" a task
- User wants step-by-step actions for robot execution
Input Format
- Image: Photo of the physical scene (any environment: kitchen, office, outdoor, etc.)
- Task Instruction: Natural language description of what to accomplish
Example:
Task Instruction: take toasted bread from bread machine on white table place on plate
Image: [image path or description]
Output Format
Numbered list of subtasks, each following format:
{action} {target} {location/optional prepositional phrase} with {left/right/either} gripper
Process
- Analyze the image - Identify objects, surfaces, locations, tools visible
- Understand the task - What is the goal? What needs to be moved/ manipulated?
- Break into atomic actions - Each subtask = one action from the action bank
- Specify gripper - Always indicate left, right or either gripper
Action Bank
Refer to action-bank.md for the complete list of allowed actions. All subtasks MUST use actions from this bank.
Examples
See examples.md for detailed decomposition examples across different domains.
Important Notes
- Use ONLY actions from the action bank
- Each subtask = one primary action
- Always specify gripper (left/right/either)
- Include target object and location
- Keep subtasks atomic and sequential
- Consider object state changes (e.g., "open bag" before "take fruit")
Updating the Action Bank
The agent MAY add new actions to the action bank when needed. To add a new action:
- Check for duplicates - Search existing actions for similar functionality
- Verify functional difference - New action must serve a distinct purpose
- Add with documentation - Include description and example usage
Duplicate Check Criteria
A new action is considered a duplicate if it:
- Has the same name as an existing action
- Describes the same physical movement (e.g., "lift" vs "raise")
- Can be used interchangeably with an existing action in all contexts
Adding a New Action
When adding to action-bank.md, follow this format:
| action_name | Description | Example Usage |
|-------------|-------------|---------------|
| new_action | What it does | "new_action the object"
Example of adding "insert" (different from "place" - "place" = put on surface, "insert" = put into container):
| insert | Put object inside a container or slot | "insert the key into the lock"
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install embodied-task-decomposition - After installation, invoke the skill by name or use
/embodied-task-decomposition - Provide required inputs per the skill's parameter spec and get structured output
What is Embodied Task Decomposition?
Decompose complex physical tasks into atomic subtasks for robot execution. Use when user provides: (1) An image showing a physical scene (indoor/outdoor), an... It is an AI Agent Skill for Claude Code / OpenClaw, with 143 downloads so far.
How do I install Embodied Task Decomposition?
Run "/install embodied-task-decomposition" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Embodied Task Decomposition free?
Yes, Embodied Task Decomposition is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Embodied Task Decomposition support?
Embodied Task Decomposition is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Embodied Task Decomposition?
It is built and maintained by NaNaoiSong (@nanaoisong); the current version is v1.0.0.