Microsoft ships Agent Framework builder skills for coding agents
Microsoft has published installable Agent Framework builder skills for .NET and Python, aimed at coding agents rather than human developers. The skills guide agents on choosing patterns, wiring tools, sessions, workflows, and hosting, and are installed via a GitHub or skills CLI. They are development-time only and require a coding agent that supports the Agent Skills format, with language-specific guidance for each platform.

Microsoft ships Agent Framework builder skills for coding agents
Microsoft has published installable Agent Framework builder skills for .NET and Python, aimed at coding agents rather than human developers. The skills, maintained by Microsoft in the agent-framework repository, provide guidance for building and modifying Agent Framework applications: choosing a pattern, wiring tools, sessions, workflows, and hosting.
The skills are development-time only. They are not runtime skills loaded by the application that ships; the app still needs its SDK packages and model credentials. The coding agent must support the Agent Skills format, and installation is done through either the GitHub CLI (gh skill install microsoft/agent-framework agent-framework-builder-dotnet@main) or the skills CLI (npx skills add microsoft/agent-framework --skill agent-framework-builder-dotnet). The Python variant installs the same way. Both default to the main branch of the repository; Microsoft suggests pinning a tag or commit for reproducible snapshots. The two installers differ in supported clients and scope, so users are told to check the docs for whichever they pick.
Each skill has a SKILL.md entry point and focused references. The coding agent first inspects the project and dependencies, then loads only the guidance relevant to the task rather than every framework feature. The design favors the smallest suitable pattern: one agent when tools and sessions are enough, a harness when an operating loop is needed, or a workflow when explicit stages, routing, and checkpointing are part of the requirements. The framing is deliberate — a support assistant with several tools does not need a multi-agent system just because it has them.
The guidance is language-specific. The .NET skill covers AIAgent, Microsoft.Extensions.AI, NuGet packages, dependency injection, and ASP.NET Core hosting. The Python skill covers Agent, provider packages, middleware, context providers, and Python workflow patterns.
Microsoft recommends pairing either skill with the Microsoft Learn MCP Server, which lets the coding agent search the full Agent Framework documentation and fetch complete articles and code examples. Its Streamable HTTP endpoint is configured at https://learn.microsoft.com/api/mcp. For applications using other Microsoft services, the Azure Skills Plugin adds Foundry and Azure skills plus Azure and Foundry MCP servers; those require appropriate credentials and permissions.
Two prompting examples are included. For .NET: add a support assistant to an ASP.NET Core app, isolate conversations per user, require approval before changing tickets, and test tool behavior with a fake IChatClient. For Python: turn an existing research agent into a research-and-review workflow with checkpointing, preserving its response format. Users are told to specify provider, hosting target, persistence requirements, and approval boundaries; the skills then direct the agent to clarify consequential unknowns, preserve existing behavior, and validate the change.
A caveat applies: the skills' usefulness depends on how well a given coding agent follows the guidance. Microsoft asks anyone who hits a problem to open an issue with the skill name, the coding agent used, what was tried, and what went wrong.
Read the original at devblogs.microsoft.com →