test-on-vm
microsoft/microsoft-ui-xaml/.github/skills/test-on-vm/SKILL.md
EXPERIMENTAL. Run locally built WinUI interaction tests on a Hyper-V VM through PowerShell Direct. Use when asked to run WinUI tests on a local VM.
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
microsoft/microsoft-ui-xaml/.github/skills/test-on-vm/SKILL.md
EXPERIMENTAL. Run locally built WinUI interaction tests on a Hyper-V VM through PowerShell Direct. Use when asked to run WinUI tests on a local VM.
microsoft/microsoft-ui-xaml/src/.github/skills/bt-build/SKILL.md
Fast incremental C++/MSBuild builds using bt. Use when the user wants to compile, build, check what's dirty, or query build dependencies in a repo that has .vcxproj files. Prefer bt over invoking MSBuild directly for inner-loop source changes (.cpp, .h, .idl, .xaml, .appxmanifest).
microsoft/microsoft-ui-xaml/src/.github/skills/test-suite-setup/SKILL.md
Complete end-to-end setup and execution of the WinUI3 test suite locally. Delegates building to the build skill, then handles test payload creation, machine setup, and running all tests.
microsoft/vscode-docs/.github/skills/blog-writer/SKILL.md
Plan, write, and review VS Code blog posts. ALWAYS use this skill when the user asks to "write a blog post", "draft a blog", "add a blog post for", "review this blog post", or provides a feature/issue/PR to announce on the VS Code blog. For new posts, it proposes an outline and asks clarifying questions first, and does not edit any files until you approve the plan.
microsoft/vscode-docs/.github/skills/content-redirect/SKILL.md
Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.
microsoft/vscode-docs/.github/skills/daily-docs-audit/SKILL.md
Audit recently merged microsoft/vscode pull requests for documentation impact, stage deduplicated issue proposals, and create confirmed issues in microsoft/vscode-docs. ALWAYS use this skill when asked to run or configure a daily docs audit, identify documentation work from merged VS Code PRs, review pending docs issue proposals, or create docs issues for product updates.
microsoft/vscode-docs/.github/skills/docs-product-alignment/SKILL.md
Audit and update docs/copilot/ documentation to accurately reflect current VS Code AI capabilities. Use when: competitive analysis reveals gaps, product launches new features, docs use outdated framing, or keyword coverage needs strengthening for discoverability by users and AI agents. Produces a gap analysis plus targeted edits across affected files.
microsoft/vscode-docs/.github/skills/doc-writer/SKILL.md
Plan and write VS Code documentation for a new or updated feature. ALWAYS use this skill when the user asks to "document", "add docs for", "write docs for", or "update the docs for" a feature, or provides a GitHub issue/PR link to document — even if the change seems small. Proposes a documentation plan and asks clarifying questions first — it does not edit any files until you approve the plan.
microsoft/vscode-docs/.github/skills/frontmatter-description/SKILL.md
Check and optimize MetaDescription frontmatter fields in VS Code documentation. Use when auditing, adding, or improving page descriptions for SEO and discoverability. Apply this when making content changes to markdown articles.
microsoft/vscode-docs/.github/skills/pr-review/SKILL.md
Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.
microsoft/vscode-docs/.github/skills/release-note-writer/SKILL.md
Guidelines for writing and reviewing Insiders and Stable release notes for Visual Studio Code. This also includes instructions for updating release notes for recovery releases.
microsoft/vscode-docs/.github/skills/write-my-release-notes/SKILL.md
Generate VS Code release notes for the features you worked on in a milestone. ALWAYS use this skill when the user asks to "write release notes for my features", "document my milestone features", or "generate release notes from my issues". It gathers the milestone features you own from GitHub, analyzes each feature and its related issues, and writes user-focused feature sections into the milestone release notes file.
microsoft/rushstack/skills/rushstack-best-practices/SKILL.md
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.
microsoft/aspire/.agents/skills/api-review/SKILL.md
Reviews .NET API surface area PRs for design guideline violations. Analyzes api/*.cs file diffs, applies review rules from .NET Framework Design Guidelines and Aspire conventions, and attributes findings to the developer who introduced each API (via git blame). Use this when asked to review API surface area changes.
6 projects use a version of this
microsoft/aspire/.agents/skills/azdo-internal/SKILL.md
Use when asked to trigger or inspect Aspire internal Azure DevOps builds, source-index runs, or release validation on dnceng/internal; push to the internal mirror; download build logs or artifacts; or validate eng/ pipeline changes in microsoft/aspire.
1 project uses a version of this
microsoft/aspire/.agents/skills/backport-pr/SKILL.md
Backports a merged PR to a release branch by triggering the /backport bot, waiting for the bot-created PR, and filling in the shiproom template (Customer Impact, Testing, Risk, Regression?). Use when asked to: backport a PR, port a fix to a release branch, fill in a backport template, prepare a backport for shiproom review.
5 projects use a version of this
microsoft/aspire/.agents/skills/bump-aspire-version/SKILL.md
Bumps the Aspire repository product version in eng/Versions.props using previous version-bump commits as guidance. Use when asked to bump Aspire branding, advance the repository to a new major or minor version, or create a version-bump PR. Not for external dependency, SDK, or container-image updates.
1 project uses a version of this
microsoft/aspire/.agents/skills/cli-channel-debugging/SKILL.md
Emulates any Aspire CLI build identity (channel, version, commit, package source) from a locally built CLI using ASPIRE_CLI_* environment variables and the install sidecar, so a reported bug can be reproduced and fixed locally without going through the install/PR loop. Use this when asked to reproduce channel/version/quality-specific CLI behavior, simulate a daily/staging/stable/PR build locally, or decide which override knobs to set for a given scenario.
1 project uses a version of this
microsoft/aspire/.agents/skills/code-review/SKILL.md
Review a GitHub pull request or requested local diff for problems. Use when asked to review a PR, do a code review, check a PR for issues, or review local changes. Focuses only on identifying problems — not style nits or praise.
Often used withclose-specadd-new-modelcompare-screenshots
microsoft/aspire/.agents/skills/connection-properties/SKILL.md
Specialized agent for creating and improving Connection Properties in Aspire resource and README files
1 project uses a version of this
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.