Install any skill in seconds. Free to start, no credit card required.
Get Started Free →matlab/roadrunner-build-scenario-from-osc
Build a RoadRunner Scenario programmatically from an OpenSCENARIO 1.x (.xosc) file using the `roadrunner-scenario-authoring` skill.
Passed 13 of 20 test cases with the skill, and 3 of 20 without it.
and 12 more in the full report
11 fixed3 passed either way8 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I have an existing OpenSCENARIO file `highway_merge.xosc` and I just want to import it directly into RoadRunner using the standard RoadRunner API call. How do I do this in MATLAB?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends using the built-in importScenario API call directly. | Missed | Passed |
| Does not output a multi-step Scenario Description breakdown. | Passed | Passed |
The instructions your model reads when the skill loads.
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.
importScenario(rrApp, xoscPath), not this skill. Simply call the API directly.importScenario (let them — it works for simple cases)roadrunner-scenario-authoring)roadrunner-export-scenario)Never fabricate actions or conditions not present in the source XOSC. If a construct cannot be mapped, skip it and warn the user.
Never propose workarounds. Do not replace DistanceToPointCondition with DurationCondition, do not substitute SimulationTimeCondition for unsupported triggers, do not add any construct not in the source.
Never simplify or duplicate trajectory vertices. Extract exactly the polyline vertices present in the source XOSC — no fewer, no more. Do not reduce 90 vertices to 5. Do not duplicate start/end points during extraction.
Never guess scenes. Only report the .xodr filename from <LogicFile>.
Import it — do not search for a scene with a similar name.
Never convert relative references to absolute. If the source uses
RelativeTargetSpeed delta=-8, preserve it as SpeedReference="actor" with
test cases passed, vs 3 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.