Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
glab-changelog - Skill - OpenSmartRoute
Skillv1.0.0
glab-changelog
Generate changelogs from GitLab releases, tags, and commits. Use when creating release notes, generating changelog files, or documenting version history.
Imported from vince-winkintel/gitlab-cli-skills (glab-changelog/SKILL.md). Install upstream with npx skills add vince-winkintel/gitlab-cli-skills --skill glab-changelog. Copyright stays with the author.
glab changelog
Overview
Interact with the changelog API.
USAGE
glab changelog <command> [command] [--flags]
COMMANDS
generate [--flags] Generate a changelog for the repository or project.
FLAGS
-h --help Show help for this command.
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install glab-changelog 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.