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.

s104-water-level - Skill - OpenSmartRoute

Name: s104-water-level
Author: philliphoff

Instruction file imported from philliphoff/EncDotNet.S100 (.github/instructions/s104-water-level.instructions.md). Copyright stays with the author.

S-104 editing rules

When modifying S-104 code:

Load the s104-water-level skill before proposing non-trivial changes.
Preserve HDF5 group/attribute names exactly as specified in the S-104 Edition 2.0.0 product spec (case-sensitive).
Do not assume dataCodingFormat is regular grid (2) — support (or explicitly reject) the other formats declared on the root group.
waterLevelTrend is a spec-defined enumeration (0 nodata, 1 decreasing, 2 increasing, 3 steady). Never recompute it client-side; preserve producer-supplied values.
Times derive from dateTimeOfFirstRecord + timeRecordInterval * index unless an explicit time dataset exists.
Cite the S-104 section number in XML doc comments when adding spec-derived constants, attribute names, or group paths.
Any new public API requires a matching xunit test (skip with Assert.SkipUnless when a real HDF5 file is required).
Portrayal is SoundCharts' own by design. IHO publishes no official S-104 portrayal catalogue (the spec treats water levels as input to ECDIS depth adjustment, not a visual layer). S104CoverageStyle defines station gauges (trend mark + signed value) and dashed surface isolines in one ink colour per Day / Dusk / Night palette; the S-104 README's Portrayal section is the reference. Do not invent a synthetic IHO-shaped PC under content/S104/pc/; that directory stays .gitkeep-only until IHO publishes one. Don't add colour fills, or red, green or depth blues: they compete with the ENC. Update S104CoverageStyleTests and the S104RenderingTests baselines with any change. The style is built with the EncDotNet.S100.Portrayals.Application toolkit: colours in S104CoverageStyle.Palette (ApplicationPalette), symbols as SVG files in src/EncDotNet.S100.Datasets.S104/Symbols/ (SymbolSet), instructions from StationSymbols / StationLabels (InstructionBuilder). Don't add palette dictionaries or inline SVG strings back. Bump S104CoverageStyle.StyleVersion when a symbol or colour changes, so the tile disk cache drops tiles drawn with the old style.

Install s104-water-level 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": "philliphoff-encdotnet-s100-s104-water-level-instructions", "kind": "skill", "name": "s104-water-level", "description": "When modifying S-104 code:", "publisher": "philliphoff", "version": "1.0.0", "capabilities": { "domains": [ "coding", "data_analysis" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "When modifying S-104 code:" ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/philliphoff/EncDotNet.S100", "path": ".github/instructions/s104-water-level.instructions.md", "ref": "b353f69028bfbe3a321b2db7c36a2a5f2d38874d", "url": "https://github.com/philliphoff/EncDotNet.S100/blob/b353f69028bfbe3a321b2db7c36a2a5f2d38874d/.github/instructions/s104-water-level.instructions.md", "key": "philliphoff/EncDotNet.S100/.github/instructions/s104-water-level.instructions.md" }, "applies_to": "src/EncDotNet.S100.Datasets.S104/**,tests/EncDotNet.S100.Datasets.S104.Tests/**" }, "instructions": "# S-104 editing rules\n\nWhen modifying S-104 code:\n\n- Load the `s104-water-level` skill before proposing non-trivial changes.\n- Preserve HDF5 group/attribute names exactly as specified in the\n S-104 Edition 2.0.0 product spec (case-sensitive).\n- Do not assume `dataCodingFormat` is regular grid (2) — support (or\n explicitly reject) the other formats declared on the root group.\n- `waterLevelTrend` is a spec-defined enumeration (0 nodata, 1\n decreasing, 2 increasing, 3 steady). Never recompute it client-side;\n preserve producer-supplied values.\n- Times derive from `dateTimeOfFirstRecord` + `ti", "cost": { "context_tokens": 532 } }

s104-water-level

About

S-104 editing rules

Install s104-water-level 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