dotnet-profiling

Diagnose .NET application performance using dotnet-trace, dotnet-counters, and dotnet-gcdump.

466|35|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-profiling-managedcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-profiling
Source: https://github.com/managedcode/dotnet-skills/tree/main/skills/dotnet-profiling
Command: npx skills add https://github.com/managedcode/dotnet-skills --skill dotnet-profiling-managedcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers diagnose and resolve performance bottlenecks, memory leaks, and runtime issues in .NET applications using official command-line diagnostic tools.

Core Features & Use Cases

  • CPU Profiling: Identify CPU hotspots and slow methods.
  • Memory Analysis: Investigate memory leaks and heap composition.
  • Runtime Diagnostics: Monitor live counters, GC behavior, and exception rates.
  • Use Case: When a .NET application is experiencing high CPU usage under load, this Skill can collect a CPU trace to pinpoint the exact methods consuming the most resources, enabling targeted optimization.

Quick Start

Use the dotnet-profiling skill to collect a CPU trace for the running .NET application.

Frequently Asked Questions about dotnet-profiling

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

FAQPage Schema
How do I diagnose high CPU usage in a .NET application?

To perform .NET memory leak investigation, this Skill uses dotnet-gcdump to analyze heap composition and garbage collection behavior. It helps you identify memory leaks and understand what objects are retaining memory during runtime.

What's the best way to investigate a memory leak in a .NET application?

.NET memory leak investigation is best handled by using dotnet-gcdump to analyze heap composition and garbage collection behavior. This Skill helps you identify memory leaks and understand what objects are retaining memory during runtime.

Do I need a running .NET process to collect performance traces?

Yes, you need a running .NET application process to inspect. This Skill requires an active target process to attach diagnostic CLI tools like dotnet-trace and dotnet-counters for collecting CPU and memory metrics.

How do I trace garbage collection pressure and exception rates in .NET?

To trace garbage collection pressure and exception rates in .NET, you can use dotnet-counters to monitor live runtime diagnostics. This Skill tracks GC behavior, contention, and exception rates in real-time without GUI dependencies.