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

Name: glab-schedule
Author: vince-winkintel

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

glab schedule

Overview


  Work with GitLab CI/CD schedules.
  USAGE
    glab schedule <command> [command] [--flags]
  COMMANDS
    create [--flags]       Schedule a new pipeline.
    delete <id> [--flags]  Delete the schedule with the specified ID.
    list [--flags]         Get the list of schedules.
    run <id>               Run the specified scheduled pipeline.
    update <id> [--flags]  Update a pipeline schedule.
  FLAGS
    -h --help              Show help for this command.
    -R --repo              Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.

Quick start

glab schedule --help

Structured output

glab schedule list supports --output json / -F json for structured output, which is useful for agent automation.

The human list header uses the API-reported total across pages rather than treating the current page length as the total. JSON still contains only the fetched page of schedules; use --page and --per-page to inspect subsequent pages. Do not mistake the header's total for a fully fetched inventory, and do not create, update, run, or delete schedules as part of a read-only audit.

# List schedules with JSON output
glab schedule list --output json
glab schedule list -F json

Schedule variables

Schedule variable keys are validated before schedule creation. Empty keys are rejected, so check generated --variable <key>:<value> input before creating schedules.

Subcommands

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

Install glab-schedule 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-schedule", "kind": "skill", "name": "glab-schedule", "description": "Manage CI/CD pipeline schedules including create, list, update, delete, and run scheduled pipelines. Use when automating pipelines, setting up cron jobs, or managing scheduled builds. Triggers on schedule, scheduled pipeline, cron, pipeline schedule, automated build.", "publisher": "vince-winkintel", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Manage CI/CD pipeline schedules including create, list, update, delete, and run scheduled pipelines. Use when automating pipelines, setting up cron jobs, or managing scheduled builds. Triggers on schedule, scheduled pipeline, cron, pipeline schedule, automated build." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/vince-winkintel/gitlab-cli-skills", "path": "glab-schedule/SKILL.md", "ref": "HEAD", "url": "https://github.com/vince-winkintel/gitlab-cli-skills/blob/HEAD/glab-schedule/SKILL.md", "key": "vince-winkintel/gitlab-cli-skills/glab-schedule/SKILL.md" } }, "instructions": "# glab schedule\n\n## Overview\n\n```\n\n Work with GitLab CI/CD schedules.\n USAGE\n glab schedule <command> [command] [--flags]\n COMMANDS\n create [--flags] Schedule a new pipeline.\n delete <id> [--flags] Delete the schedule with the specified ID.\n list [--flags] Get the list of schedules.\n run <id> Run the specified scheduled pipeline.\n update <id> [--flags] Update a pipeline schedule.\n FLAGS\n -h --help Show help for this command.\n -R --repo Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.\n```\n\n## Quick start\n\n```bash\nglab schedule --help\n```\n\n## Structured output\n\n`glab schedule list` supports `--output json` / `-F json` for structured output, which is useful for agent automation.\n\nThe human list header uses the API-reported total across pages rather than treating the current page length as the total. JSON still contains only the fetched page of schedules; use `--page` and `--per-page` to inspect subsequent pages. Do not mistake the header's total for a fully fetched inventory, and do not create, update, run, or delete schedules as part of a read-only audit.\n\n```bash\n# List schedules with JSON output\nglab schedule list --output json\nglab schedule list -F json\n```\n\n## Schedule variables\n\nSchedule variable keys are validated before schedule creation. Empty keys are rejected, so check generated `--variable <key>:<value>` input before creating schedules.\n\n## Subcommands\n\nSee [references/commands.md](references/commands.md) for full `--help` output.", "cost": { "context_tokens": 405 } }

glab-schedule

About

glab schedule

Overview

Quick start

Structured output

Schedule variables

Subcommands

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