dotnet

Classify .NET repositories by SDK and framework to route to specialized skills.

2|Updated Mar 17, 2026

Search Tags:#routing #dotnet #software-engineering #code-generation #framework-detection #app-model-detection #skill-hand-off

Ready to run

npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-sayedihashimi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet
Source: https://github.com/sayedihashimi/copilot-skill-eval/tree/main/examples/aspnet-razor-pages/skills/managedcode-dotnet-skills/dotnet
Command: npx skills add https://github.com/sayedihashimi/copilot-skill-eval --skill dotnet-sayedihashimi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Classifies a .NET repository to identify the primary app model and route it to the narrowest specialized skill, avoiding generic guidance.

Core Features & Use Cases

Route to the narrowest matching .NET skill based on project SDKs, frameworks, and app models.
Detect common .NET app patterns (ASP.NET Core, Blazor, MAUI, EF, etc.) and hand off to the appropriate specialized skill.
Use case: a monorepo with multiple frameworks gets routed to the right skill to generate, review, or analyze code.

Quick Start

Provide a .NET repository and ask the router to identify the primary app model and hand off to the most specific skill.

Frequently Asked Questions about dotnet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I route a .NET monorepo to the correct specialized skill for code generation?▼

To route a .NET monorepo, the skill classifies the repository by analyzing project SDKs and target frameworks to detect the primary app model, then hands off to the narrowest specialized skill for precise code generation guidance.

What .NET app models can be detected for framework-specific skill handoff?▼

Framework-specific skill handoff supports detecting common .NET app models including ASP.NET Core, Blazor, MAUI, and Entity Framework, ensuring the repository receives accurate, specialized guidance instead of generic advice.

When do I need app-model detection for a multi-framework .NET codebase?▼

App-model detection is needed for multi-framework .NET codebases when you require precise handoff for code generation, review, or quality checks, validating repo compatibility to ensure accurate framework-specific guidance across the detected stack.

Does the .NET skill router work with Blazor and MAUI project SDKs?▼

Yes, the .NET skill router works with Blazor and MAUI project SDKs by performing target framework analysis to identify the primary app model and route the repository to the appropriate specialized skill.

Can I avoid generic .NET guidance for my ASP.NET Core repository?▼

You can avoid generic .NET guidance by using the router to classify your ASP.NET Core repository, which identifies the primary app model and routes it to the narrowest matching specialized skill for accurate, framework-specific code analysis.

What is the best way to validate repo compatibility before .NET code generation?▼

The best way to validate repo compatibility is to apply project SDK detection and target framework analysis, which identifies the app model and ensures the codebase is routed to a compatible specialized skill for generation.