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.

subtitle-merger - Skill - OpenSmartRoute

Name: subtitle-merger
Author: moritzbrantner

Imported from moritzbrantner/subtitle-merger (AGENTS.md). Install upstream with npx skills add moritzbrantner/subtitle-merger. Copyright stays with the author.

Agent instructions

Applicable convention stack

Apply the shared conventions from moritzbrantner/coding-agent-conventions without copying them here:

principles/
conventions/agents/
conventions/dependencies/
conventions/environment/
conventions/interface-design/
conventions/repository/
conventions/testing/
technologies/rust/
technologies/typescript/
technologies/typescript/react/
technologies/typescript/react/moritzbrantner-ui/
technologies/tooling/ plus vite/, vitest/, and playwright/

Repository-local rules below override only where they conflict.

Repository-specific rules

Treat Subtitle Merger as the vertical consumer: upstream Native WhisperX or audio-stack work must be driven by a concrete editor or subtitle workflow.
Read docs/adr/0003-released-native-whisperx-boundary.md before changing transcription, translation, or their source dependency boundary.
Host-native development is canonical because the product uses native file picking, local media/model caches, and optional local GPU resources. Containers are optional verification tools, not the source of truth for the development environment.
Keep the development loop usable directly from the repository.

Authority boundaries

Machine-readable in .repository.toml ([architecture]); keep both lists identical. bun run check:boundaries rejects direct ASR/alignment/translation/model-runtime dependencies in the editor manifests.

Owns: subtitle-merger/subtitle-editing, subtitle-merger/timeline-workflow, subtitle-merger/generation-ux, subtitle-merger/subtitle-export, subtitle-merger/local-app-bootstrap
Adapts: native-whisperx/transcription, native-whisperx/alignment, native-whisperx/translation, audio-analysis/browser-transcription, timeline-editor/timeline-ui, editor-core/editor-model
Non-authoritative: native-whisperx/transcription, native-whisperx/alignment, native-whisperx/translation, audio-analysis/browser-transcription, media/model-runtime

Repository context

Domain vocabulary: CONTEXT.md
Architectural decisions: docs/adr/
Domain context: docs/agents/domain.md

Install subtitle-merger 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": "moritzbrantner-subtitle-merger-subtitle-merger", "kind": "skill", "name": "subtitle-merger", "description": "Apply the shared conventions from `moritzbrantner/coding-agent-conventions` without copying them here:", "publisher": "moritzbrantner", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Apply the shared conventions from `moritzbrantner/coding-agent-conventions` without copying them here:" ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/moritzbrantner/subtitle-merger", "path": "AGENTS.md", "ref": "e6a3b8569287873b6341116c09fd86506f921d89", "url": "https://github.com/moritzbrantner/subtitle-merger/blob/e6a3b8569287873b6341116c09fd86506f921d89/AGENTS.md", "key": "moritzbrantner/subtitle-merger/AGENTS.md" } }, "instructions": "# Agent instructions\n\n## Applicable convention stack\n\nApply the shared conventions from `moritzbrantner/coding-agent-conventions` without copying them here:\n\n- `principles/`\n- `conventions/agents/`\n- `conventions/dependencies/`\n- `conventions/environment/`\n- `conventions/interface-design/`\n- `conventions/repository/`\n- `conventions/testing/`\n- `technologies/rust/`\n- `technologies/typescript/`\n- `technologies/typescript/react/`\n- `technologies/typescript/react/moritzbrantner-ui/`\n- `technologies/tooling/` plus `vite/`, `vitest/`, and `playwright/`\n\nRepository-local rules below override only whe", "cost": { "context_tokens": 547 } }

subtitle-merger

About

Agent instructions

Applicable convention stack

Repository-specific rules

Authority boundaries

Repository context

Install subtitle-merger 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