/mlnet
Use ML.NET to train, evaluate, or integrate machine-learning models into .NET applications with realistic data preparation, inference, and deployment expectations. USE FOR: ML.NET integration; local model training or retraining; inference pipelines, model loading, evaluation,
$ npx -y skills add managedcode/dotnet-skills --skill mlnet --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/mlnet
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use ML.NET to train, evaluate, or integrate machine-learning models into .NET applications with realistic data preparation, inference, and deployment expectations. USE FOR: ML.NET integration; local model training or retraining; inference pipelines, model loading, evaluation,
SKILL.md
mlnet.SKILL.mdname: mlnet
description: "Use ML.NET to train, evaluate, or integrate machine-learning models into .NET applications with realistic data preparation, inference, and deployment expectations. USE FOR: ML.NET integration; local model training or retraining; inference pipelines, model loading, evaluation, and deployment review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made."
compatibility: "Requires ML.NET, Model Builder, or ML.NET CLI scenarios."
ML.NET
Trigger On
- integrating machine learning into a .NET application
- training or retraining ML.NET models from local data
- reviewing inference pipelines, model loading, or AutoML-generated code
Workflow
1. Start from the prediction task and data quality, not the algorithm or package list. 2. Separate training code from inference code so the production path stays lean and predictable. 3. Review feature engineering, normalization, label quality, and evaluation metrics before trusting model output. 4. Use Model Builder or the ML.NET CLI when they speed up exploration, but inspect the generated C# before treating it as production architecture. 5. Plan how the model is loaded, versioned, and refreshed in the application lifecycle. 6. Validate with representative datasets and explicit evaluation, not only with a sample that happens to run.
Deliver
- ML.NET pipelines that fit the prediction task
- production-usable inference integration
- evaluation evidence tied to the business scenario
Validate
- model quality is measured, not assumed
- training and inference responsibilities are separated
- deployment and versioning expectations are explicit
References
- [patterns.md](references/patterns.md) - Data loading, training pipelines, evaluation metrics, deployment strategies, and feature engineering patterns
- [examples.md](references/examples.md) - Complete examples for sentiment analysis, price prediction, image classification, anomaly detection, recommendations, clustering, fraud detection, text classification, object detection, and AutoML
Read more
name: mlnet description: "Use ML.NET to train, evaluate, or integrate machine-learning models into .NET applications with realistic data preparation, inference, and deployment expectations. USE FOR: ML.NET integration; local model training or retraining; inference pipelines, model loading, evaluation, and deployment review. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made." compatibility: "Requires ML.NET, Model Builder, or ML.NET CLI scenarios."
ML.NET
Trigger On
- integrating machine learning into a .NET application
- training or retraining ML.NET models from local data
- reviewing inference pipelines, model loading, or AutoML-generated code
Workflow
1. Start from the prediction task and data quality, not the algorithm or package list. 2. Separate training code from inference code so the production path stays lean and predictable. 3. Review feature engineering, normalization, label quality, and evaluation metrics before trusting model output. 4. Use Model Builder or the ML.NET CLI when they speed up exploration, but inspect the generated C# before treating it as production architecture. 5. Plan how the model is loaded, versioned, and refreshed in the application lifecycle. 6. Validate with representative datasets and explicit evaluation, not only with a sample that happens to run.
Deliver
- ML.NET pipelines that fit the prediction task
- production-usable inference integration
- evaluation evidence tied to the business scenario
Validate
- model quality is measured, not assumed
- training and inference responsibilities are separated
- deployment and versioning expectations are explicit
References
- [patterns.md](references/patterns.md) - Data loading, training pipelines, evaluation metrics, deployment strategies, and feature engineering patterns
- [examples.md](references/examples.md) - Complete examples for sentiment analysis, price prediction, image classification, anomaly detection, recommendations, clustering, fraud detection, text classification, object detection, and AutoML
Stop explaining .NET to your AI. Start building. We've all been there: asking Claude to use Entity Framework, only to get EF6 patterns in a .NET 8 project. Explaining to Copilot that Blazor Server and Blazor WebAssembly aren't the same thing.
Repo: managedcode/dotnet-skills
Other skills on dotnet-skills.
- /aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET. USE FOR: working on ASP.NET Core apps, services, or middleware; changing auth, routing, configuration,
Open skill - /aspire
Build, upgrade, and operate Aspire 13.4.x C# or TypeScript application hosts with the current CLI, AppHost, ServiceDefaults, integrations, dashboard, testing, MCP, and deployment patterns for distributed apps. USE FOR: Aspire.AppHost.Sdk, Aspire.Hosting.*,
Open skill - /azure-functions
Build, review, or migrate Azure Functions in .NET with correct execution model, isolated worker setup, bindings, DI, and Durable Functions patterns. USE FOR: working on Azure Functions in .NET; migrating from the in-process model to the isolated worker model; adding Durable
Open skill - /blazor
Build and review Blazor applications across server, WebAssembly, web app, and hybrid scenarios with correct component design, state flow, rendering, and hosting choices. USE FOR: building interactive web UIs with C# instead of JavaScript; choosing between Server, WebAssembly, or
Open skill - /entity-framework6
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. USE FOR: EF6 codebases; runtime versus ORM migration decisions; EDMX, code-first, ObjectContext, and legacy data-access
Open skill - /entity-framework-core
Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications. USE FOR: DbContext, migrations, model configuration, EF queries, tracking, loading, performance, transactions, and
Open skill

