Microsoft shipped built-in agent skills in Visual Studio this week. The July 2026 update includes skills authored by the .NET and Azure teams, a new Copilot Chat agent built on the GitHub Copilot SDK, and organization-level custom instructions. Skills are no longer a community experiment. They are shipping inside the IDE.

This is the first time a major IDE vendor has bundled framework-specific agent skills as a first-party feature. It changes the calculus for developers evaluating whether skills are ready for production work.

What Microsoft shipped

The update landed on July 28. Three things matter:

Built-in .NET and Azure skills. Visual Studio now includes skills written by Microsoft’s own framework teams. Two .NET skills ship with the IDE: dotnet-webapi, which guides ASP.NET Core HTTP endpoint creation with proper HTTP semantics and OpenAPI metadata, and analyzing-dotnet-performance, which scans code for roughly 50 performance anti-patterns across async, memory, strings, collections, LINQ, serialization, and I/O.

The broader .NET Agent Skills repository on GitHub contains additional skills for data access, diagnostics, MSBuild, NuGet, upgrades, MAUI, AI development, testing, ASP.NET Core, and Blazor. Not all of these are bundled in Visual Studio yet, but the infrastructure is there.

On the Azure side, skills cover infrastructure preparation (Bicep, Terraform, Dockerfiles, managed identity), validation (configuration, permissions, build checks), and deployment with error recovery. Microsoft’s Azure Skills Plugin repository documents an Azure MCP Server with over 200 structured tools across more than 40 Azure services.

A new agent built on the Copilot SDK. The Agent (Preview) in Copilot Chat is built on the same GitHub Copilot SDK that powers the Copilot CLI. The SDK handles planning, tool invocation, and file edits through JSON-RPC. It supports TypeScript, Python, Go, .NET, Java, and Rust. Developers can start work in Copilot CLI, VS Code, or the GitHub app and continue it in Visual Studio.

Skills are off by default. This is worth noting for the right reasons. Microsoft requires developers to review and explicitly enable each skill. They appear in the “Built-in” category of the Copilot tool picker when the corresponding workload is installed. You can hover over a skill to see its description and file path, or open the full skill file to inspect it. This opt-in model avoids the problem of invisible agent behavior while still making skills discoverable.

Why this matters

Agent skills have been growing as an open-source pattern since early 2026. Projects like Claude Code skills, Cursor rules, and community skill repositories proved the concept: give an AI agent structured instructions for a specific task, and it performs that task more reliably than raw prompting.

But adoption had a ceiling. Skills lived in community repos and personal configs. There was no signal from major vendors that this was a supported pattern rather than a power-user hack.

Microsoft just sent that signal.

When the .NET team writes a skill for ASP.NET Core Web APIs and ships it inside Visual Studio, it validates the entire pattern. It says: structured agent instructions are not a workaround. They are how you teach an agent to do framework-specific work correctly.

Three implications stand out:

Framework teams will write skills. The .NET team writing dotnet-webapi and analyzing-dotnet-performance sets a precedent. If you maintain a framework, SDK, or platform, writing agent skills for it is now table stakes. Developers using AI agents will gravitate toward frameworks that have them.

Skills become a distribution channel. Microsoft is using Visual Studio as a skill distribution platform. Install the .NET workload, get .NET skills. Install the Azure workload, get Azure skills. This bundles agent capabilities with the tools developers already use. Other IDEs and platforms will follow this pattern.

Organization-level instructions matter. The update also introduces organization-level custom instructions that apply automatically across team members. Combined with built-in skills, this means enterprises can standardize how AI agents work across their codebase. Coding conventions, security policies, and architectural patterns can be enforced through skills rather than code review.

What this means for the AgentNDX directory

The AgentNDX Skills Directory tracks skills across agents and categories. Microsoft’s move validates the categories we have been indexing: engineering, security, compliance, product, and more.

It also draws a clearer line between skill types:

  • IDE-bundled skills like Microsoft’s .NET and Azure skills. These are first-party, maintained by framework teams, and distributed through the IDE. They handle framework-specific patterns.
  • Community and third-party skills listed on AgentNDX. These cover broader use cases — code review, security auditing, dependency scanning, compliance checking — that are not tied to a single framework.

Both types serve developers. The first-party skills handle “how do I use this framework correctly.” The community skills handle “how do I review, secure, and ship code regardless of framework.”

The bigger picture

Skills are following the same trajectory as package managers and extensions. They start as community experiments, prove their value, and then get absorbed into official tooling. Microsoft bundling skills in Visual Studio is the absorption phase.

For developers already using agent skills in Claude Code, Cursor, or Codex, this is confirmation that the pattern works. For developers who have not tried skills yet, Microsoft just made them harder to ignore.

The next question is whether other IDE vendors and framework teams follow. Based on the velocity of the agent tooling market in 2026, the answer is probably measured in weeks rather than months.

FAQ

Q: Do Visual Studio’s built-in skills work in VS Code? A: Not directly. The built-in skills are packaged for Visual Studio’s Copilot tool picker. However, the underlying Copilot SDK is cross-platform, and VS Code has its own skill and extension system. The .NET skills repository on GitHub is open, so developers could adapt them for other agents.

Q: Are Microsoft’s skills the same as Claude Code skills? A: They follow the same concept — structured instructions that teach an agent how to handle specific tasks — but the format and delivery differ. Claude Code skills install into CLAUDE.md. Visual Studio skills install through the workload system and appear in the Copilot tool picker. The underlying idea of reusable agent instructions is the same.

Q: Should I switch from Claude Code skills to Visual Studio skills? A: They are not mutually exclusive. Visual Studio skills are specific to .NET and Azure workflows inside Visual Studio. Claude Code skills cover a broader range of use cases and work in any project. If you use both tools, you can use both skill systems.