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

80%

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

85%

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

The body is a tight, actionable, well-sequenced guide that gives Claude exactly the command, tool, and arg structure needed. The only real slack is a small amount of basic context about extension-ID formats in step 1.

Suggestions

Trim the explanation of the 'publisher.extensionName' format in step 1 to a single inline example, since Claude already understands extension ID conventions.

Optionally show one complete example tool invocation (e.g. with 'ms-python.python' and a concrete installPreReleaseVersion value) to make the args schema fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The command, args, and tool call are lean and earn their place, but step 1 explains the extension-ID format ('publisher.extensionName') — a concept Claude largely already knows — which keeps it just short of the score-3 'every token earns its place' bar.	2 / 3
Actionability	It specifies the exact VS Code command ('workbench.extensions.installExtension'), the args structure, the tool to run it ('copilot_runVscodeCommand'), the 'skipCheck' argument, and a concrete example ID ('ms-python.python'), giving fully actionable, copy-oriented guidance.	3 / 3
Workflow Clarity	The three steps are clearly sequenced (identify ID → prepare command/args → run via tool), and per the simple-skill scoring note this non-destructive single task needs no explicit validation checkpoint to earn a 3.	3 / 3
Progressive Disclosure	The skill is under 50 lines, has no bundle files to reference, and is organized into clean numbered steps, satisfying the scoring-note condition for a score-3 simple skill without external references.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 is clear, distinctive, and answers both what it does and when to use it with third-person voice and no fluff. Its main weakness is limited trigger-term coverage and only a single named action.

Suggestions

Expand trigger terms to include natural variations a user might say, e.g. 'add a VS Code extension', 'install a marketplace extension', or 'enable an extension by ID'.

Consider stating the outcome alongside the action (e.g. 'Install and enable a VS Code extension by its extension ID') to round out the single named capability.

Dimension	Reasoning	Score
Specificity	It names the domain ('VS Code extension') and one concrete action ('install ... from an extension ID'), but does not list multiple specific actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action score-3 example.	2 / 3
Completeness	It states the 'what' ('install a VS Code extension from an extension ID') and an explicit 'when' trigger ('Useful when the user wants to add new capabilities to their VS Code environment by installing extensions'), satisfying both halves of the score-3 anchor.	3 / 3
Trigger Term Quality	'VS Code extension', 'extension ID', and 'installing extensions' are natural terms a user might say, but coverage is thin and omits common variations like 'add extension' or 'marketplace', so it falls short of the broad score-3 term list.	2 / 3
Distinctiveness Conflict Risk	The niche — installing VS Code extensions by extension ID — is clear and narrowly scoped with distinct triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	10 / 12 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: b87c504

Reviewed: 2 days 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.