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.

rosy_dock - Skill - OpenSmartRoute

Name: rosy_dock
Author: robotics-team-1213

Imported from robotics-team-1213/rosy-platform (operations/site_devices/dock/firmware/rosy_dock/AGENTS.md). Install upstream with npx skills add robotics-team-1213/rosy-platform --skill rosy_dock. Copyright stays with the author.

rosy_dock

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

Purpose

Single-file ESP32 sketch: load probe, contact enable, current/voltage sense, fault foldback, Wi-Fi STA from NVS, GET /status.

Key Files

File	Description
`rosy_dock.ino`	All firmware: pins 25/34/35/32, thresholds, `setOutput`, HTTP `/status`

Subdirectories

None.

For AI Agents

Working In This Directory

Pins: PIN_OUTPUT_ENABLE=25, PIN_CURRENT_SENSE=34, PIN_VOLTAGE_SENSE=35, PIN_LIMIT_SWITCH=32 (digital, pressed=LOW).
Thresholds: charging current 0.05 A, over-current 3.0 A, over-voltage 8.7 V (2S full is 8.4 V). NTC deferred — GPIO33/36 footprint only.
setOutput is the only place contacts switch. Faults always call setOutput(false).
Do not compile Wi-Fi SSID/password into the sketch; use Preferences/NVS.
Endpoint is port 80, one route, no commands.

Testing Requirements

python3 -m pytest test/test_dock_contract.py -v

Common Patterns

Debounced load (300 ms), 50 ms sample interval.

Dependencies

Internal

Contract operations/site_devices/dock/README.md (ROSY-DOCK-001, D-28)

External

Arduino.h, WiFi.h, WebServer.h, Preferences.h

Install rosy_dock 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-rosy-dock", "kind": "skill", "name": "rosy_dock", "description": "Single-file ESP32 sketch: load probe, contact enable, current/voltage sense, fault foldback, Wi-Fi STA from NVS, `GET /status`.", "publisher": "robotics-team-1213", "version": "1.0.0", "capabilities": { "domains": [ "coding", "legal" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Single-file ESP32 sketch: load probe, contact enable, current/voltage sense, fault foldback, Wi-Fi STA from NVS, `GET /status`." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/robotics-team-1213/rosy-platform", "path": "operations/site_devices/dock/firmware/rosy_dock/AGENTS.md", "ref": "c47d7c3e78c9751a9428450579bb186af0520725", "url": "https://github.com/robotics-team-1213/rosy-platform/blob/c47d7c3e78c9751a9428450579bb186af0520725/operations/site_devices/dock/firmware/rosy_dock/AGENTS.md", "key": "robotics-team-1213/rosy-platform/operations/site_devices/dock/firmware/rosy_dock/AGENTS.md" } }, "instructions": "\n\n\n# rosy_dock\n\n**Parent context:** `../AGENTS.md`\n**Updated:** 2026-10-07\n\n## Purpose\n\nSingle-file ESP32 sketch: load probe, contact enable, current/voltage sense, fault foldback, Wi-Fi STA from NVS, `GET /status`.\n\n## Key Files\n\n| File | Description |\n|------|-------------|\n| `rosy_dock.ino` | All firmware: pins 25/34/35/32, thresholds, `setOutput`, HTTP `/status` |\n\n## Subdirectories\n\nNone.\n\n## For AI Agents\n\n### Working In This Directory\n\n- **Pins:** `PIN_OUTPUT_ENABLE=25`, `PIN_CURRENT_SENSE=34`, `PIN_VOLTAGE", "cost": { "context_tokens": 336 } }

rosy_dock

About

rosy_dock

Purpose

Key Files

Subdirectories

For AI Agents

Working In This Directory

Testing Requirements

Common Patterns

Dependencies

Internal

External

Use it

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