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.

glab-help - Skill - OpenSmartRoute

Name: glab-help
Author: vince-winkintel

Imported from vince-winkintel/gitlab-cli-skills (glab-help/SKILL.md). Install upstream with npx skills add vince-winkintel/gitlab-cli-skills --skill glab-help. Copyright stays with the author.

glab help

Help provenance — capture key 9b430a11f: official macOS arm64 glab v1.130.0; source commit 9b430a11f95ec78d87f19be071d1c381d8803630; binary archive SHA-256 5791b652e774e4eca85afba1ebfd9db8498138c3311e0ed0a39d19590311f232. Adjacent 9b430a11f markers preserve complete binary stdout except trailing spaces/tabs, including Fang headings and original product spelling. Existing legacy product-spelling normalization remains separately scoped; it is not byte-exact.

Renderer and capture fidelity

Fang renders uppercase sections such as USAGE, COMMANDS, FLAGS, ARGUMENTS, and ENVIRONMENT VARIABLES; annotation-provided argument/environment sections are part of complete help. Do not reconstruct Cobra-style output from source or silently omit these sections.

Current keyed binary captures preserve complete stdout with only trailing spaces/tabs removed. Earlier documentation may normalize product spelling to canonical GitLab; those legacy blocks retain that normalization and provenance and are not described as byte-exact captures. Unchanged historical captures are not re-stamped. For managed external commands and package-manager wrappers, inspect the parent renderer with glab help <command> rather than forwarding --help to another program.

Overview


  Help provides help for any command in the application.
  Simply type glab help [path to command] for full details.

  USAGE

    glab help [command] [--flags]

  FLAGS

    -h --help  Show help for this command.

Quick start

glab help --help

Subcommands

This command has no subcommands.

Install glab-help 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": "vince-winkintel-gitlab-cli-skills-glab-help", "kind": "skill", "name": "glab-help", "description": "Display help information for glab commands and subcommands. Use when learning glab commands, viewing command syntax, or getting usage examples. Triggers on help, command help, usage, glab help.", "publisher": "vince-winkintel", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Display help information for glab commands and subcommands. Use when learning glab commands, viewing command syntax, or getting usage examples. Triggers on help, command help, usage, glab help." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/vince-winkintel/gitlab-cli-skills", "path": "glab-help/SKILL.md", "ref": "HEAD", "url": "https://github.com/vince-winkintel/gitlab-cli-skills/blob/HEAD/glab-help/SKILL.md", "key": "vince-winkintel/gitlab-cli-skills/glab-help/SKILL.md" } }, "instructions": "# glab help\n\n> **Help provenance — capture key `9b430a11f`:** official macOS arm64 glab v1.130.0; source commit `9b430a11f95ec78d87f19be071d1c381d8803630`; binary archive SHA-256 `5791b652e774e4eca85afba1ebfd9db8498138c3311e0ed0a39d19590311f232`. Adjacent `9b430a11f` markers preserve complete binary stdout except trailing spaces/tabs, including Fang headings and original product spelling. Existing legacy product-spelling normalization remains separately scoped; it is not byte-exact.\n\n## Renderer and capture fidelity\n\nFang renders uppercase sections such as `USAGE`, `COMMANDS`, `FLAGS`, `ARGUMENTS`, and `ENVIRONMENT VARIABLES`; annotation-provided argument/environment sections are part of complete help. Do not reconstruct Cobra-style output from source or silently omit these sections.\n\nCurrent keyed binary captures preserve complete stdout with only trailing spaces/tabs removed. Earlier documentation may normalize product spelling to canonical GitLab; those legacy blocks retain that normalization and provenance and are not described as byte-exact captures. Unchanged historical captures are not re-stamped. For managed external commands and package-manager wrappers, inspect the parent renderer with `glab help <command>` rather than forwarding `--help` to another program.\n\n## Overview\n\n\n\n```text\n\n Help provides help for any command in the application.\n Simply type glab help [path to command] for full details.\n\n USAGE\n\n glab help [command] [--flags]\n\n FLAGS\n\n -h --help Show help for this command.\n\n```\n\n## Quick start\n\n```bash\nglab help --help\n```\n\n## Subcommands\n\nThis command has no subcommands.", "cost": { "context_tokens": 418 } }

glab-help

About

glab help

Renderer and capture fidelity

Overview

Quick start

Subcommands

Install glab-help 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