RoadRunner asset path lookup tables for map format conversions in MATLAB. Maps lane markings, signs, signals, barriers, objects, and lane types to RoadRunner asset paths.
SkillScore95Maintained
Automatic
◆Coding pack
Last verified 8/16/2026
What it changes
Passed 21 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill95%
Checks it passed that the model alone missed
Requires the .svg_rrx extension instead of .svg.
Requires the path value to start with Assets/ prefix.
Uses the .svg_rrx file extension for the fallback sign.
and 35 more in the full report
19 fixed2 passed either way0 still failing1 broke
Pass-rate lift
+82 pp
Tokens
+95%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 8/16/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 19 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 19
Prompt
If a Japanese map contains an unknown warning sign code that cannot be directly mapped to a specific speed or stop sign, what standard Japanese fallback sign path should be assigned?
What was checked, without and with the skill
Checked
Without skill
With skill
Assigns Assets/Signs/Japan/Regulatory Signs/SlowDown_JP_01.svg_rrx as the Japanese fallback sign asset path.
Missed
Passed
Uses the .svg_rrx file extension for the fallback sign.
Missed
Passed
case-21 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md227 lines6 files
RoadRunner Asset Mapping
Consolidated lookup tables for mapping source map format elements to RoadRunner project asset paths. All paths are relative to the project Assets/ folder.
When to Use
Resolving lane marking subtypes to RoadRunner .rrlms asset paths
Mapping sign codes (US MUTCD, German StVO, Japanese) to sign asset SVGs
Looking up barrier/extrusion asset paths for fence, guard rail, jersey barrier, wall
Finding prop/static object asset paths for placement in RRHD
Determining region-specific sign paths based on geoReference coordinates
Assigning lane type enums from source format lane classifications
When NOT to Use
Building RRHD objects from scratch — use roadrunner-rrhd-authoring
Performing the full Lanelet2 conversion pipeline — use roadrunner-convert-lanelet2-to-rrhd
Importing maps into RoadRunner — use roadrunner-import-scene
Key Rules
All asset paths start with Assets/ — always prefix when constructing RelativeAssetPath objects.
Extension matters..rrlms = lane marking style, .rrcws = crosswalk style, .rrpms = polygon marking style, .svg_rrx = sign. Using wrong extension causes "Asset file is missing" on import.
Signs use .svg_rrx extension (NOT .svg). The .svg paths in XML configs are internal references only.
Sign naming: descriptive English names with region suffix (e.g., Stop_JP_01.svg_rrx, MaxSpeedLimit_30_DE.svg_rrx). The old Sign_<code>.svg naming is obsolete.
Region detection from geoReference. Use lat/lon to determine Japan/Germany/US for sign and marking paths.
Runtime asset discovery is MANDATORY for signs. Asset names vary by version — always verify file exists before assigning.
Source Data
Asset mappings are derived from the official RoadRunner project configuration XMLs:
DefaultAssets.xml — default materials and markings
ApolloAssetData.xml — Apollo/Baidu HD Map format
OpenDriveAssetData.xml — OpenDRIVE format
HEREAssetData_NA.xml / HEREAssetData_WE.xml — HERE HD Map (NA/EU)
TomTomAssetData.xml — TomTom HD Map format
These XML files are located in the RoadRunner project's configuration directory (typically <RoadRunner Project>/Configuration/).