The skills cover choosing a pattern, wiring tools, sessions, workflows and hosting. The .NET skill covers AIAgent, Microsoft.Extensions.AI, NuGet packages, dependency injection and ASP.NET Core hosting, while the Python skill covers Agent, provider packages, middleware, context providers and workflow patterns. Developers can install them with the GitHub CLI using gh skill install, or with npx skills add, and the post recommends pinning a tag or commit for a reproducible snapshot.
The post suggests pairing the builder skill with the Microsoft Learn MCP Server, which lets a coding agent search the Agent Framework documentation and fetch full articles. For applications that also use Azure or Foundry, it points to the Azure Skills Plugin, which includes the Azure MCP Server and Foundry MCP. Applications still need their own SDK packages and model credentials.
Why it matters if you build agents
Teams using a compatible coding agent can get Agent Framework-specific guidance on pattern choice and setup without leaving their editor, though the skills are installed from the main branch by default.
The guidance favors the smallest suitable pattern, so a single agent is recommended when tools and sessions are enough, with harnesses or workflows reserved for loops, explicit stages or checkpointing.
Get stories like this every weekday
One short email with the day's agent tooling news.