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-ssh-key - Skill - OpenSmartRoute

Name: glab-ssh-key
Author: vince-winkintel

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

glab ssh-key

Help provenance. Each adjacent marker selects its matching source commit and archive SHA-256 below (checksum-verified official macOS arm64 binary). Preserve complete help bytes except trailing spaces/tabs, including casing, spelling, blank lines, indentation, examples, wrapping, and truncation. Historical keys do not override current markers.

2e352a17e: 2e352a17e7e00bef420b0f38e0ce9ab4e1a38e5d; 017b14c9bb8d54ba1ea2007607f86dbde0352ad8dea566e2647e9c1bae86bcac.

Overview


  Add, list, get, and delete the SSH keys associated with your account.

  GitLab uses SSH keys to authenticate Git operations over SSH, and,
  depending on each key's usage type, to verify signed commits.


  USAGE

    glab ssh-key <command> [command] [--flags]

  COMMANDS

    add [key-file] [--flags]     Add an SSH key to your GitLab account.
    delete [<key-id>] [--flags]  Deletes a single SSH key specified by the ID.
    get [<key-id>] [--flags]     Returns a single SSH key specified by the ID.
    list [--flags]               Get a list of SSH keys for the currently authenticated user.

  FLAGS

    -h --help                    Show help for this command.
    -R --repo                    Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.

⚠️ Security Warning: Public Keys Only

Always verify you are uploading a PUBLIC key, not a private key.

✅ Public keys: ~/.ssh/id_rsa.pub, ~/.ssh/id_ed25519.pub (.pub extension)
❌ Private keys: ~/.ssh/id_rsa, ~/.ssh/id_ed25519 (no extension — NEVER upload these)

Uploading a private key to GitLab would expose your credentials. Double-check the filename before running glab ssh-key add.

# ✅ Safe — public key
glab ssh-key add ~/.ssh/id_ed25519.pub --title "My Laptop"

# ❌ NEVER do this — private key
# glab ssh-key add ~/.ssh/id_ed25519 --title "My Laptop"

Before uploading, verify your key is public:

# Should start with 'ssh-rsa', 'ssh-ed25519', 'ecdsa-sha2-*', etc.
head -c 20 ~/.ssh/id_ed25519.pub

Quick start

glab ssh-key --help

Replace an existing key

GitLab rejects duplicate public-key fingerprints even when the registered key has expired. After confirming the authenticated account and the key to replace, use:

glab ssh-key add ~/.ssh/id_ed25519.pub --title "My Laptop" --expires-at 2027-01-01 --replace

--expires-at accepts both a date-only value such as 2027-01-01 (midnight UTC) and a full RFC 3339 timestamp such as 2027-01-01T00:00:00Z. The flag help shows the full timestamp form; the date-only example above is also accepted by the CLI parser.

--replace parses the public key, searches the current user's keys across pages for the same SHA256 fingerprint, deletes the match, and adds the supplied key with the requested title, usage type, and expiration. With no match it adds the key normally. There is no replacement confirmation prompt or rollback: if adding fails after deletion, the old key is already gone. Review the matching key before using this flag and keep another authorized access method available. This re-registers the same public key; it does not generate or rotate key material.

Shell completion

ssh-key get and delete complete the first argument with current-account key IDs and titles through an authenticated API lookup. Completion is therefore not offline discovery or authorization to delete a key. add completes file paths without restricting them to .pub; verify that the selected file is a public key before uploading. --usage-type completes auth, signing, and auth_and_signing. Help inspection does not exercise those completions.

Structured output

glab ssh-key list and glab ssh-key get support --output json / -F json for structured output, which is useful for agent automation.

# List SSH keys with JSON output
glab ssh-key list --output json
glab ssh-key list -F json

# Get a specific SSH key with JSON output
glab ssh-key get <key-id> --output json
glab ssh-key get <key-id> -F json

Subcommands

See references/commands.md for full --help output.

Install glab-ssh-key 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-ssh-key", "kind": "skill", "name": "glab-ssh-key", "description": "Manage SSH keys for GitLab account including add, list, and delete operations. Use when setting up SSH authentication, managing SSH keys, or configuring Git over SSH. Triggers on SSH key, add SSH key, SSH authentication, Git SSH.", "publisher": "vince-winkintel", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Manage SSH keys for GitLab account including add, list, and delete operations. Use when setting up SSH authentication, managing SSH keys, or configuring Git over SSH. Triggers on SSH key, add SSH key, SSH authentication, Git SSH." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/vince-winkintel/gitlab-cli-skills", "path": "glab-ssh-key/SKILL.md", "ref": "HEAD", "url": "https://github.com/vince-winkintel/gitlab-cli-skills/blob/HEAD/glab-ssh-key/SKILL.md", "key": "vince-winkintel/gitlab-cli-skills/glab-ssh-key/SKILL.md" } }, "instructions": "# glab ssh-key\n\n> **Help provenance.** Each adjacent marker selects its matching source commit and archive SHA-256 below (checksum-verified official macOS arm64 binary). Preserve complete help bytes except trailing spaces/tabs, including casing, spelling, blank lines, indentation, examples, wrapping, and truncation. Historical keys do not override current markers.\n> - `2e352a17e`: `2e352a17e7e00bef420b0f38e0ce9ab4e1a38e5d`; `017b14c9bb8d54ba1ea2007607f86dbde0352ad8dea566e2647e9c1bae86bcac`.\n\n## Overview\n\n\n\n```text\n\n Add, list, get, and delete the SSH keys associated with your account.\n\n GitLab uses SSH keys to authenticate Git operations over SSH, and,\n depending on each key's usage type, to verify signed commits.\n\n\n USAGE\n\n glab ssh-key <command> [command] [--flags]\n\n COMMANDS\n\n add [key-file] [--flags] Add an SSH key to your GitLab account.\n delete [<key-id>] [--flags] Deletes a single SSH key specified by the ID.\n get [<key-id>] [--flags] Returns a single SSH key specified by the ID.\n list [--flags] Get a list of SSH keys for the currently authenticated user.\n\n FLAGS\n\n -h --help Show help for this command.\n -R --repo Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.\n\n```\n\n## ⚠️ Security Warning: Public Keys Only\n\n**Always verify you are uploading a PUBLIC key, not a private key.**\n\n- ✅ Public keys: `~/.ssh/id_rsa.pub`, `~/.ssh/id_ed25519.pub` (`.pub` extension)\n- ❌ Private keys: `~/.ssh/id_rsa`, `~/.ssh/id_ed25519` (no extension — NEVER upload these)\n\nUploading a private key to GitLab would expose your credentials. Double-check the filename before running `glab ssh-key add`.\n\n```bash\n# ✅ Safe — public key\nglab ssh-key add ~/.ssh/id_ed25519.pub --title \"My Laptop\"\n\n# ❌ NEVER do this — private key\n# glab ssh-key add ~/.ssh/id_ed25519 --title \"My Laptop\"\n```\n\n**Before uploading, verify your key is public:**\n```bash\n# Should start with 'ssh-rsa', 'ssh-ed25519', 'ecdsa-sha2-*', etc.\nhead -c 20 ~/.ssh/id_ed25519.pub\n```\n\n## Quick start\n\n```bash\nglab ssh-key --help\n```\n\n## Replace an existing key\n\nGitLab rejects duplicate public-key fingerprints even when the registered key has expired. After confirming the authenticated account and the key to replace, use:\n\n```bash\nglab ssh-key add ~/.ssh/id_ed25519.pub --title \"My Laptop\" --expires-at 2027-01-01 --replace\n```\n\n`--expires-at` accepts both a date-only value such as `2027-01-01` (midnight UTC) and a full RFC 3339 timestamp such as `2027-01-01T00:00:00Z`. The flag help shows the full timestamp form; the date-only example above is also accepted by the CLI parser.\n\n`--replace` parses the public key, searches the current user's keys across pages for the same SHA256 fingerprint, deletes the match, and adds the supplied key with the requested title, usage type, and expiration. With no match it adds the key normally. There is no replacement confirmation prompt or rollback: if adding fails after deletion, the old key is already gone. Review the matching key before using this flag and keep another authorized access method available. This re-registers the same public key; it does not generate or rotate key material.\n\n## Shell completion\n\n`ssh-key get` and `delete` complete the first argument with current-account key IDs and titles through an authenticated API lookup. Completion is therefore not offline discovery or authorization to delete a key. `add` completes file paths without restricting them to `.pub`; verify that the selected file is a public key before uploading. `--usage-type` completes `auth`, `signing`, and `auth_and_signing`. Help inspection does not exercise those completions.\n\n## Structured output\n\n`glab ssh-key list` and `glab ssh-key get` support `--output json` / `-F json` for structured output, which is useful for agent automation.\n\n```bash\n# List SSH keys with JSON output\nglab ssh-key list --output json\nglab ssh-key list -F json\n\n# Get a specific SSH key with JSON output\nglab ssh-key get <key-id> --output json\nglab ssh-key get <key-id> -F json\n```\n\n## Subcommands\n\nSee [references/commands.md](references/commands.md) for full `--help` output.", "cost": { "context_tokens": 1069 } }

glab-ssh-key

About

glab ssh-key

Overview

⚠️ Security Warning: Public Keys Only

Quick start

Replace an existing key

Shell completion

Structured output

Subcommands

Install glab-ssh-key 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