agentleFS
hiteshbandhuhiteshbandhu/skills-i-use/skills/ai-engineer-talks/build-robotics-ai/SKILL.md

build-robotics-ai

Skill1 starsChanged 5 months agoMITView on GitHub

Runs workflows for robotics/autonomy talks — lab co-scientist loops, Optimus systems latency, kitchen supervised autonomy, Waymo EMMA, GR00T N1 humanoid FM, open $9k humanoids. Use when the user builds robots, humanoids, AV planning, or lab automation agents.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the decision tree below.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build robotics AI systems

Action playbook from six AI Engineer / World's Fair talks. Do not summarize talks — pick a workflow and execute it.

Supporting files (read when needed):

  • workflows.md — workflows A–F (steps, deliverables, stop conditions)
  • source-index.md — src-NNN → talk learnings in ingest-into-skills

Optional: {SKILL_OUTPUT_DIR}/build-robotics-ai/


Step 0 — Pick workflow

Use the decision tree below. Open the matching section in workflows.md.

What is the user trying to do?
├─ Closed-loop lab / co-scientist agent                  → A
├─ Humanoid systems performance (latency/data)         → B
├─ Commercial kitchen/service robotics                 → C
├─ AV + VLM planning (Waymo EMMA)                      → D
├─ Adopt humanoid foundation model (GR00T)             → E
└─ Ship affordable open humanoid platform              → F

Stop summarizing once a workflow is identified — run its checklist.


Install

cp -r skills/build-robotics-ai ~/.claude/skills/
cp -r skills/build-robotics-ai ~/.cursor/skills/
cp -r skills/build-robotics-ai ~/.codex/skills/

From skills-i-use or ingest-into-skills (playlists/robotics-autonomy-ai-engineer/).


Cross-cutting rules

RuleSource
Profile end-to-end control latency[src-002 @ 7:11]
Sim/real eval before planner changes[src-004 @ 14:16]
Teleop safety before full autonomy[src-006 @ 10:29]

Disputed steps: see source-index.md. Name workflow A–F; save artifacts to ./skill-outputs/build-robotics-ai/ when requested; do not auto-commit.


Invocation examples

@build-robotics-ai humanoid data pipeline architecture
lab agent with live sensors

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.