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.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./extensions/copilot/assets/prompts/skills/install-vscode-extension/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean and actionable, giving the exact command, arg format, and tool to run it. Its main weakness is the absence of a verification step to confirm the extension actually installed, which caps workflow clarity despite the clear sequence.

Suggestions

Add a validation checkpoint after installation, e.g., verify the extension is enabled by running a command to list installed extensions or by checking the command returned success.

Briefly note how to obtain an extension ID when the user only gives a name (e.g., searching the marketplace) to close the actionability gap.

Trim the editorial aside 'as we know it does' to slightly tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is short and focused, giving the command name, arg format, and the tool to invoke it with only one mildly over-explanatory line ('as we know it does'); it mostly assumes Claude's competence, fitting the 4 anchor with minor trim opportunities.	4 / 5
Actionability	Provides the concrete VS Code command, the exact args array format, and the specific tool name (copilot_runVscodeCommand) with the skipCheck flag, which is mostly executable guidance with a minor gap around how to obtain the extension ID.	4 / 5
Workflow Clarity	A clear three-step sequence is present, but the operation (installing software into the environment) is a system-modifying action with no validation step confirming the install succeeded, so per the destructive/batch cap it cannot exceed 3.	3 / 5
Progressive Disclosure	This is a short single-purpose skill under 50 lines with no need for external references; the body is well-organized into a clean ordered sequence, meeting the simple-skill exception for a 5.	5 / 5
	Total	16 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill does and when to use it, with a distinct niche around VS Code extension installation. It is held back by limited enumeration of concrete actions and a thin set of natural trigger phrases.

Suggestions

Add concrete trigger phrases users would naturally say, such as 'Use when the user asks to install, add, or enable a VS Code extension or add-on.'

Enumerate the specific actions covered (e.g., 'install stable or pre-release versions, enable extensions by extension ID') to lift specificity.

Include common synonyms like 'add-on' or 'marketplace' to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('install a VS Code extension from an extension ID') and one concrete action (installing via an extension ID), but does not enumerate the specific steps or variations, matching the anchor for a clear what with limited action coverage.	3 / 5
Completeness	Provides a clear 'what' (installing a VS Code extension from an extension ID) and a 'when' ('Useful when the user wants to add new capabilities to their VS Code environment by installing extensions'); the trigger clause is present and reasonable, though it could be more specific with concrete trigger phrases, fitting the 4 anchor.	4 / 5
Trigger Term Quality	Includes relevant terms like 'VS Code extension' and 'extension ID', but lacks common synonyms or natural phrasings users might say (e.g., 'add-on', 'marketplace', 'install add-on'), placing it at the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The skill is narrowly scoped to installing VS Code extensions via extension ID, a fairly distinct niche with minor overlap risk only with general VS Code tooling skills, matching the 'mostly distinct' anchor.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: posit-dev/positron
Path: extensions/copilot/assets/prompts/skills/install-vscode-extension/SKILL.md
Commit: 9bb0f27

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.