How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

drivers - Skill - OpenSmartRoute

Name: drivers
Author: robotics-team-1213

Imported from robotics-team-1213/rosy-platform (middleware/drivers/AGENTS.md). Install upstream with npx skills add robotics-team-1213/rosy-platform --skill drivers. Copyright stays with the author.

drivers

Parent context: ../AGENTS.md Generated: 2026-10-07 · Updated: 2026-10-07

Purpose

Pinky board drivers that publish sensor or actuator topics. They do not own the robot mode or the final command.

Subdirectories

Directory	Purpose
`imu_bno055/`	BNO055 IMU (see `imu_bno055/AGENTS.md`)
`pinky_adc/`	ADC, battery, IR, ultrasonic (see `pinky_adc/AGENTS.md`)
`pinky_lamp/`	WS2812 lamp (see `pinky_lamp/AGENTS.md`)
`pinky_led/`	Status LED (see `pinky_led/AGENTS.md`)

For AI Agents

Working In This Directory

A driver that reads 4095 or times out is a bringup problem. Use the rosy-hw-bringup skill on a robot rather than changing a threshold to hide it.
Do not subscribe here and publish /cmd_vel.

Testing Requirements

Each package's test/ AGENTS.md names the suite. IMU and LED have host tests. ADC and lamp are closer to the hardware.

Common Patterns

ament_cmake or ament_python as the package already uses. Node names stay in the package, not in CORE.

Dependencies

Internal

Started by middleware/devices/pinky/bringup/.
CORE reads their topics through core.bridge.

External

I2C, ws2811, and the Pinky ADC path named in each package.

Manual Notes

Install drivers and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "robotics-team-1213-rosy-platform-drivers", "kind": "skill", "name": "drivers", "description": "Pinky board drivers that publish sensor or actuator topics. They do not own the robot mode or the final command.", "publisher": "robotics-team-1213", "version": "1.0.0", "capabilities": { "domains": [ "coding", "math" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Pinky board drivers that publish sensor or actuator topics. They do not own the robot mode or the final command." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/robotics-team-1213/rosy-platform", "path": "middleware/drivers/AGENTS.md", "ref": "c47d7c3e78c9751a9428450579bb186af0520725", "url": "https://github.com/robotics-team-1213/rosy-platform/blob/c47d7c3e78c9751a9428450579bb186af0520725/middleware/drivers/AGENTS.md", "key": "robotics-team-1213/rosy-platform/middleware/drivers/AGENTS.md" } }, "instructions": "# drivers\n\n**Parent context:** `../AGENTS.md`\n**Generated:** 2026-10-07 · **Updated:** 2026-10-07\n\n## Purpose\n\nPinky board drivers that publish sensor or actuator topics. They do not own the robot mode or the final command.\n\n## Subdirectories\n\n| Directory | Purpose |\n|-----------|---------|\n| `imu_bno055/` | BNO055 IMU (see `imu_bno055/AGENTS.md`) |\n| `pinky_adc/` | ADC, battery, IR, ultrasonic (see `pinky_adc/AGENTS.md`) |\n| `pinky_lamp/` | WS2812 lamp (see `pinky_lamp/AGENTS.md`) |\n| `pinky_led/` | Status LED (see `pinky_led/AGENTS.md`) |\n\n## For AI Agents\n\n### Working In This Directory\n\n- A", "cost": { "context_tokens": 322 } }

drivers

About

drivers

Purpose

Subdirectories

For AI Agents

Working In This Directory

Testing Requirements

Common Patterns

Dependencies

Internal

External

Manual Notes

Use it

Install drivers and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews