We have added installable Microsoft Agent Framework builder skills for .NET and Python. They give coding agents Microsoft-maintained guidance for building and modifying Agent Framework applications, from choosing the right pattern to wiring tools, sessions, workflows, and hosting.
These are development-time skills for your coding assistant, not runtime skills loaded by the application you ship.
Use a coding agent that supports the Agent Skills format. With GitHub CLI, install the .NET skill from main:
gh skill install microsoft/agent-framework agent-framework-builder-dotnet@main
For Python:
gh skill install microsoft/agent-framework agent-framework-builder-python@main
Both examples use main for the latest repository guidance. Pin a tag or commit if you need a reproducible snapshot.
Alternatively, install either skill with the cross-agent CLI:
npx skills add microsoft/agent-framework --skill agent-framework-builder-dotnet
npx skills add microsoft/agent-framework --skill agent-framework-builder-python
Choose one installer, and check its documentation for supported clients and scope: GitHub CLI or skills CLI. Your application still needs its SDK packages and model credentials.
Pair the builder skill with Microsoft Learn MCP
The natural companion to either builder skill is the Microsoft Learn MCP Server. The skill provides focused implementation guidance, while Learn MCP lets your coding agent search the full Agent Framework documentation and fetch complete articles and code examples when it needs more detail.
Configure its Streamable HTTP endpoint:
https://learn.microsoft.com/api/mcp
What the guidance adds
Each skill has a SKILL.md entry point and focused references. The coding agent first inspects your project and dependencies, then loads the guidance relevant to the task rather than every framework feature at once.
Both skills favor 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. A support assistant does not need a multi-agent system just because it has several tools.
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.
A note on other Microsoft services
If your application also uses other Microsoft services, use the Azure Skills Plugin for Azure and Foundry work. Its microsoft-foundry skill covers Foundry model and agent workflows, while azure-prepare, azure-deploy, and azure-diagnostics help prepare, deploy, and troubleshoot Azure applications.
The plugin includes the Azure MCP Server for tasks such as listing resources and querying logs, plus Foundry MCP for model and agent operations. Add these when your application needs them; Azure operations require the appropriate credentials and permissions.
Put it to work
Prompt the coding agent naturally; compatible clients discover skills through their metadata, without a universal slash command. For .NET:
Add an Agent Framework support assistant to our ASP.NET Core app.
Use our model provider, isolate conversations per user, require approval
before changing tickets, and test tool behavior with a fake IChatClient.
For an existing Python application:
Turn this Python Agent Framework research agent into a research-and-review
workflow. Preserve its response format, add checkpointing, and test resume
behavior using the project's existing test tooling.
Include your provider, hosting target, persistence requirements, and approval boundaries when you know them. The skills direct the coding agent to clarify consequential unknowns, preserve existing behavior, and validate the change.
Give the builder skill for your language a try in your own project. If something doesn’t work, open an issue in the Agent Framework repository and include the skill name, the coding agent you used, what you tried, and what went wrong.
0 comments
Be the first to start the discussion.