Claude Skill

dotnet-mlnet

Use ML.NET to train, evaluate, or integrate machine-learning models into .NET applications with realistic data preparation, inference, and deployment expectations.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download postpartum-genushyacinthus29-dotnet-skills-skills_dotnet-mlnet-bfa4ebd.zip · 11 KB

Install

skills CLI npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-mlnet
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install postpartum-genushyacinthus29-dotnet-skills@llmmart
Git git clone https://github.com/Postpartum-genushyacinthus29/dotnet-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole postpartum-genushyacinthus29/dotnet-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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 - Data loading, training pipelines, evaluation metrics, deployment strategies, and feature engineering patterns
  • examples.md - Complete examples for sentiment analysis, price prediction, image classification, anomaly detection, recommendations, clustering, fraud detection, text classification, object detection, and AutoML
Files (dotnet-skills)
  • references
    • examples.md 28.7 KB
      Loading…
    • patterns.md 18.7 KB
      Loading…
  • SKILL.md 1.9 KB
    ---
    name: dotnet-mlnet
    version: "1.0.0"
    category: "AI"
    description: "Use ML.NET to train, evaluate, or integrate machine-learning models into .NET applications with realistic data preparation, inference, and deployment expectations."
    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
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.