How do I install the Roboneuron skill?

Run npx skillmds@latest add tomevault-io/roboneuron in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Roboneuron safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Roboneuron?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Roboneuron free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Roboneuron?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Roboneuron by tomevault-io — Agent Skill

Name: Roboneuron
Author: tomevault-io

File contents

Use this skill when the task involves controlling RoboNeuron through its MCP servers from OpenClaw.

Scope:

Robot perception/control/VLA bring-up through RoboNeuron MCP.
Inspecting available RoboNeuron tools with mcporter.
Starting or stopping the RoboNeuron MCP daemon/runtime paths used by OpenClaw.

Required command form:

Always invoke mcporter with --config /home/guanweifan/RoboNeuron/configs/openclaw/mcporter.json.
Never rely on editor-imported MCP configs for RoboNeuron.

Startup order:

For camera-only workflows, use roboneuron-perception.
For motion/control workflows, start roboneuron-control before sending end-effector commands.
For instruction-conditioned policy execution, start roboneuron-perception, then roboneuron-control, then roboneuron-vla.
Use roboneuron-twist only for /cmd_vel style base motion publishing.
Use roboneuron-eef-delta for direct end-effector delta commands.

Useful commands:

mcporter --config /home/guanweifan/RoboNeuron/configs/openclaw/mcporter.json list
mcporter --config /home/guanweifan/RoboNeuron/configs/openclaw/mcporter.json list roboneuron-control --schema
mcporter daemon status
mcporter daemon restart --log

Rules:

Treat RoboNeuron MCP servers as stateful and persistent. Do not replace them with ad-hoc --stdio calls unless explicitly debugging.
Reuse configured server names (roboneuron-perception, roboneuron-vla, roboneuron-control, roboneuron-twist, roboneuron-eef-delta).
If a tool call fails after a crash or stale connection, restart the daemon with mcporter daemon restart.

References:

references/startup-order.md
references/troubleshooting.md

Source: guanweifan/RoboNeuron — distributed by TomeVault.

---name: roboneurondescription: Control RoboNeuron through its project-scoped MCP servers via mcporter. Use when this capability is needed.---Use this skill when the task involves controlling RoboNeuron through its MCP servers from OpenClaw.Scope:- Robot perception/control/VLA bring-up through RoboNeuron MCP.- Inspecting available RoboNeuron tools with `mcporter`.- Starting or stopping the RoboNeuron MCP daemon/runtime paths used by OpenClaw.Required command form:- Always invoke `mcporter` with `--config /home/guanweifan/RoboNeuron/configs/openclaw/mcporter.json`.- Never rely on editor-imported MCP configs for RoboNeuron.Startup order:1. For camera-only workflows, use `roboneuron-perception`.2. For motion/control workflows, start `roboneuron-control` before sending end-effector commands.3. For instruction-conditioned policy execution, start `roboneuron-perception`, then `roboneuron-control`, then `roboneuron-vla`.4. Use `roboneuron-twist` only for `/cmd_vel` style base motion publishing.5. Use `roboneuron-eef-delta` for direct end-effector delta commands.Useful commands:- `mcporter --config /home/guanweifan/RoboNeuron/configs/openclaw/mcporter.json list`- `mcporter --config /home/guanweifan/RoboNeuron/configs/openclaw/mcporter.json list roboneuron-control --schema`- `mcporter daemon status`- `mcporter daemon restart --log`Rules:- Treat RoboNeuron MCP servers as stateful and persistent. Do not replace them with ad-hoc `--stdio` calls unless explicitly debugging.- Reuse configured server names (`roboneuron-perception`, `roboneuron-vla`, `roboneuron-control`, `roboneuron-twist`, `roboneuron-eef-delta`).- If a tool call fails after a crash or stale connection, restart the daemon with `mcporter daemon restart`.References:- `references/startup-order.md`- `references/troubleshooting.md`---> Source: [guanweifan/RoboNeuron](https://github.com/guanweifan/RoboNeuron) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Roboneuron