agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/vscode-copilot-chat/assets/prompts/skills/install-vscode-extension/SKILL.md

install-vscode-extension

Skill10k starsChanged 7 months agoMITArchived repositoryView on GitHub

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.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run that command via the copilot_runVscodeCommand tool.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Installing VS Code extensions

  1. 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 ID ms-python.python.
  2. To install a VS Code extension, you need to use the VS Code command workbench.extensions.installExtension and 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.

  1. Run that command via the copilot_runVscodeCommand tool. Make sure to pass the skipCheck argument as true to avoid checking if the command exists, as we know it does.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free