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.

weather-forecast - Skill - OpenSmartRoute

Name: weather-forecast
Author: lovellfelix

Imported from lovellfelix/skills (portable/weather-forecast/SKILL.md). Install upstream with npx skills add lovellfelix/skills --skill weather-forecast. Copyright stays with the author.

Weather Forecast Skill

What This Skill Covers

Current conditions and today's summary
Short multi-day forecasts
ZIP-first weather lookup without API keys
Lat/lon fallback when coordinates are already known

Preferred Helper Paths

Use the shared helper when possible:

bash scripts/weather.sh

If a runtime restricts execution to OpenCode-managed paths, use the wrapper instead:

bash ~/.config/opencode/scripts/weather.sh

Personal Machine Activation

This skill is personal-machine only.

Linked automatically when ~/.overlay/local/.enabled is absent (no allowlist to maintain).

Default No-Key Workflow

Prefer a stored ZIP/postal preference when available.
Otherwise accept an explicit --zip or --lat/--lon input.
Call the helper.
Return concise weather results, not raw API dumps unless JSON was requested.

Supported commands:

bash scripts/weather.sh today --zip 75077 --json
bash scripts/weather.sh forecast --zip 75077 --days 5 --json
bash scripts/weather.sh today --lat 32.9919 --lon -97.0700 --json

Session Memory

If the user often asks for local weather, reuse a saved ZIP value.

session_memory action=track_user_preference category=workflow key=zip_code value=75077 confidence=1.0

Provider Rules

Use case	Default provider	API key required
ZIP geocoding	OSM Nominatim	No
Weather forecast	Open-Meteo	No
Paid weather provider	Optional future path	Yes

Default behavior stays keyless.

Practical Workflows

Today's weather from ZIP

bash scripts/weather.sh today --zip 75077 --json

Five-day forecast from ZIP

bash scripts/weather.sh forecast --zip 75077 --days 5 --json

Forecast from known coordinates

bash scripts/weather.sh forecast --lat 32.9919 --lon -97.0700 --days 3 --json

Troubleshooting

Invalid ZIP code: use a 5-digit US ZIP.
Location not specified: pass --zip or --lat/--lon.
Weather API request failed: retry once and keep the request volume low.
If a runtime blocks the shared helper path, retry with the OpenCode wrapper path.

Validation

bash scripts/weather.sh today --zip 75077 --json
bash scripts/weather.sh forecast --zip 75077 --days 3 --json
bash ~/.config/opencode/scripts/weather.sh today --zip 75077 --json

Install weather-forecast 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": "lovellfelix-skills-weather-forecast", "kind": "skill", "name": "weather-forecast", "description": "Use when the user asks for current weather, today's conditions, or a short forecast without relying on paid weather APIs.", "publisher": "lovellfelix", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "weather", "forecast", "portable", "personal-assistant", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Use when the user asks for current weather, today's conditions, or a short forecast without relying on paid weather APIs." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/lovellfelix/skills", "path": "portable/weather-forecast/SKILL.md", "ref": "a107c5b09ace88d684eb56d79a5ee8359a87e235", "url": "https://github.com/lovellfelix/skills/blob/a107c5b09ace88d684eb56d79a5ee8359a87e235/portable/weather-forecast/SKILL.md", "key": "lovellfelix/skills/portable/weather-forecast/SKILL.md" } }, "instructions": "# Weather Forecast Skill\n\n## What This Skill Covers\n\n- Current conditions and today's summary\n- Short multi-day forecasts\n- ZIP-first weather lookup without API keys\n- Lat/lon fallback when coordinates are already known\n\n## Preferred Helper Paths\n\nUse the shared helper when possible:\n\n```bash\nbash scripts/weather.sh\n```\n\nIf a runtime restricts execution to OpenCode-managed paths, use the wrapper instead:\n\n```bash\nbash ~/.config/opencode/scripts/weather.sh\n```\n\n## Personal Machine Activation\n\nThis skill is personal-machine only.\n\n- Linked automatically when `~/.overlay/local/.enabled` is absent", "cost": { "context_tokens": 596 } }

weather-forecast

About

Weather Forecast Skill

What This Skill Covers

Preferred Helper Paths

Personal Machine Activation

Default No-Key Workflow

Session Memory

Provider Rules

Practical Workflows

Today's weather from ZIP

Five-day forecast from ZIP

Forecast from known coordinates

Troubleshooting

Validation

Install weather-forecast 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