Agent skill
install-vscode-extension
How to install a VS Code extension from an extension ID. Useful when the user wants to add new capabilities to their VS Code environment by installing extensions.
Install this agent skill to your Project
npx add-skill https://github.com/microsoft/vscode/tree/main/extensions/copilot/assets/prompts/skills/install-vscode-extension
SKILL.md
Installing VS Code extensions
- VS Code extensions are identified by their unique extension ID, which typically follows the format
publisher.extensionName. For example, the Python extension by Microsoft has the IDms-python.python. - To install a VS Code extension, you need to use the VS Code command
workbench.extensions.installExtensionand pass in the extension ID. The args are of the format:
[extensionId, { enable: true, installPreReleaseVersion: boolean }]
NOTE: install the pre-release version of the extension if the user explicitly mentions it or if the current environment is VS Code Insiders. Otherwise, install the stable version.
- Run that command via the
copilot_runVscodeCommandtool. Make sure to pass theskipCheckargument as true to avoid checking if the command exists, as we know it does.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
component-fixtures
Use when creating or updating component fixtures for screenshot testing, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, and common pitfalls.
memory-leak-audit
Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.
fix-ci-failures
Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the `gh` CLI.
azure-pipelines
Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.
add-policy
Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.
chat-customizations-editor
Use when working on the Chat Customizations editor — the management UI for agents, skills, instructions, hooks, prompts, MCP servers, and plugins.
Didn't find tool you were looking for?