← ClaudeAtlas

create-agent-dotnetlisted

This skill creates a durable AI agent application in .NET using Microsoft Agent Framework on Dapr Workflow. Use this skill when the user asks to "create an agent in .NET", "build an agent app in C#", or "scaffold a .NET agent with Microsoft Agent Framework".
diagrid-labs/dapr-skills · ★ 12 · AI & Automation · score 80
Install: claude install-skill diagrid-labs/dapr-skills
# Create a .NET Agent Application ## Overview This skill describes how to create a durable AI agent application in .NET. > **On naming.** [Dapr Agents](https://github.com/dapr/dapr-agents) is a **Python-only** framework and is not used here. The .NET path is [Microsoft Agent Framework](https://learn.microsoft.com/en-us/agent-framework/) (`Microsoft.Agents.AI` + `Microsoft.Extensions.AI`) executed durably on Dapr Workflow by the [`Diagrid.AI.Microsoft.AgentFramework`](https://www.nuget.org/packages/Diagrid.AI.Microsoft.AgentFramework) package. That package turns every LLM call and every tool call into its own workflow activity, so an agent run survives a process restart and resumes from the last completed step. The `Dapr` in `AddDaprAgents()` / `IDaprAgentInvoker` names that workflow runtime — it is not the Python framework. The LLM is reached through a Dapr [conversation component](https://docs.dapr.io/reference/components-reference/supported-conversation/), not through a provider SDK registered in DI. Swapping providers is a YAML change, not a code change. Observability is not baked in. Dapr's own sidecar metrics and traces cover the workflow layer (see [`../shared/agent-metrics-prometheus.md`](../shared/agent-metrics-prometheus.md)); anything above that comes from the wrapped framework's OpenTelemetry support or from your own APM. ## Execution Order You MUST follow these phases in strict order: 1. **Check specification** — Check if the user specified what needs to be