Roadrunner Core
Connect to RoadRunner from MATLAB and manage project/scene/scenario lifecycle
Test report
- Verdict
- Works with setup
- Score
- Tested
- Jul 21, 2026
- Environment
- Claude Code 2.x (agent harness)
- Upstream re-checked
- Aug 10, 2026 · afb1dbe
Located SKILL.md at skills-catalog/automotive/roadrunner-core and fetched it raw along with both referenced scripts (rrCoreInitialize.m, rrCoreCommands.m both HTTP 200) and manifest.yaml. Frontmatter parses with name+description; the skill body's only path is a documented <absolute-path-to-this-skill> placeholder (no hardcoded machine paths), and rrCoreInitialize.m resolves the RoadRunner install via settings/workspace vars rather than guessing. No security smells: addpath/savepath persistence is the skill's stated purpose, no curl|sh, blobs, or exfiltration. Could NOT run the OUTPUT stage — every operation routes through the evaluate_matlab_code MCP tool against a live RoadRunner+MATLAB install I do not have, so no baseline-vs-skill artifact was produced (outputMeasured=false). Trigger phrasings judged: SHOULD fire — "connect to RoadRunner from MATLAB and open my highway project", "create a new RoadRunner scene and set the world origin", "close RoadRunner and check its status"; SHOULD NOT — "build a Simulink model for engine control", "write a MATLAB function to filter a noisy signal"; all 5 decided correctly.
Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works
- Installs cleanly 5/5
- Triggers reliably 5/5
- Output vs. baseline 5/10
- Docs & honesty 5/5
What Roadrunner Core does
Foundation skill for RoadRunner automation from MATLAB: sets up the API path, connects to or launches RoadRunner, and manages the project/scene/scenario lifecycle, world settings, status, and close, producing the rrApp handle other RoadRunner skills depend on. Triggers when connecting to RoadRunner, creating or opening projects/scenes/scenarios, setting world origin or scene bounds, checking status, or closing RoadRunner. Requires MATLAB R2022a+, a RoadRunner installation, Automated Driving Toolbox, and the evaluate_matlab_code MCP tool.
How to install Roadrunner Core
git clone --depth 1 https://github.com/matlab/matlab-agentic-toolkit.git /tmp/roadrunner-core-src
mkdir -p ~/.claude/skills
cp -R /tmp/roadrunner-core-src/skills-catalog/automotive/roadrunner-core ~/.claude/skills/roadrunner-core
# Requires (all external, not bundled):
# - MATLAB R2022a or later (changeWorldSettings needs R2023b+)
# - RoadRunner installed + Automated Driving Toolbox licensed
# - the evaluate_matlab_code MCP tool wired into the agent (all MATLAB runs through it; never matlab -batch)
# First run: agent addpaths <skill>/scripts, runs rrCoreInitialize. If it errors PathsRequired,
# supply installFolder + projectPath MATLAB vars and re-run (one-time, persisted via savepath/settings).
Skills live in ~/.claude/skills/ (global) or .claude/skills/
(per-project). Restart Claude Code after installing.
Commands — how to trigger Roadrunner Core
-
/roadrunner-coreConnect to RoadRunner from MATLAB and manage project/scene/scenario lifecycle
It also activates on plain-language prompts like these:
-
Connect to RoadRunner and open this project -
Set the world origin for this scene -
Check RoadRunner connection status and close it
Frequently asked questions
- Is the Roadrunner Core skill free?
- Yes. The skill itself is free from matlab/matlab-agentic-toolkit. SkillProof publishes the install command and an independent test verdict at no cost.
- Does Roadrunner Core work with Claude Code?
- We tested it with Claude Code 2.x (agent harness) on Jul 21, 2026. Verdict: Works with setup. Located SKILL.md at skills-catalog/automotive/roadrunner-core and fetched it raw along with both referenced scripts (rrCoreInitialize.m, rrCoreCommands.m both HTTP 200) and manifest.yaml. Frontmatter parses with name+description; the skill body's only path is a documented <absolute-path-to-this-skill> placeholder (no hardcoded machine paths), and rrCoreInitialize.m resolves the RoadRunner install via settings/workspace vars rather than guessing. No security smells: addpath/savepath persistence is the skill's stated purpose, no curl|sh, blobs, or exfiltration. Could NOT run the OUTPUT stage — every operation routes through the evaluate_matlab_code MCP tool against a live RoadRunner+MATLAB install I do not have, so no baseline-vs-skill artifact was produced (outputMeasured=false). Trigger phrasings judged: SHOULD fire — "connect to RoadRunner from MATLAB and open my highway project", "create a new RoadRunner scene and set the world origin", "close RoadRunner and check its status"; SHOULD NOT — "build a Simulink model for engine control", "write a MATLAB function to filter a noisy signal"; all 5 decided correctly.
- What is the Roadrunner Core SkillProof Score?
- 8.0/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 5/10, docs & honesty 5/5.
- How do I install Roadrunner Core?
- Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
- Can I use Roadrunner Core with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
- The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.