@dotnet

msbuild-modernization provides a structured migration path from legacy .net framework projects to sdk-style csproj format, with before/after examples, a numbered checklist, and guidance on common pitfalls like embedded resources and multi-targeting.

optimizing-ef-core-queries covers detecting and fixing n+1 patterns, choosing tracking modes, leveraging compiled queries, and avoiding common linq translation pitfalls in entity framework core.

including-generated-files addresses msbuild's evaluation-execution phase mismatch by providing patterns to register generated artifacts in compile and filewrites item groups, with timing guidance for different file types.

technology-selection provides a decision tree for routing .net ai/ml tasks to ml.net, llms via microsoft.extensions.ai, agent frameworks, or local inference, with concrete guardrails for reproducibility, cost control, and non-determinism handling.

migrate-dotnet8-to-dotnet9 covers systematic upgrade of .net 8 projects to .net 9, resolving breaking changes across runtime, asp.net core, and ef core with clean builds and passing tests.

dump-collect configures and captures crash dumps for .net applications (coreclr and nativeaot) across linux, macos, and windows. scope is collection only, not analysis or root cause diagnosis.

nuget-trusted-publishing guides setup of oidc-based token authentication for github actions nuget deployments, eliminating long-lived api key management and rotation overhead.

extracts and symbolizes native backtrace frames from android tombstone files for .net runtime crashes, mapping pc offsets and buildids to function names and source locations via llvm-symbolizer and microsoft symbol servers.

dotnet-trace-collect guides developers through selecting and running diagnostic tools for production .net performance triage, covering tool trade-offs and platform-specific setup without performing analysis itself.

detects msbuild project path collisions in outputpath and intermediateoutputpath that cause parallel build failures, file locks, and nuget restore conflicts. identifies clashes across multi-targeted builds and multi-solution scenarios.

run-tests executes dotnet test with framework detection and filter support, handling vstest and mtp platforms. covers platform selection and filter syntax but lacks procedural depth on execution steps.

clr-activation-debugging helps diagnose .net framework runtime loading failures by analyzing mscoree.dll shim logs to determine why the clr failed to activate or selected the wrong version.

create-custom-agent scaffolds vs code .agent.md files with frontmatter, tools, instructions, and handoffs for specialized ai personas, but lacks implementation detail and error handling guidance.

incremental-build explains how msbuild skips targets when outputs are already up to date, covering inputs/outputs attributes, timestamp comparison, and the incremental flag to control rebuild behavior.

binlog-generation documents mandatory /bl flag injection across dotnet and msbuild commands for diagnostic log capture, targeting .net build pipelines with version-gated syntax.

build-parallelism documents msbuild worker node configuration and dependency graph concepts, with diagnostic approaches for identifying bottlenecks in multi-project builds.

dotnet-maui-doctor validates .net maui development environments by discovering version requirements dynamically from nuget apis and diagnosing missing sdks, workloads, jdk, and platform components.

mcp-csharp-debug covers local execution, ide breakpoint setup, protocol-level testing via mcp inspector, and copilot integration verification for c# mcp servers, but lacks actionable step-by-step procedures.

organizing msbuild infrastructure via directory.build.props and directory.build.targets files, clarifying evaluation order and appropriate use cases for each file type.

crap-score evaluates .net method quality by combining cyclomatic complexity and code coverage metrics into a single risk indicator, useful for identifying undertested complex code.

msbuild-antipatterns is a catalog of common msbuild build errors with detection patterns and remediation examples. focuses on exec task misuse and similar structural issues but lacks procedural depth and activation guidance.

writing-mstest-tests covers assertion patterns, data-driven test setup, and test modernization guidance for mstest 3.x/4.x. triggers are specific about when the skill applies (assertion replacement, bug fixes, datadriven conversions) but the skill provides no actionable procedure for actually implementing changes.

microbenchmarking covers benchmarkdotnet library patterns, job configuration, and comparative measurement methodology for .net performance analysis.

resolve-project-references explains why MSBuild's ResolveProjectReferences target appears expensive in performance summaries, clarifying the distinction between reported wall-clock time and actual cpu work to prevent misguided optimization efforts.

eval-performance outlines msbuild's evaluation phases and names diagnostic tools, but lacks actionable remediation steps, decision trees, or concrete recovery procedures for slow builds.

Establish build performance baselines and apply systematic optimization techniques. Only activate in MSBuild/.NET build context. USE FOR: diagnosing slow…

Run file-based C# apps with the .NET CLI when the user explicitly wants C#/.NET code without creating a project. Use for C# language/API experiments, one-file…

>-

Scaffolds new agent skills for the dotnet/skills repository. Use when creating a new skill, generating SKILL.md files, or setting up skill directory…

Diagnose MSBuild build performance bottlenecks using binary log analysis. Only activate in MSBuild/.NET build context. USE FOR: identifying why builds are slow…

>

Guide for using MSBuild Server to improve CLI build performance. Only activate in MSBuild/.NET build context. Activate when developers report slow incremental…

>

>

Analyze MSBuild binary logs to diagnose build failures. Only activate in MSBuild/.NET build context. USE FOR: build errors that are unclear from console…

>

>

dotnet-aot-compat — an installable skill for AI agents, published by dotnet/skills.

>-