vscode-dev-workbench

Use when the user wants to run the vscode.dev server locally and exercise the VS Code workbench or Agents window in the integrated browser against the local `microsoft/vscode` sources. Covers starting the dev server, the `vscode-quality=dev` URL, browser-driven interaction patterns, and optionally wiring up a local mock agent host for the Agents window.

Quality

88%

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

Quality

Content

77%

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

Highly actionable and clearly sequenced with real validation checkpoints, but the body is a long single-file document whose optional advanced sections would benefit from being split into one-level-deep reference files.

Suggestions

Move the optional mobile-emulation section and the mock-agent-host setup into dedicated reference files (e.g., references/mobile-emulation.md, references/mock-agent-host.md) and link to them from the body, so SKILL.md stays a lean overview.

Trim inferable framing prose such as 'This is the fastest way to validate web-only changes to the workbench without shipping an Insiders build.' to improve token efficiency.

Add a short table of contents or 'If you need X, jump to section Y' navigation cues to aid discovery within the longer sections.

Dimension	Reasoning	Score
Conciseness	The body is information-dense with hard-won operational specifics (the npm run dev cwd gotcha, service-worker cache, Monaco Enter behavior, protocol-version tag), but at ~137 lines it is long, and the optional mobile-simulation section plus inferable intro prose ('This is the fastest way to validate web-only changes...') could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready guidance: the pushd/npm run dev snippet, the curl readiness check, the service-worker unregister JS, the CDP mobile snippet, the mock-agent-host command with exact flags, and exact URLs with query parameters.	3 / 3
Workflow Clarity	Sequences are explicit with validation checkpoints — the curl '%{http_code}' == 200 readiness check, the ordered expected-log list for the mock host, the out/ prerequisite, and the symptom/cause/fix troubleshooting table for error recovery.	3 / 3
Progressive Disclosure	Sections are clearly organized with headers, but the skill is a >50-line monolithic file with no external references, and substantial optional sections (mobile emulation, mock agent host setup) are inline rather than split into reference files.	2 / 3
	Total	10 / 12 Passed

Description

100%

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

A strong, well-scoped description that names concrete capabilities, includes an explicit 'Use when...' trigger, and is unlikely to collide with other skills. It uses third-person voice throughout with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'run the vscode.dev server locally', 'exercise the VS Code workbench or Agents window in the integrated browser', 'starting the dev server', 'the vscode-quality=dev URL', 'browser-driven interaction patterns', and 'wiring up a local mock agent host' — matching the top anchor for specific concrete actions.	3 / 3
Completeness	Explicitly answers both: the trigger ('Use when the user wants to run the vscode.dev server locally and exercise the VS Code workbench...') and the what ('Covers starting the dev server, the vscode-quality=dev URL, browser-driven interaction patterns, and optionally wiring up a local mock agent host').	3 / 3
Trigger Term Quality	Covers the natural terms a developer would actually say — 'run the vscode.dev server locally', 'VS Code workbench', 'Agents window', 'integrated browser', 'microsoft/vscode sources' — giving good coverage rather than jargon-only phrasing.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (local vscode.dev server against a sibling microsoft/vscode checkout) with distinct triggers that would not fire for unrelated skills, so conflict risk is low.	3 / 3
	Total	12 / 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: .github/skills/vscode-dev-workbench/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.