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-cluster - Skill - OpenSmartRoute

Name: glab-cluster
Author: vince-winkintel

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

glab cluster

Capture key 4dd0d32d1: checksum-verified official macOS arm64 binary, source commit 4dd0d32d18361db6c1c668eb4ac691c0d6edf255, archive SHA-256 11980310aaad2bd9c4e75b5635a60e984da5d0e6245187f2cd6e8db0ec4c5a92. Only adjacent marked help fences use this provenance; complete renderer output is preserved except trailing spaces/tabs. Other fences retain their stated prior provenance.

Overview


  Agents connect your cluster to GitLab, enabling pull-based deployments
  and secure access to the Kubernetes API.


  USAGE

    glab cluster <command> [command] [--flags]

  COMMANDS

    agent <command> [command] [--flags]  Manage GitLab Agents for Kubernetes.
    graph [--flags]                      Query the Kubernetes object graph using the GitLab Agent for Kubernetes. (EXPERIMENTAL)

  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.

Quick start

glab cluster --help

Structured output

glab cluster agent list and glab cluster agent token list support --output json / -F json for structured output, which is useful for agent automation.

# List cluster agents with JSON output
glab cluster agent list --output json
glab cluster agent list -F json

# List agent tokens with JSON output
glab cluster agent token list <agent-id> --output json
glab cluster agent token list <agent-id> -F json

glab cluster agent list uses the API-reported total in its text header when available, separately from the current page's row count. JSON remains the requested page of agents. Traverse --page / --per-page explicitly; neither a page's JSON length nor missing total metadata proves there are no further results. This total change applies to the agent list, not the agent-token list.

Subcommands

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

Snap kubeconfig access

The snap uses the manual-connect dot-kube-config plug, scoped to ~/.kube/config and ~/.kube/config.lock, rather than the whole .kube directory. A different kubeconfig path can remain inaccessible under confinement. Connecting the plug or updating kubeconfig changes local permissions/configuration and requires approval; do not treat CLI help as permission to connect it or modify a cluster.

Install glab-cluster 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-cluster", "kind": "skill", "name": "glab-cluster", "description": "Manage GitLab Kubernetes clusters and agent integrations. Use when connecting clusters, managing cluster agents, or working with Kubernetes integration. Triggers on cluster, Kubernetes, k8s, cluster agent, connect cluster.", "publisher": "vince-winkintel", "version": "1.0.0", "capabilities": { "domains": [ "coding", "data_analysis" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Manage GitLab Kubernetes clusters and agent integrations. Use when connecting clusters, managing cluster agents, or working with Kubernetes integration. Triggers on cluster, Kubernetes, k8s, cluster agent, connect cluster." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/vince-winkintel/gitlab-cli-skills", "path": "glab-cluster/SKILL.md", "ref": "HEAD", "url": "https://github.com/vince-winkintel/gitlab-cli-skills/blob/HEAD/glab-cluster/SKILL.md", "key": "vince-winkintel/gitlab-cli-skills/glab-cluster/SKILL.md" } }, "instructions": "# glab cluster\n\n> Capture key `4dd0d32d1`: checksum-verified official macOS arm64 binary, source commit `4dd0d32d18361db6c1c668eb4ac691c0d6edf255`, archive SHA-256 `11980310aaad2bd9c4e75b5635a60e984da5d0e6245187f2cd6e8db0ec4c5a92`. Only adjacent marked help fences use this provenance; complete renderer output is preserved except trailing spaces/tabs. Other fences retain their stated prior provenance.\n\n## Overview\n\n\n\n```text\n\n Agents connect your cluster to GitLab, enabling pull-based deployments\n and secure access to the Kubernetes API.\n\n\n USAGE\n\n glab cluster <command> [command] [--flags]\n\n COMMANDS\n\n agent <command> [command] [--flags] Manage GitLab Agents for Kubernetes.\n graph [--flags] Query the Kubernetes object graph using the GitLab Agent for Kubernetes. (EXPERIMENTAL)\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## Quick start\n\n```bash\nglab cluster --help\n```\n\n## Structured output\n\n`glab cluster agent list` and `glab cluster agent token list` support `--output json` / `-F json` for structured output, which is useful for agent automation.\n\n```bash\n# List cluster agents with JSON output\nglab cluster agent list --output json\nglab cluster agent list -F json\n\n# List agent tokens with JSON output\nglab cluster agent token list <agent-id> --output json\nglab cluster agent token list <agent-id> -F json\n```\n\n`glab cluster agent list` uses the API-reported total in its text header when available, separately from the current page's row count. JSON remains the requested page of agents. Traverse `--page` / `--per-page` explicitly; neither a page's JSON length nor missing total metadata proves there are no further results. This total change applies to the agent list, not the agent-token list.\n\n## Subcommands\n\nSee [references/commands.md](references/commands.md) for full `--help` output.\n\n## Snap kubeconfig access\n\nThe snap uses the manual-connect `dot-kube-config` plug, scoped to `~/.kube/config` and `~/.kube/config.lock`, rather than the whole `.kube` directory. A different kubeconfig path can remain inaccessible under confinement. Connecting the plug or updating kubeconfig changes local permissions/configuration and requires approval; do not treat CLI help as permission to connect it or modify a cluster.", "cost": { "context_tokens": 630 } }

glab-cluster

About

glab cluster

Overview

Quick start

Structured output

Subcommands

Snap kubeconfig access

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