DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to try a duck goal in the simulator with no robot with Quackd

Run a goal like find the ball and kick it on a simulated Microduck with no hardware.

Authorization notice. Quackd is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA robotics hobbyist with no robot yet who wants to see how an LLM pilots a body before buying one.

The problemSetting up a robot just to test how goal-directed control works is expensive and slow.

The outcomeA goal runs to completion in the cartoon arena, and the run shows which skills the model chose.

What you need first

  • Python installed on a laptop or computer
  • An API key for one hosted model (Claude, OpenAI, Gemini, Grok and others), or a local model served by Ollama, vLLM, llama.cpp or LM Studio
  • For the simulated duck: the quackd[microduck] extra
  • For real hardware: a supported robot such as the SO-101 arm over LeRobot, plus its serial or USB connection

Steps

  1. Install Quackd with the microduck extra: pip install "Quackd[microduck]" (inferred, check the README)
  2. Register the simulated Microduck once by name using the Quackd registration command in the README (inferred, check the README)
  3. Run: Quackd run --goal "Find the ball and kick it"
  4. Read the run output and confirm the ball kick succeeded

Prompt for your agent

Using the rokbenko/quackd repo, install quackd[microduck], register a simulated Microduck under the name <robot-name>, then run quackd run --goal "Find the ball and kick it" against it. Report the final status and the list of skills the model called. Verify that the run ends with success rather than an abort.

Caveat. The cartoon simulator checks success against ground truth in a sprite arena, so a pass there does not show the real Microduck will kick a real ball.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page