Agent Skills

memory-leak-audit

✓★ 187,144

by microsoft

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.

🧰 Not standalone — use together with microsoft/vscode

cpu-profile-analysis

✓★ 187,144

by microsoft

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.

🧰 Not standalone — use together with microsoft/vscode

accessibility

✓★ 187,144

by microsoft

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

🧰 Not standalone — use together with microsoft/vscode

fix-ci-failures

✓★ 187,144

by microsoft

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.

🧰 Not standalone — use together with microsoft/vscode

heap-snapshot-analysis

✓★ 187,144

by microsoft

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.

🧰 Not standalone — use together with microsoft/vscode

project-setup-info-context7

✓★ 187,144

by microsoft

Comprehensive setup steps to help the user create complete project structures in a VS Code workspace. This tool is designed for full project initialization and scaffolding, not for creating individual files. When to use this tool: when the user wants to create a new complete project from scratch; when setting up entire project frameworks (TypeScript projects, React apps, Node.js servers, etc.); when initializing Model Context Protocol (MCP) servers with full structure; when creating VS Code exte

🧰 Not standalone — use together with microsoft/vscode

author-contributions

✓★ 187,144

by microsoft

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

🧰 Not standalone — use together with microsoft/vscode

add-dock-band

✓★ 136,050

by microsoft

Add dock band support to your Command Palette extension for persistent toolbar widgets. Use when asked to add dock support, toolbar buttons, persistent UI widgets, taskbar integration, live-updating status displays, quick-access buttons, or always-visible controls. Supports single buttons, multi-button strips, and live-updating content.

🧰 Not standalone — use together with microsoft/powertoys

add-adaptive-card-form

✓★ 136,050

by microsoft

Create form-based UI for your Command Palette extension using Adaptive Cards. Use when asked to add forms, user input fields, toggle switches, text inputs, dropdown menus, data entry, surveys, configuration dialogs, or interactive content pages. Supports the Adaptive Cards Designer for visual form building.

🧰 Not standalone — use together with microsoft/powertoys

add-fallback-commands

✓★ 136,050

by microsoft

Add fallback commands to your Command Palette extension for catch-all search behavior. Use when asked to add search functionality, query matching, direct input handling, calculator-style evaluation, URL opening, command execution, or results that appear when no other extension matches. Used by 14 of 20 built-in extensions.

🧰 Not standalone — use together with microsoft/powertoys

publish-extension

✓★ 136,050

by microsoft

Publish your Command Palette extension to the Microsoft Store or WinGet. Use when asked to publish, distribute, release, deploy to store, create MSIX packages, submit to WinGet, set up CI/CD for releases, or automate builds with GitHub Actions.

🧰 Not standalone — use together with microsoft/powertoys

wpf-to-winui3-migration

✓★ 136,050

by microsoft

Guide for migrating PowerToys modules from WPF to WinUI 3 (Windows App SDK). Use when asked to migrate WPF code, convert WPF XAML to WinUI, replace System.Windows namespaces with Microsoft.UI.Xaml, update Dispatcher to DispatcherQueue, replace DynamicResource with ThemeResource, migrate imaging APIs from System.Windows.Media.Imaging to Windows.Graphics.Imaging, convert WPF Window to WinUI Window, migrate .resx to .resw resources, migrate custom Observable/RelayCommand to CommunityToolkit.Mvvm so

🧰 Not standalone — use together with microsoft/powertoys

add-extension-settings

✓★ 136,050

by microsoft

Add a settings page to your Command Palette extension. Use when asked to add settings, preferences, configuration options, toggles, text inputs, dropdowns, or user-customizable behavior. Covers ToggleSetting, TextSetting, ChoiceSetSetting, and persistence.

🧰 Not standalone — use together with microsoft/powertoys

winmd-api-search

✓★ 136,050

by microsoft

Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI/ML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).

🧰 Not standalone — use together with microsoft/powertoys

playwright-cli

✓★ 92,271

by microsoft

Automate browser interactions, test web pages and work with Playwright tests.

🧰 Not standalone — use together with microsoft/playwright

playwright-trace

✓★ 92,271

by microsoft

Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.

🧰 Not standalone — use together with microsoft/playwright

playwright-cli

✓★ 11,813

by microsoft

Automate browser interactions, test web pages and work with Playwright tests.

🧰 Not standalone — use together with microsoft/playwright-cli

rushstack-best-practices

✓★ 6,479

by microsoft

Provides best practices and guidance for working with Rush monorepos. Use when the user is working in a Rush-based repository, asks about Rush commands (install, update, build, rebuild), needs help with project selection, dependency management, build caching, subspace configuration, or troubleshooting Rush-specific issues.

🧰 Not standalone — use together with microsoft/rushstack

hex1b

✓★ 6,148

by microsoft

CLI tool for automating any terminal application — TUI apps, shells, CLI tools, REPLs, and more. Use when you need to launch a process in a virtual terminal, capture its screen output, inject keystrokes or mouse input, take screenshots, record sessions, or assert on what's visible.

🧰 Not standalone — use together with microsoft/aspire

create-pr

✓★ 6,148

by microsoft

Create a pull request using the repository PR template. Use when asked to: create PR, open PR, push and create PR, submit PR, open pull request, send changes for review.

🧰 Not standalone — use together with microsoft/aspire

supply-chain-security

✓★ 3,123

by microsoft

Activate when reviewing or modifying dependency resolution, lockfile schema, package downloaders, signature/integrity checks, file integration cleanup, or anything that could expose APM to dependency confusion, typosquatting, malicious packages, or token leakage.

🧰 Not standalone — use together with microsoft/apm

docs-impact-classifier

✓★ 3,123

by microsoft

Use this skill to classify the documentation impact of a pull request diff, returning one of three verdicts -- no-change, in-place edit, or structural change -- with bounded LLM cost. Activate as a sibling skill of docs-sync; the orchestrator calls this first, before any panel spawn, to keep cost floor at 1 LLM call when no docs work is needed. Reads .apm/docs-index.yml as the corpus map; never reads the full corpus.

🧰 Not standalone — use together with microsoft/apm

cli-logging-ux

✓★ 3,123

by microsoft

Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (_rich_success, _rich_warning, _rich_error, _rich_info, _rich_echo), DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output — even if the user doesn't mention "logging" or "UX" explicitly.

🧰 Not standalone — use together with microsoft/apm

docs-grounding-verifier

✓★ 3,123

by microsoft

Use this skill to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code. Activate when you have specific pages to check for factual accuracy -- not when sweeping a whole corpus (use docs-corpus-audit for that) and not when triaging a PR diff (use docs-sync for that). Trigger nouns: "is this doc accurate", "verify the page against the code", "fact-check this section", "any claims that drifted from source", "fact-checking", "grounding audit", "drift hunt",

🧰 Not standalone — use together with microsoft/apm

placeholder

✓★ 3,123

by microsoft

🧰 Not standalone — use together with microsoft/apm

docs-impact-localizer

✓★ 3,123

by microsoft

Use this skill to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel. Activate after docs-impact-classifier returns verdict in_place; reads the candidate page list, fetches the actual page contents, narrows scope to specific sections within each page, and emits the per-page task brief the panel fans out against.

🧰 Not standalone — use together with microsoft/apm

hello

✓★ 3,123

by microsoft

🧰 Not standalone — use together with microsoft/apm

devx-ux

✓★ 3,123

by microsoft

Activate when designing or modifying CLI command surfaces, command help text, install/init/run flows, error wording, or first-run experience in the APM CLI -- even when the user does not say "UX" explicitly.

🧰 Not standalone — use together with microsoft/apm

oss-growth

✓★ 3,123

by microsoft

Activate for OSS adoption work -- README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles -- and any update to the maintained growth strategy at WIP/growth-strategy.md.

🧰 Not standalone — use together with microsoft/apm

apm-usage

✓★ 3,123

by microsoft

Activate when the user asks about APM (Agent Package Manager): installing, configuring, authoring, or troubleshooting AI-agent packages, dependencies, compilation, MCP servers, policy, or any `apm` CLI command.

🧰 Not standalone — use together with microsoft/apm