robium
Physical AI skills for coding agents, with field-tested robotics guidance, the robium-ai CLI, and a learning engine.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/robium-ai--robium)HTML
<a href="/listings/robium-ai--robium"><img src="/api/listings/robium-ai--robium/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
You need Node.js 18+, Git, and at least one supported coding agent.
npx robium-ai setup npx robium-ai doctor
Setup detects your agents and asks where to create the workspace. To install for one agent or choose the location up front:
npx robium-ai setup --agent codex npx robium-ai setup --dir ~/projects/my-robotics
This is an **editable install**, not a hidden package snapshot. Setup creates ordinary Git checkouts and connects your agent to them:
~/robium-workspace/ # default; location and name are your choice ├── robium/ # editable skills and plugin source └── robium-apps/ # runnable reference applications
Run `npx robium-ai workspace` anytime to find them. After editing or manually updating Robium, run `npx robium-ai setup` again and restart your agent so its integration refreshes.
Install skills only
To add Robium's skills to an existing project with the [skills CLI](https://skills.sh/), run:
npx skills add robium-ai/robium
Choose skills interactively, or select them by name:
npx skills add robium-ai/robium --skill ros2 gazebo mujoco
This installs the skill instructions and their supporting files. For the complete Robium workspace, reference applications, and plugin integration, use `npx robium-ai setup` above.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 17 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- {
- "name": "robium",
- "owner": {
- "name": "robium-ai"
- },
- "metadata": {
- "description": "Self-improving robotics skills for coding agents",
- "version": "0.5.2"
- },
- "plugins": [
- {
- "name": "robium",
- "source": "./",
- "description": "Self-improving robotics expertise for AI agents: stack selection, simulation, visualization, data, testing, and training skills for physical-AI applications"
- }
- ]
- }
README.md · README · 171 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <div align="center">
- <picture>
- <source media="(prefers-color-scheme: dark)" srcset="assets/brand/robium-lockup-dark.png">
- <img src="assets/brand/robium-lockup.png" alt="robium" width="360">
- </picture>
- ### Physical AI skills for coding agents
- Robium gives Claude Code, Codex, Gemini CLI, and Cursor field-tested robotics
- skills, troubleshooting guidance, and runnable reference applications. Start
- with a working robot, then ask your agent to adapt it.
- [](https://github.com/robium-ai/robium/actions/workflows/skills.yml)
- [](https://skills.sh/robium-ai/robium)
- [](https://robium.ai)
- [](https://www.npmjs.com/package/robium-ai)
- [](./LICENSE)
- [](https://robium.ai/join/discord)
- </div>
- ## Introducing Robium
- https://github.com/user-attachments/assets/90eed7a7-d240-4e64-bd2a-6a7d6290be46
- [Watch on YouTube](https://www.youtube.com/watch?v=y1a3PakIQsQ)
- ## Install
- You need Node.js 18+, Git, and at least one supported coding agent.
- ```bash
- npx robium-ai setup
- npx robium-ai doctor
- ```
- Setup detects your agents and asks where to create the workspace. To install
- for one agent or choose the location up front:
- ```bash
- npx robium-ai setup --agent codex
- npx robium-ai setup --dir ~/projects/my-robotics
- ```
- This is an **editable install**, not a hidden package snapshot. Setup creates
- ordinary Git checkouts and connects your agent to them:
- ```text
- ~/robium-workspace/ # default; location and name are your choice
- ├── robium/ # editable skills and plugin source
- └── robium-apps/ # runnable reference applications
- ```
- Run `npx robium-ai workspace` anytime to find them. After editing or manually
- updating Robium, run `npx robium-ai setup` again and restart your agent so its
- integration refreshes.
- ### Install skills only
- To add Robium's skills to an existing project with the
- [skills CLI](https://skills.sh/), run:
- ```bash
- npx skills add robium-ai/robium
- ```
- Choose skills interactively, or select them by name:
- ```bash
- npx skills add robium-ai/robium --skill ros2 gazebo mujoco
- ```
- This installs the skill instructions and their supporting files. For the
- complete Robium workspace, reference applications, and plugin integration,
- use `npx robium-ai setup` above.
- ## Try a working robot
- Restart your agent after setup, open it in a folder where it may work, and paste
- one of these prompts. Robium will inspect the matching reference app, check the
- prerequisites, and aim for a visible result before suggesting custom work.
- ### Map and navigate a simulated home
- <a href="https://github.com/robium-ai/robium-apps/tree/main/robot-navigation"><img src="https://raw.githubusercontent.com/robium-ai/robium-apps/main/robot-navigation/assets/stills/readme-navigation.png" alt="A simulated TurtleBot mapping and navigating a home" width="700"></a>
- > Map a simulated house with ROS 2, Gazebo, and SLAM, then navigate the robot to a goal.
- This uses the stable `robot-navigation` example with ROS 2, Nav2, Gazebo, and a
- bundled browser viewer. Docker with Compose v2 is required. A successful first
- run creates and saves a map, localizes the robot on it, and reaches a navigation
- goal.
- To run the example directly instead:
- ```bash
- npx robium-ai app doctor robot-navigation
- npx robium-ai app run robot-navigation
- ```
- ### Run a pretrained two-arm policy
- > Help me run a pretrained policy that transfers a cube between two simulated robot arms.
- This uses the official ACT checkpoint in `act-aloha-cube-transfer`. There is no
- training step and no dedicated GPU is required. The first run prepares the
- locked environment and downloads the pinned model; success means the viewer
- opens, real inference runs, and the default cube-transfer result is reported.
- ```bash
- npx robium-ai app doctor act-aloha-cube-transfer
- npx robium-ai app run act-aloha-cube-transfer
- ```
- The native path is tested on Apple Silicon. Ask your agent to check the app
- README before using another platform.
- ### Build a robot assistant
- > Help me build a simulated robot assistant that understands what it sees and follows natural-language instructions.
- This starts from `silly-turtlebot`: a camera-equipped TurtleBot simulation with
- guarded navigation tools. It requires Docker and your own authorized Gemini
- Robotics access. Live model calls may cost money, so Robium checks access before
- starting and will not present a mock run as a live result.
- More applications and hosted demos are at [robium.ai](https://robium.ai) and in
- [robium-apps](https://github.com/robium-ai/robium-apps).
- ## Make it yours
- Keep the shipped examples clean and create an editable derivative in your own
- `my-apps/` directory:
- ```bash
- npx robium-ai app new my-navigation --from robot-navigation
- ```
- Then open that new app with your coding agent and describe one change. Robium
- will reuse the proven environment and test shape instead of rebuilding the
- whole stack from scratch.
- Useful commands:
- ```bash
- npx robium-ai app list # browse every reference app
- npx robium-ai skills nav # search the skill catalog
- npx robium-ai update --check # check upstream without changing files
- npx robium-ai update # update clean main branches safely
- ```
- ## What is included
- - Skills for ROS 2, Nav2, Gazebo, MuJoCo, Isaac Sim/Lab, LeRobot, robot data,
- visualization, testing, and deployment.
- - An architect that selects a compatible reference app and proves the smallest
- useful robot behavior first.
- - Capture and learning tools that turn verified build findings into better
- guidance without requiring raw agent transcripts.
- - A zero-dependency CLI for setup, diagnosis, updates, skills, and application
- lifecycle commands.
- See the [CLI guide](cli/README.md) for host-specific setup and update behavior,
- or [CONTRIBUTING.md](CONTRIBUTING.md) to improve a skill. Questions are welcome
- on [Discord](https://robium.ai/join/discord) and in
- [GitHub Discussions](https://github.com/robium-ai/robium/discussions).
- ## License
- [MIT](LICENSE)
scripts/bootstrap.sh · Bundled script · 64 lines · 1 finding marked
- #!/usr/bin/env bash
- # robium dev bootstrap — run from a clone: ./scripts/bootstrap.sh
- #
- # DEFAULT (anyone, incl. public contributors — NO secrets, NO Doppler needed):
- # installs uv + npm deps and runs the repository check. That's all you need to
- # author skills and work on the CLI locally.
- # ./scripts/bootstrap.sh
- #
- # MAINTAINER / OPERATOR (adds Doppler-managed secrets — only for publishing the
- # CLI, deploying the site, RunPod/NGC/GCP work):
- # ./scripts/bootstrap.sh --secrets # laptop (after `doppler login`)
- # DOPPLER_TOKEN=dp.st.dev.… ./scripts/bootstrap.sh # server (auto-enables)
- set -euo pipefail
- say() { printf '\033[1;36m▸ %s\033[0m\n' "$*"; }
- # run from the repo (the script lives in scripts/, so root is one level up)
- ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
- cd "$ROOT"
- [ -f skills/skill-author/scripts/validate_skills.py ] || {
- echo "Run this from a robium clone (./scripts/bootstrap.sh)." >&2; exit 1; }
- # secrets are OPT-IN: --secrets flag, or DOPPLER_TOKEN present (server case)
- WITH_SECRETS=0
- [ "${1:-}" = "--secrets" ] && WITH_SECRETS=1
- [ -n "${DOPPLER_TOKEN:-}" ] && WITH_SECRETS=1
- # 1) Toolchain + deps (no secrets involved) ----------------------------------
- command -v uv >/dev/null 2>&1 || { say "Installing uv…"; curl -LsSf https://astral.sh/uv/install.sh | sh; }
- if command -v npm >/dev/null 2>&1; then
- [ -d cli ] && { say "npm deps: cli/"; (cd cli && npm ci --silent 2>/dev/null || npm install --silent); }
- fi
- # 2) Sanity check the core dev loop works (no secrets) -----------------------
- if command -v uv >/dev/null 2>&1; then
- say "Running repository checks…"; ./scripts/check.sh
- fi
- # 3) Secrets (maintainer-only, opt-in) ---------------------------------------
- if [ "$WITH_SECRETS" = "1" ]; then
- say "Secrets: setting up Doppler…"
- if ! command -v doppler >/dev/null 2>&1; then
- if command -v brew >/dev/null 2>&1; then brew install dopplerhq/cli/doppler
- else curl -Ls https://cli.doppler.com/install.sh | sh; fi
- Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
- Line 42 on GitHub
- fi
- if [ -z "${DOPPLER_TOKEN:-}" ] && ! doppler whoami >/dev/null 2>&1; then
- echo " Need Doppler auth: run 'doppler login' or set DOPPLER_TOKEN, then re-run with --secrets." >&2
- else
- [ -z "${DOPPLER_TOKEN:-}" ] && doppler setup --no-interactive -p robium -c dev >/dev/null
- if doppler run --project robium --config dev -- sh -c 'test -n "${NPM_TOKEN:-}"' >/dev/null 2>&1; then
- say "Doppler secrets reachable ✓ — run privileged tasks with: doppler run -- <cmd>"
- else
- echo " Could not read secrets — check DOPPLER_TOKEN / login." >&2
- fi
- fi
- else
- say "Secrets skipped (maintainer-only: CLI publish, site deploy, RunPod/NGC/GCP)."
- echo " Need them? re-run: ./scripts/bootstrap.sh --secrets (see docs/secrets.md)"
- fi
- cat <<DONE
- ▸ robium ready.
- Contribute (no secrets): ./scripts/check.sh
- Privileged tasks: doppler run -- <command> (after --secrets setup)
- DONE
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.