dotnet-ai
Overview
Use this skill for AI and ML work in .NET, including LLM integration, agentic workflows, RAG pipelines, MCP servers or clients, embeddings, and ML.NET systems using dotnet/skills.
Workflow
- Clarify the AI task, data flow, model/provider, latency, privacy, and evaluation constraints.
- Choose .NET libraries and architecture that fit the repository's hosting model and deployment target.
- Keep prompt, retrieval, tool, and model contracts explicit and testable.
- Validate with unit tests, integration tests, evals, or deterministic smoke checks where possible.
Guardrails
- Do not hard-code secrets, model credentials, or provider-specific assumptions.
- Keep user data, embeddings, logs, and prompts privacy-aware.
- Prefer measurable quality and latency criteria over vague AI behavior claims.
Expected Output
Return a .NET AI implementation or plan with architecture, provider assumptions, and verification.
1---2name: dotnet-ai3description: AI and ML skills for .NET: technology selection, LLM integration, agentic workflows, RAG pipelines, MCP, and classic ML with ML.NET.4license: MIT5---67# dotnet-ai89## Overview1011Use this skill for AI and ML work in .NET, including LLM integration, agentic workflows, RAG pipelines, MCP servers or clients, embeddings, and ML.NET systems using [dotnet/skills](https://github.com/dotnet/skills).1213## Workflow14151. Clarify the AI task, data flow, model/provider, latency, privacy, and evaluation constraints.162. Choose .NET libraries and architecture that fit the repository's hosting model and deployment target.173. Keep prompt, retrieval, tool, and model contracts explicit and testable.184. Validate with unit tests, integration tests, evals, or deterministic smoke checks where possible.1920## Guardrails2122- Do not hard-code secrets, model credentials, or provider-specific assumptions.23- Keep user data, embeddings, logs, and prompts privacy-aware.24- Prefer measurable quality and latency criteria over vague AI behavior claims.2526## Expected Output2728Return a .NET AI implementation or plan with architecture, provider assumptions, and verification.