dotnet

Route generic .NET tasks to the most specific platform skill.

8|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-postpartum-genushyacinthus29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet
Source: https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet
Command: npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-postpartum-genushyacinthus29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you route generic .NET guidance and tasks to the most specific platform skill, ensuring precise, context-aware advice instead of broad, generic recommendations.

Core Features & Use Cases

  • Auto-detects the repo's .NET app model, target frameworks, and workloads to inform routing decisions.
  • Delegates tasks to the narrowest specialized skill (e.g., dotnet-aspnet-core, dotnet-maui, dotnet-entity-framework-core) to avoid generic guidance.
  • Coordinates cross-cutting concerns such as project bootstrap, architecture, and quality tooling by handing off to companion skills when appropriate.
  • Provides a safe fallback to the generic .NET skill when no narrower match exists.

Quick Start

Provide the repository context and ask for the most precise .NET routing decision.

Frequently Asked Questions about dotnet

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

FAQPage Schema
How do I route .NET tasks to the correct project skill in a multi-model repository?

To route .NET tasks, this skill auto-detects the repository's app model, target frameworks, and workloads, delegating the task to the narrowest specialized skill for precise guidance.

What is the best way to avoid generic .NET guidance for specific frameworks like ASP.NET Core or MAUI?

Avoiding generic .NET guidance requires detecting the stack and delegating to the narrowest skill, such as dotnet-aspnet-core or dotnet-maui, ensuring context-aware advice.

Does this .NET routing approach work with mixed workloads and cross-cutting architecture concerns?

Yes, .NET routing works with mixed workloads by detecting the SDK and target frameworks, coordinating cross-cutting architecture concerns by handing off to companion skills.

Can I use this routing mechanism if my target .NET skill is unavailable?

If the target .NET skill is unavailable, the mechanism validates availability and provides a safe fallback to the generic .NET skill, avoiding mixing runner commands.

When do I need .NET skill detection for task routing decisions?

You need .NET skill detection when working with multi-model repositories where routing decisions must cover app models, workloads, and cross-cutting concerns like project structure.