VS Code Chat Customizations Editor Skill
Guides developers through safe changes and testing for VS Code’s chat customization management UI.
The skill is scoped to Chat Customizations editor code paths and declares a limited Bash/npx Playwright tool pattern, showing some least-privilege awareness. It does not define user confirmation, sensitive-data flows, external-network behavior, rollback, or operational safety boundaries, so 10 points are deducted.
It provides key folders, interface synchronization chains, test commands, fixture data requirements, and concrete layout diagnostics, making the happy path fairly clear. However, the referenced spec, sessions skill, component-fixtures skill, and launch skill are not included, and static review cannot verify runnable commands or failure feedback; 8 is appropriate under the static cap.
The intended audience is clear: maintainers working on the Chat Customizations editor, including Local, CLI, Claude harnesses and multiple customization types. Non-fit cases, trigger boundaries, input/output contracts, and Chinese-language support are not specified, so adaptability is limited.
The document is well organized and includes metadata, repository navigation, interfaces, tests, fixtures, CI, debugging guidance, and known fixture/product gaps. It lacks explicit versioning, changelog, named maintenance responsibility, and an independent update path, with several assumptions delegated to external skills.
For narrowly defined VS Code maintenance tasks, the guidance is actionable, especially for interface synchronization, fixture construction, and layout diagnosis. It produces no directly usable deliverable and provides no statically verifiable representative result or alternative-cost comparison, so 6 is awarded under the static cap.
The repository materials include CI workflows, test commands, and fixture conventions, making some claims auditable. They do not clearly cover every key path of this skill, and no reproduction was executed in this review, so 4 is appropriate under the static cap.
- This assessment is based only on static file review; tests, Playwright, compilation, and live-product debugging were not executed.
- The skill depends on unavailable AI_CUSTOMIZATIONS.md, sessions, component-fixtures, and launch skills, so parts of the guidance cannot be independently reproduced from the supplied evidence.
- The tool pattern declared in metadata does not fully match the component-screenshot MCP references and other external skill references in the body; actual permissions should be confirmed.
- No malware, credential theft, covert exfiltration, or other explicit red-line risk was identified; Chinese-language support and mainland-China network reachability are not evidenced.
What does this skill do, and when should you use it?
This skill targets development of the Chat Customizations editor in the VS Code repository, covering management UI for agents, skills, instructions, hooks, prompts, MCP servers, and plugins. It explains how to follow harness descriptors, storage-source filters, and cross-layer extension API synchronization rules. It also covers component fixtures, screenshot regression checks, layout diagnostics, and live Code OSS debugging. Its scope is limited to the editor described by `.github/skills/chat-customizations-editor/SKILL.md`; it does not describe the capabilities of the repository’s other skills.
It instructs developers to read src/vs/sessions/AI_CUSTOMIZATIONS.md before changes and update it afterward; locate chat common interfaces, the management editor, sessions-window overrides, and sessions tree code; keep changes to the proposed customization provider API synchronized across the extension API, IPC DTO, ExtHost, MainThread, and internal interface layers; populate component fixtures with data for each customization type; use npx @playwright/cli to connect to Code OSS, open the customization editor, switch sections, and inspect DOM layout; and run the specified unit test, client type-check, and layer-validation commands.
- A VS Code developer needs to add or modify management UI for agents, skills, prompts, MCP servers, or plugins.
- A developer changes harness descriptors, button overrides, or storage-source filtering and must verify both core and sessions registrations.
- An extension API contributor adds fields to `chatSessionCustomizationProvider` and needs to propagate them through the complete API and IPC mapping chain.
- A test developer maintains component screenshot fixtures and needs coverage for tabs, harnesses, or narrow layouts.
- A developer investigates list-height, reflow, or real-data layout problems that do not reproduce in mocked component fixtures.
What are this skill's strengths and limitations?
- Provides concrete guidance for the editor’s folders, interfaces, API synchronization chain, and test fixtures.
- Covers component screenshots, CI regression gates, live-product debugging, and common layout failure modes.
- Explicitly requires consistency between core and sessions registrations and defines the five layers affected by extension API field changes.
- Distributed with the MIT-licensed Code - OSS repository.
- Its scope is tightly limited to the Chat Customizations editor in the VS Code source tree rather than general chat customization development.
- It depends on VS Code internal paths, interfaces, and mocked test services, so it is not designed for use outside this repository.
- The source does not provide standalone installation steps, version requirements, or cross-platform validation evidence.
- It requires shell and filesystem access plus `@playwright/cli`; some screenshot workflows also depend on the repository’s MCP component-screenshot tool.
How do you install this skill?
This skill is one of 61 skills in the microsoft/vscode repository and is located at .github/skills/chat-customizations-editor/SKILL.md. The source provides the repository URL, https://github.com/microsoft/vscode, but no standalone installation command or dedicated destination directory; place the file where the Agent Skills client can discover it. The repository as a whole is distributed under the MIT license.
How do you use this skill?
In a VS Code checkout, give a task such as: “Modify the Chat Customizations editor’s MCP Servers tab and add screenshot-fixture coverage.” Read src/vs/sessions/AI_CUSTOMIZATIONS.md first, make the changes using the documented folders and interfaces, and update the specification afterward. For UI verification, use the component fixtures or connect to a running Code OSS instance with npx @playwright/cli. The source lists ./scripts/test.sh --grep "applyStorageSourceFilter|customizationCounts", npm run typecheck-client, and npm run valid-layers-check; these assume an appropriate VS Code source-development environment.