MicrosoftSkillissue-grouping
microsoft/vscode/.github/skills/issue-grouping/SKILL.md
Group similar issues.
Claude skills and agent skills
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Most stars first · from page 10Worked for most · soon
MicrosoftSkillMicrosoftSkillmemory-leak-audit
microsoft/vscode/.github/skills/memory-leak-audit/SKILL.md
Audit code for memory leaks and disposable issues. Use when reviewing event listeners, DOM handlers, lifecycle callbacks, or fixing leak reports. Covers addDisposableListener, Event.once, MutableDisposable, DisposableStore, and onWillDispose patterns.
MicrosoftSkillmigrate-issues
microsoft/vscode/.github/skills/migrate-issues/SKILL.md
migrate GitHub issues from one repository to another
MicrosoftSkillotel
microsoft/vscode/.github/skills/otel/SKILL.md
OpenTelemetry guidance for VS Code agent experiences. Use when changing Agent Host telemetry, local Copilot Chat telemetry, provider-native spans or metrics, OTel settings and managed policy, trace persistence/export, or monitoring documentation.
MicrosoftSkillpolicy-and-managed-settings
microsoft/vscode/.github/skills/policy-and-managed-settings/SKILL.md
Use whenever adding, modifying, or reviewing any Copilot, agent, LLM, AI, tool, permission, sandbox, MCP, model, telemetry, feature-gate, setting, configuration, or enterprise control—especially anything an organization or administrator may need to manage. Start here to decide whether it belongs in runtime managed settings, a typed SDK contract, VS Code configuration policy, extension policy, or a split implementation. Run on every new Copilot/agent/LLM control and ANY change that adds a `policy:` field.
MicrosoftSkillsessions
microsoft/vscode/.github/skills/sessions/SKILL.md
Core principles and workflow router for changes to the Agents Window under src/vs/sessions.
MicrosoftSkillsetup-environment
microsoft/vscode/.github/skills/setup-environment/SKILL.md
First Time Setup
MicrosoftSkillsmoke-tests
microsoft/vscode/.github/skills/smoke-tests/SKILL.md
Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI.
MicrosoftSkillsweeper-implement
microsoft/vscode/.github/skills/sweeper-implement/SKILL.md
Implement a VS Code Sweeper agent-ready issue — fetch the sweeper's review record from its state repo, implement the change in the current vscode checkout from the review's brief (an implement-ready record) or from an approved sweeper-plan file, validate the diff against it, and — after the maintainer has reviewed the changes in their editor — open a draft PR. Use ONLY when the request explicitly asks for the sweeper — "sweeper-implement", "sweeper", "vscodesweeper", a sweeper record, an agent-ready issue, or a sweeper brief — or asks to implement a sweeper plan ("implement plan <n>", a `.sweeper/plans/issue-<n>.md` file). Do NOT use for a plain "fix this issue" request that doesn't mention the sweeper; fix those directly with your normal tools instead.
MicrosoftSkillsweeper-plan
microsoft/vscode/.github/skills/sweeper-plan/SKILL.md
Plan a VS Code Sweeper agent-ready issue with the maintainer — fetch the sweeper's review record from its state repo, put the review's open decisions to the maintainer, and write a plan file (.sweeper/plans/issue-<n>.md) for them to edit in their editor; it writes no code and ends there — the sweeper-implement skill implements the approved plan. Use ONLY when the request explicitly asks for the sweeper plan — "sweeper-plan", "plan … with the sweeper", a sweeper record or agent-ready issue to plan first. Do NOT use for a plain planning request that doesn't mention the sweeper.
MicrosoftSkillsymbolicate-crash-dump
microsoft/vscode/.github/skills/symbolicate-crash-dump/SKILL.md
Symbolicate a native VS Code crash dump (.dmp) using electron-minidump. Use when given a crash dump file, asked to symbolicate a crash, resolve missing method names in a native crash backtrace, or attach Electron/Insiders/Stable symbol files. VS Code team members only; requires macOS or Linux.
MicrosoftSkillunit-tests
microsoft/vscode/.github/skills/unit-tests/SKILL.md
Use when running unit tests in the VS Code repo. Covers the runTests tool, scripts/test.sh (macOS/Linux) and scripts/test.bat (Windows), and their supported arguments for filtering, globbing, and debugging tests.
MicrosoftSkillupdate-instructions
microsoft/vscode/.github/skills/update-instructions/SKILL.md
update-instructions
MicrosoftSkillupdate-screenshots
microsoft/vscode/.github/skills/update-screenshots/SKILL.md
Update the committed blocks-ci screenshot hashes after the "Screenshots & Tests" check fails, or investigate a screenshot diff reported on a PR. Use when asked to update, accept, or refresh component screenshot baselines from CI. This skill should be run as a subagent.
MicrosoftSkillux-css-layout
microsoft/vscode/.github/skills/ux-css-layout/SKILL.md
VS Code CSS conventions, file organization, class naming, standard sizes, SplitView/Grid layout, scrollable content, responsive layout, and text overflow/ellipsis patterns. Use when writing CSS, building layouts, or fixing text truncation issues.
MicrosoftSkillux-theming
microsoft/vscode/.github/skills/ux-theming/SKILL.md
VS Code theming, color tokens, widget styles, focus indicators, and high-contrast theme support. Use when registering colors, styling widgets with theme tokens, or ensuring HC/focus compliance.
MicrosoftSkillvalidate-ui-scenario
microsoft/vscode/.github/skills/validate-ui-scenario/SKILL.md
Use when reproducing a UI bug or verifying a fix by driving a real VS Code window end to end and capturing evidence. Writes a scenario file, runs it against a dev build or installed Insiders, and produces a captioned video, per-step screenshots, a Playwright trace, and an HTML report to attach to an issue or pull request.
MicrosoftSkillvscode-dev-workbench
microsoft/vscode/.github/skills/vscode-dev-workbench/SKILL.md
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.
MicrosoftSkillact-on-feedback
microsoft/vscode/src/vs/sessions/skills/act-on-feedback/SKILL.md
Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.
MicrosoftSkillcode-review
microsoft/vscode/src/vs/sessions/skills/code-review/SKILL.md
Perform a code review of the current session's changes. Use when the user requests a code review via the Run Code Review button in the Changes toolbar.
About skills
What is a Claude skill?
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.