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.

config - Skill - OpenSmartRoute

Name: config
Author: robotics-team-1213

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

config

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

Purpose

Pinky Pro board overlays mounted into rosy-core. ROSY_RUNTIME_MODE selects core, motor, or hardware. board.yaml catalogs slices (required: [core]) and presets that map onto those modes. The full in-tree middleware/devices/pinky/profile/config/capabilities.yaml (D-196) is the Pinky source profile; these files are what the robot actually advertises.

Key Files

File	Description
`profile.core.yaml` / `capabilities.core.yaml`	Dashboard only: no teleop, no lidar
`profile.motor.yaml` / `capabilities.motor.yaml`	Dynamixel teleop, encoder only
`profile.hardware.yaml` / `capabilities.hardware.yaml`	Motor + RPLidar + localized Nav2 goal/return-home; slam false
`capabilities.hardware-mapping.yaml`	Hardware SLAM overlay selected only by `ROSY_NAVIGATION_BACKEND=slam`; slam true, navigation false
`motion_profiles.yaml`	Measured base/arm/payload states; defaults to unmeasured `unknown`
`board.yaml`	Modes, aliases (`pi5-lite` → `hardware`), `slices` (`required: [core]`; available motor/io/nav/vision/omx/ai), and `presets` (`core` / `motor` / `hardware`)
`resolve-mode.sh`	Maps aliases and `--slices` sets onto catalog modes; overlay YAML exists only for catalog modes
`rosy.pi5.example.yaml`	Example `ROSY_CONFIG` for the device; hardware readiness gate is required

Subdirectories

None.

For AI Agents

Working In This Directory

Compose bind-mounts profile/capabilities over /etc/rosy/. Keep keys aligned with contracts/foundation/config/ schemas.
Overlay YAML exists only for core / motor / hardware. Do not copy YAML for aliases.
Presets: core → [core]; motor → [core, motor]; hardware → [core, motor, io, nav]. vision/omx/ai are catalog-only (enabled: false); do not add overlay YAML or compose services for them.
Do not enable slam/swarm unless the hardware image actually launches those stacks. D-144 permits slam only through the dedicated hardware-mapping overlay; the normal hardware overlay remains localization-only.

Testing Requirements

Covered by test/test_robot_runtime.py and middleware/core/gateway/test/test_runtime_config.py.

Common Patterns

YAML only; no code.

Dependencies

Internal

contracts/foundation/config/rosy_default.yaml structure
deploy/robot/pinky_pro/compose.yaml volume mounts

External

None.

Install config 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-config", "kind": "skill", "name": "config", "description": "Pinky Pro board overlays mounted into `rosy-core`. `ROSY_RUNTIME_MODE` selects `core`, `motor`, or `hardware`. `board.yaml` catalogs slices (`required: [core]`) and presets that map onto those modes. The full in-tree `middleware/devices/pinky/profile/config/capabilities.yaml` (D-196) is the Pinky source profile; these files are what the robot actually advertises.", "publisher": "robotics-team-1213", "version": "1.0.0", "capabilities": { "domains": [ "data_analysis", "math" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Pinky Pro board overlays mounted into `rosy-core`. `ROSY_RUNTIME_MODE` selects `core`, `motor`, or `hardware`. `board.yaml` catalogs slices (`required: [core]`) and presets that map onto those modes. The full in-tree `middleware/devices/pinky/profile/config/capabilities.yaml` (D-196) is the Pinky source profile; these files are what the robot actually advertises." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/robotics-team-1213/rosy-platform", "path": "deploy/robot/pinky_pro/config/AGENTS.md", "ref": "c47d7c3e78c9751a9428450579bb186af0520725", "url": "https://github.com/robotics-team-1213/rosy-platform/blob/c47d7c3e78c9751a9428450579bb186af0520725/deploy/robot/pinky_pro/config/AGENTS.md", "key": "robotics-team-1213/rosy-platform/deploy/robot/pinky_pro/config/AGENTS.md" } }, "instructions": "\n\n\n# config\n\n**Parent context:** `../AGENTS.md`\n**Updated:** 2026-10-07\n\n## Purpose\n\nPinky Pro board overlays mounted into `rosy-core`. `ROSY_RUNTIME_MODE` selects `core`, `motor`, or `hardware`. `board.yaml` catalogs slices (`required: [core]`) and presets that map onto those modes. The full in-tree `middleware/devices/pinky/profile/config/capabilities.yaml` (D-196) is the Pinky source profile; these files are what the robot actually advertises.\n\n## Key Files\n\n| File | Description |\n|------|-------------|\n| `prof", "cost": { "context_tokens": 646 } }

config

About

config

Purpose

Key Files

Subdirectories

For AI Agents

Working In This Directory

Testing Requirements

Common Patterns

Dependencies

Internal

External

Install config 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

Use it

Manifest

Reviews