Tarard Torii SUMO Expert Skill
Purpose
Use this skill as a router and evidence gate for Eclipse SUMO/TraCI traffic-signal experiments. Do not treat it as a full tutorial. First identify the user's scenario, then load only the reference files needed for that path.
Default loop:
request -> classify scenario -> load minimal references -> ask or act -> verify evidence -> bound the claim
Start Here
| Scenario | Load | Expected output |
|---|---|---|
| SUMO environment, executable toolchain, or runnable smoke proof is missing | references/preflight-sumo-environment.md |
Environment Preflight record and pass/fail route |
| Torii MCP execution, installable plugin use, MCP tool output, or feedback from a SUMO run | references/mcp-tool-routing.md |
MCP Tool Use Record, feedback diagnosis, and claim boundary |
| OSM-to-SUMO network construction, imported-network cleanup, road-detail planning, reference-matched network building, or Netedit/HTML review artifacts | references/osm-to-sumo-workflow.md |
OSM cleanup workflow contract, planning gate, reality/TLS gates, connectivity, routeability, HTML review, Netedit launch, and claim boundary |
| Region-specific map/TLS reality checks, detector lane mapping, field-data sensor alignment, or background visualization | references/model-osm-detectors.md |
map baseline record, TLS review evidence, detector alignment gates, and diagnostic background visualization boundary |
| Public OSM import libraries, Overpass robustness, offline PBF import, SUMO OSM scripts, OpenDRIVE conversion, or source-code reuse decisions | references/osm-source-patterns.md |
source-pattern map, integration ladder, no-vendoring boundary, and region-aware temporal baseline |
| Detector-constrained SUMO demand reconstruction from real count sensors, route priors, route-incidence matrices, routeSampler residual correction, or month-long count-matched validation | references/detector-constrained-demand-reconstruction.md |
workflow contract, detector/route/time-bin gates, public-data boundary, residual-correction ladder, and completion-first validation record |
| Ongoing project, unclear progress, repo/logs/outputs provided, or "what next?" | references/route-project-workflow.md |
Project Control Screen and next-step plan |
| New, vague, or assumption-heavy experiment | references/interactive-experiment-intake.md |
one-question-at-a-time intake, recommended answers, and readiness route |
| Confirmed experiment intake ready for planning | references/plan-experiment.md |
Experiment Readiness Record, then SUMO Experiment Plan |
| SUMO/TraCI failure, suspicious behavior, warnings, or broken run evidence | references/route-project-workflow.md plus references/develop-and-verify-code.md |
root-cause hypothesis, next probe, fix/rerun/demotion |
| Controller, parser, runner, validator, or audit-code change | references/develop-and-verify-code.md |
RED/GREEN/REFACTOR or explicit test-after record |
| Controller/TLS/NEMA/TraCI boundary question | references/audit-sumo-controllers.md |
controller identity, API boundary, and missing evidence |
| Applying controller families inspired by sumolights, including max-pressure, Webster, SOTL, fixed-time, actuated, or custom TLS control | references/sumolights-controller-patterns.md plus references/audit-sumo-controllers.md |
Controller Application Plan and Controller Identity Record |
| Mechanism-isolated corridor perturbation comparison, localized impact-signal tests, or multi-baseline controller evidence | references/compare-corridor-perturbations.md |
controlled-scope experiment logic, paired metrics, negative controls, and claim boundary |
| SUMO semantics, official/forum lessons, or public-code pattern | references/learn-sumo-knowledge.md |
source-bounded lesson and evidence requirement |
| Results, metrics, baseline comparison, or paper/report claim | references/evaluate-and-report-results.md |
evidence class and allowed/prohibited claim wording |
| User found a fix this skill missed | references/capture-field-lesson.md |
privacy-safe field lesson candidate; ask before persisting |
| Public release or repository exposure check | references/release-project.md |
release checklist and residual risk |
If a target/current-state/deviation cannot be inferred, switch to the intake path before running experiments or endorsing claims.
Core Rules
- Load the minimum reference set for the scenario; do not bulk-load every file.
- Preserve the one-sentence workflow. Infer safe defaults, run bounded diagnostic steps, and ask only truly blocking questions; missing map/TLS reality evidence should block clean/experiment-ready claims without preventing construction, routeability checks, SUMO-GUI, or Netedit review artifacts.
- Confirm missing experiment assumptions before formal execution or comparison.
- Prove the SUMO environment before formal experiment work when
sumo,duarouter,SUMO_HOME, Python,traci, or output generation has not been verified. - Separate what SUMO loaded, what the controller did, what outputs were written, what warnings/failures occurred, and what claim is supportable.
- Compare controllers only with paired route, demand, seed, horizon, outputs, and completion criteria.
- Do not use GUI inspection, clean execution, or arrived-only metrics as sufficient evidence.
- If completion differs across methods, report completion/unfinished/teleport status before travel-time, waiting-time, or delay averages.
- Treat bad metrics, warnings, teleports, unfinished vehicles, and controller logs as feedback signals. Diagnose what the metric implies before changing code, routes, networks, signal plans, or controller parameters.
- Use these claim labels:
formal-evidence,diagnostic-demo,stress-diagnostic,construction-invalid,claim-overreach,blocked. - At the end of each SUMO experiment or experiment-code pass, check whether the run produced a reusable SUMO/TraCI lesson. If yes, update the relevant skill reference instead of leaving the lesson only in the chat.
Reference Map
Load these only when the scenario requires them:
- Ongoing project routing, state screening, or "what next?":
references/route-project-workflow.md. - Torii MCP execution, tool-output interpretation, feedback diagnosis, and installable plugin behavior:
references/mcp-tool-routing.md. - SUMO/TraCI failure, suspicious behavior, warnings, or broken run evidence: start with
references/route-project-workflow.md; usereferences/develop-and-verify-code.mdbefore code, parser, runner, validator, or controller changes. - SUMO executable environment,
SUMO_HOME, Python tooling, or smoke-test proof:references/preflight-sumo-environment.md. - Interactive intake for vague, ambitious, or assumption-heavy experiments:
references/interactive-experiment-intake.md. - Confirmed experiment intake and planning:
references/plan-experiment.md. - Code implementation, TDD, and completion evidence:
references/develop-and-verify-code.md. - OSM-to-SUMO construction, imported-network cleanup, road-detail planning, reference-matched construction, routeability, topology/TLS cleanup, HTML review, and Netedit launch:
references/osm-to-sumo-workflow.md. - Region-specific map/TLS reality checks, detector lane repair, field-data sensor alignment, and background visualization:
references/model-osm-detectors.md. - Public OSM source patterns from OSMnx, OSMNet, pyrosm, SUMO osmGet/osmBuild, or osm-to-xodr:
references/osm-source-patterns.md. - Detector-constrained SUMO demand reconstruction from real sensor counts, routeSampler residual correction, detector-route incidence matrices, anti-replay route priors, workflow gates, public-data boundaries, and month-long validation:
references/detector-constrained-demand-reconstruction.md. - SUMO semantics, official/forum lessons, and public-code patterns:
references/learn-sumo-knowledge.md. - NEMA/TLS/TraCI controller identity and API-boundary checks:
references/audit-sumo-controllers.md. - Controller-family application patterns inspired by sumolights, without copying GPL source:
references/sumolights-controller-patterns.md. - Mechanism-isolated corridor perturbation comparisons, localized impact-signal tests, and multi-baseline controller evidence:
references/compare-corridor-perturbations.md. - Outputs, metrics, baselines, ablations, validation ladder, and claim wording:
references/evaluate-and-report-results.md. - User-discovered reusable fixes:
references/capture-field-lesson.md. - Public release, trademark, privacy, and exposure checks:
references/release-project.md.
Output Shape
For most tasks, end with:
scenario:
loaded_references:
missing_assumptions:
evidence:
claim_status:
next_step:
residual_risk:
When editing the skill itself, keep this SKILL.md lean and move detailed rules into references/.