Microduck Workshop
GitHub ↗

SELF-PACED WORKSHOP

Organize tasks and accumulate skills with ASPIRE

Let a model propose plans, call skills, inspect feedback and revise programs; distinguish ASPIRE, GR00T and Agnes Harness.

Chapter 8 · Estimated learning time: 25 minutes

A reasoning model needs executable robot interfaces

“Go around the chair and send the ball into the goal” combines goal interpretation, subtask organization and motion. A model can propose and revise a plan, while controllers maintain balance and handle contact. A complete plan may require both a high-level sequence and a geometric route; prose alone does not supply either validated execution or collision avoidance.

Scroll horizontally to view the full diagram

Connect reasoning, skill execution and feedback while retaining continuous motor control.Task agent: Interpret the goal; choose the next step → Skill interface: Observe, move, contact and stop → Action policy: GR00T or existing motor policies → Feedback: Images, progress, failures and outcome predicatesTask agentInterpret the goal; choose the next stepSkill interfaceObserve, move, contact and stopAction policyGR00T or existing motor policiesFeedbackImages, progress, failures and outcomepredicatesConnect reasoning, skill execution and feedback while retaining continuous motor control.Task agent: Interpret the goal; choose the next step → Skill interface: Observe, move, contact and stop → Action policy: GR00T or existing motor policies → Feedback: Images, progress, failures and outcome predicatesTask agentInterpret the goal; choose the next stepSkill interfaceObserve, move, contact and stopAction policyGR00T or existing motor policiesFeedbackImages, progress, failures and outcomepredicates
Connect reasoning, skill execution and feedback while retaining continuous motor control.

ASPIRE: turn attempts into reusable experience

ASPIRE uses code-as-policy: an agent generates control programs, inspects multimodal execution traces, diagnoses failures, revises code and retains validated experience in a skill library. This learning primarily updates programs and skill knowledge, rather than necessarily updating neural weights. The public October 2026 v1.0 workflow includes iterative debugging and evolutionary search.

Scroll horizontally to view the full diagram

Revise from execution feedback and reuse skills after validation.Propose: Retrieve skills and generate a program → Execute and observe: Record images, actions, states and outcomes → Diagnose and revise: Locate failure and change the next attempt → Retain: Add skills after development validationProposeRetrieve skills and generate a programExecute and observeRecord images, actions, states and outcomesDiagnose and reviseLocate failure and change the next attemptRetainAdd skills after development validationRevise from execution feedback and reuse skills after validation.Propose: Retrieve skills and generate a program → Execute and observe: Record images, actions, states and outcomes → Diagnose and revise: Locate failure and change the next attempt → Retain: Add skills after development validationProposeRetrieve skills and generate a programExecute and observeRecord images, actions, states and outcomesDiagnose and reviseLocate failure and change the next attemptRetainAdd skills after development validation
Revise from execution feedback and reuse skills after validation.

For example, missing goal-post bases on a pale floor can prompt inspection of images and failure records, followed by another viewpoint or a revised perception interface. A program exiting normally is not a goal, and redefining scoring to pass a trial is not an improvement. The reusable output is a tested method.

Adapting the framework to Microduck

InterfaceReusable foundationRemaining integration
ObservationRGB, ToF, IMU and joint recordsConsistent timing, frames and observation age
ActionWalking, skating, kicking and stoppingBounded calls, timeouts, cancellation and mode semantics
OutcomeContact, crossing, fall and recovery checksDiagnostic feedback plus independent scoring
Skill libraryExisting control and failure knowledgeValidate new programs on unseen starts/scenes

Official examples target LIBERO-Pro, Robosuite, BEHAVIOR-1K and documented real-arm systems. There is no ready Microduck adapter for this course. Renaming arm joints does not turn end-effector control into biped control. Reuse ASPIRE’s exploration and skill-library approach while implementing body-motion and football interfaces for Newton.

Extension: where Agnes Harness fits

AspectASPIREAgnes Harness
FocusRefine robot programs and skills through executionConnect models, tools, task state and devices
ReuseValidated robotic skill librariesSkills, sessions and execution records
Current scopeRobotic exploration/research workflowsDeveloper-preview general agent harness
Course roleMain task-agent methodologyOptional device-integration comparison

They share concepts but are not equivalent products. Agnes’s MHS device integration and plugins merit study, but the inspected public main branch contains no ready Microduck adapter. We keep it as an extension rather than repeat the agent loop in another full chapter.

The linked Microduck community demo is a useful reference for questions about action tools, completion checks and recovery. Its page was unavailable in this review environment; its implementation and autonomy level have not been independently verified or counted as course results.

Feasible with an adapter and independent evaluation

The method and open interfaces are promising. A Microduck execution bridge, skill library and autonomous exploration trials remain to be implemented. Begin with observe, bounded movement, stop and check, then extend to football. Separate development and held-out seeds, bound trial budgets and record success, recovery and model-call costs.

References