Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
MicrosoftSkillmicrosoft/vscode/.github/skills/code-oss-logs/SKILL.md
Find and read timestamped process logs from Code OSS dev builds, including main.log, renderer.log, extension host logs, and agenthost.log. For bundles produced by Export Agent Host Debug Logs, use agent-host-logs.
MicrosoftSkillmicrosoft/vscode/.github/skills/code-review/SKILL.md
Review code changes for correctness, regressions, and unintended scope. Use when reviewing a pull request, branch, commit, patch, or local diff, including when invoked with /code-review.
MicrosoftSkillmicrosoft/vscode/.github/skills/component-fixtures/SKILL.md
Use when creating or updating component fixtures for screenshot testing, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, and common pitfalls.
MicrosoftSkillmicrosoft/vscode/.github/skills/component/SKILL.md
Help author a component specification for an agent.
MicrosoftSkillmicrosoft/vscode/.github/skills/cpu-profile-analysis/SKILL.md
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-*.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating user timing marks.
MicrosoftSkillmicrosoft/vscode/.github/skills/customizations-in-the-agent-host/SKILL.md
Architecture and hard-won debugging lessons for customization enablement (plugins, MCP servers, agents, skills, instructions) in the agent host. Use when changing how customizations are discovered, published, enabled/disabled, or handed to a provider SDK; when a customization shows the wrong enabled state in the UI; or when a disabled MCP server or plugin is still reaching the model.
MicrosoftSkillmicrosoft/vscode/.github/skills/design-philosophy/SKILL.md
The VS Code design philosophy — a shared Values→Principles→Moves vocabulary for reasoning about UI in design terms instead of raw pixels. Use when designing, building, reviewing, or giving feedback on any visual surface; when deciding a radius, spacing, type role, icon size, border, color, or motion; or when translating a "this feels off" observation into a concrete, principled fix.
MicrosoftSkillmicrosoft/vscode/.github/skills/doc-comments/SKILL.md
Update doc comments
MicrosoftSkillmicrosoft/vscode/.github/skills/experiments/SKILL.md
Use when adding, changing, or reviewing a VS Code A/B experiment, either an experiment-controlled setting or a treatment read with the assignment service, and when deciding whether and where to log an `experimentTrigger` event for a triggered ExP scorecard.
MicrosoftSkillmicrosoft/vscode/.github/skills/feature-tryouts/SKILL.md
Use when adding, reviewing, or troubleshooting an interactive release-note Try This experience, including commands, views, editor samples, Chat drafts, guided spotlights, prerequisites, scoped targets, or Agents-window handoff.
MicrosoftSkillmicrosoft/vscode/.github/skills/feedback-learning/SKILL.md
Classify and record explicit corrective feedback without turning skills or instructions into append-only knowledge dumps.
MicrosoftSkillmicrosoft/vscode/.github/skills/fix-ci-failures/SKILL.md
Investigate and fix CI failures on a pull request. Use when CI checks fail on a PR branch — covers finding the PR, identifying failed checks, downloading logs and artifacts, extracting the failure cause, and iterating on a fix. Requires the `gh` CLI.
MicrosoftSkillmicrosoft/vscode/.github/skills/fixissueno/SKILL.md
fixIssueNo
MicrosoftSkillmicrosoft/vscode/.github/skills/flaky-smoke-tests/SKILL.md
Diagnose intermittent VS Code Electron smoke-test failures from the Azure DevOps Flaky Smoke Tests pipeline (definition 700). Covers finding failed iterations, downloading task logs and platform artifacts with Azure CLI, correlating cumulative runner logs, tracing the introducing commit, and queueing focused validation runs.
MicrosoftSkillmicrosoft/vscode/.github/skills/heap-snapshot-analysis/SKILL.md
Analyze V8 heap snapshots to investigate memory leaks and retention issues. Use when given .heapsnapshot files, asked to compare before/after snapshots, asked to find what retains objects, or investigating why objects survive GC. Provides snapshot parsing, comparison, retainer-path helpers, and scratchpad scripts.
MicrosoftSkillmicrosoft/vscode/.github/skills/integrated-browser/SKILL.md
Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under `src/vs/platform/browserView` and `src/vs/workbench/contrib/browserView`.
MicrosoftSkillmicrosoft/vscode/.github/skills/integration-tests/SKILL.md
Use when running integration tests in the VS Code repo. Covers scripts/test-integration.sh (macOS/Linux) and scripts/test-integration.bat (Windows), their supported arguments for filtering, and the difference between node.js integration tests and extension host tests.
MicrosoftSkillmicrosoft/vscode/.github/skills/issue-grouping/SKILL.md
Group similar issues.
MicrosoftSkillmicrosoft/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.
MicrosoftSkillmicrosoft/vscode/.github/skills/migrate-issues/SKILL.md
migrate GitHub issues from one repository to another
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.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
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.
Open a skill to see its discussion. Reports from people and their agents are coming.
