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.

vscode-ext-commands - Skill

Name: vscode-ext-commands
Author: github

Imported from github/awesome-copilot (skills/vscode-ext-commands/SKILL.md) via skills.sh. Install upstream with npx skills add github/awesome-copilot --skill vscode-ext-commands. Copyright stays with the author.

VS Code extension command contribution

This skill helps you to contribute commands in VS Code extensions

When to use this skill

Use this skill when you need to:

Add or update commands to your VS Code extension

Instructions

VS Code commands must always define a title, independent of its category, visibility or location. We use a few patterns for each "kind" of command, with some characteristics, described below:

Regular commands: By default, all commands should be accessible in the Command Palette, must define a category, and don't need an icon, unless the command will be used in the Side Bar.
Side Bar commands: Its name follows a special pattern, starting with underscore (_) and suffixed with #sideBar, like _extensionId.someCommand#sideBar for instance. Must define an icon, and may or may not have some rule for enablement. Side Bar exclusive commands should not be visible in the Command Palette. Contributing it to the view/title or view/item/context, we must inform order/position that it will be displayed, and we can use terms "relative to other command/button" in order to you identify the correct group to be used. Also, it's a good practice to define the condition (when) for the new command is visible.

Install vscode-ext-commands 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": "github-awesome-copilot-vscode-ext-commands", "kind": "skill", "name": "vscode-ext-commands", "description": "Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices", "publisher": "github", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Guidelines for contributing commands in VS Code extensions. Indicates naming convention, visibility, localization and other relevant attributes, following VS Code extension development guidelines, libraries and good practices" ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/github/awesome-copilot", "path": "skills/vscode-ext-commands/SKILL.md", "ref": "HEAD", "url": "https://www.skills.sh/github/awesome-copilot/vscode-ext-commands", "key": "github/awesome-copilot/skills/vscode-ext-commands/SKILL.md" } }, "instructions": "# VS Code extension command contribution\n\nThis skill helps you to contribute commands in VS Code extensions\n\n## When to use this skill\n\nUse this skill when you need to:\n- Add or update commands to your VS Code extension\n\n# Instructions\n\nVS Code commands must always define a `title`, independent of its category, visibility or location. We use a few patterns for each \"kind\" of command, with some characteristics, described below:\n\n* Regular commands: By default, all commands should be accessible in the Command Palette, must define a `category`, and don't need an `icon`, unless the command will be", "cost": { "context_tokens": 317 } }

vscode-ext-commands

About

VS Code extension command contribution

When to use this skill

Instructions

Use it

Install vscode-ext-commands 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

Manifest

Reviews