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.

dotfiles - Skill - OpenSmartRoute

Name: dotfiles
Author: highb

Imported from highb/dotfiles (AGENTS.md). Install upstream with npx skills add highb/dotfiles. Copyright stays with the author.

Repository instructions for all agents

Read README.md and KNOWN_ISSUES.md before changing provisioning or platform behavior. These instructions apply to this entire repository, including delegated agents.

Purpose and core loop

These dotfiles augment Brandon's shell and OS environment to expand his own capabilities through as much deterministic code as possible. They also provide access to LLMs to help drive further augmentation of that environment.

Turn recurring needs and lessons from LLM-assisted work into reusable local tools: scripts, commands, configuration, and repeatable workflows.
Prefer deterministic code for behavior that can be expressed and verified reliably. Use LLMs to help discover, build, explain, and improve those tools.
Always seek to leave Brandon with tools he can run locally without LLM assistance. Where a capability inherently requires an LLM, make that dependency explicit and keep the surrounding workflow usable and inspectable locally.
Treat comprehensive documentation as part of the deliverable. Explain the purpose, prerequisites, setup, commands, expected results, verification, and troubleshooting in enough detail for Brandon to follow independently.
Keep durable instructions and examples in the repository alongside the tools; a chat response alone is not sufficient documentation for a new workflow.
Close the loop by making each augmentation reproducible through chezmoi and the repository's provisioning model, with an independent local entry point and documentation for using and maintaining it.

Supported platforms

Primary: Ubuntu/Debian Linux, including Pop!_OS, and macOS.
CI: Ubuntu 24.04 and macOS 15; keep changes portable to both.
Partial: Arch Linux and Fedora. Bootstrap recognizes them, but many inventory entries lack providers. Report unresolved packages rather than implying full support.
Unsupported deployment targets: Windows, WSL, Android/Termux, and other OSes. Do not infer platform support from an upstream application's error message. Adding a target requires explicit documentation, provisioning, and validation.
Linux desktops may use Wayland or X11; headless and SSH sessions may have neither. Select clipboard providers at runtime: wl-copy/wl-paste on Wayland, xclip on X11, built-in pbcopy/pbpaste on macOS. Do not force a desktop backend globally.

Implementation and validation

.chezmoiroot points at home/. Edit source files here, not generated targets.
Package definitions belong in home/.chezmoidata/packages.yaml; selection and resolution live in home/.chezmoitemplates/. Use platforms OS restrictions for tools that must not be selected on other targets.
Preserve task selection, exclusions, provider overrides, manualProvisioning, and scoped install consent. Avoid broad package syncs for a narrow repair.
Keep Bash compatible with macOS's bundled Bash 3.2. Do not assume GNU utilities on macOS. Linux desktop helpers must remain gated by platform and task.
Run relevant isolated tests with python3 -B -m unittest discover -s tests -v. Tests must not read workstation credentials or provision real host packages.
Do not commit secrets or bypass the repository's commit protection.

Install dotfiles 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": "highb-dotfiles-dotfiles", "kind": "skill", "name": "dotfiles", "description": "Read README.md and KNOWN_ISSUES.md before changing provisioning or platform behavior. These instructions apply to this entire repository, including delegated agents.", "publisher": "highb", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Read README.md and KNOWN_ISSUES.md before changing provisioning or platform behavior. These instructions apply to this entire repository, including delegated agents." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/highb/dotfiles", "path": "AGENTS.md", "ref": "96e1b6ffa200f5f2e3a56cee7e93147e7d926c48", "url": "https://github.com/highb/dotfiles/blob/96e1b6ffa200f5f2e3a56cee7e93147e7d926c48/AGENTS.md", "key": "highb/dotfiles/AGENTS.md" } }, "instructions": "# Repository instructions for all agents\n\nRead README.md and KNOWN_ISSUES.md before changing provisioning or platform behavior.\nThese instructions apply to this entire repository, including delegated agents.\n\n## Purpose and core loop\n\nThese dotfiles augment Brandon's shell and OS environment to expand his own\ncapabilities through as much deterministic code as possible. They also provide\naccess to LLMs to help drive further augmentation of that environment.\n\n- Turn recurring needs and lessons from LLM-assisted work into reusable local\n tools: scripts, commands, configuration, and repeatable wo", "cost": { "context_tokens": 816 } }

dotfiles

About

Repository instructions for all agents

Purpose and core loop

Supported platforms

Implementation and validation

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