roadrunner-build-scenario-from-osc
Build a RoadRunner Scenario programmatically from an OpenSCENARIO 1.x (.xosc) file using the `roadrunner-scenario-authoring` skill. Use when the user wants to recreate a scenario from a .xosc file, interpret an OpenSCENARIO file and build it programmatically, reconstruct a .xosc as a RoadRunner scenario, generate a MATLAB script from a .xosc file, or convert an OpenSCENARIO file to MATLAB code. Do NOT use when the user says "import" a .xosc file — that means they want RoadRunner's built-in importScenario API, not programmatic reconstruction. Handles position translation (LanePosition and RoadP
npx skills add matlab/matlab-agentic-toolkit --skill roadrunner-build-scenario-from-osc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Build RoadRunner Scenario from OpenSCENARIO Interpret an OpenSCENARIO 1.x (.xosc) file and recreate the scenario in RoadRunner using the `roadrunner-scenario-authoring` skill. Translates positions, maps constructs, preserves relative references, and builds correct phase logic. ## When to Use - User has a .xosc file and wants to recreate it in RoadRunner - User wants to programmatically build a scenario from OpenSCENARIO - User says "build this .xosc in RoadRunner" or "recreate this scenario" - User has an OpenSCENARIO file from a partner or standards body (e.g., Euro NCAP, ALKS) - User wants to generate a MATLAB script from a .xosc file - User says "convert this xosc to matlab" or "recreate with a matlab script" ## When NOT to Use - User says "import" a .xosc file — they want `importScenario(rrApp, xoscPath)`, not this skill. Simply call the API directly. - User wants to use RoadRunner's built-in `importScenario` (let them — it works for simple cases) - User wants to create a scenario from scratch **without** a .xosc file (use `roadrunner-scenario-authoring`) - User wants to export a scenario TO OpenSCENARIO (use `roadrunner-export-scenario`) ## Critical Rules 1. **Never fabricat
- When to Use
- When NOT to Use
- Critical Rules
- Workflow
- Step 1: Analyze the .xosc and Produce a Scenario Description
- Step 2: Build the Scenario via Dependent Skills
- References
- Common Mistakes
- Conventions
What does the roadrunner-build-scenario-from-osc skill do?
Build a RoadRunner Scenario programmatically from an OpenSCENARIO 1.x (.xosc) file using the `roadrunner-scenario-authoring` skill. Use when the user wants to recreate a scenario from a .xosc file, interpret an OpenSCENARIO file and build it programmatically, reconstruct a .xosc as a RoadRunner scenario, generate a MATLAB script from a .xosc file, or convert an OpenSCENARIO file to MATLAB code. Do NOT use when the user says "import" a .xosc file — that means they want RoadRunner's built-in importScenario API, not programmatic reconstruction. Handles position translation (LanePosition and RoadP
How do I install it?
Run `npx skills add matlab/matlab-agentic-toolkit --skill roadrunner-build-scenario-from-osc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From matlab/matlab-agentic-toolkit, a repository with 868 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.