dotnet-profiling

Diagnose .NET performance issues using dotnet-counters, dotnet-trace, and dotnet-dump.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-profiling
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-profiling
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-profiling
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-profiling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers pinpoint and resolve performance bottlenecks in .NET applications by providing tools and guidance for deep-dive diagnostics.

Core Features & Use Cases

  • Real-time Monitoring: Use dotnet-counters to observe key runtime metrics like CPU, memory, and GC activity.
  • Event Tracing: Employ dotnet-trace to capture detailed execution traces, enabling flame graph analysis for CPU hot paths and allocation tracking.
  • Memory Dump Analysis: Utilize dotnet-dump to capture and analyze memory dumps for investigating leaks and heap issues.
  • Use Case: Your .NET application is experiencing high CPU usage under load. You can use dotnet-trace to generate a CPU sampling profile, convert it to a flame graph, and identify the specific methods consuming the most CPU time.

Quick Start

Use the dotnet-profiling skill to collect a 30-second CPU trace for the process with ID 12345.

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 diagnose .NET high CPU usage, use `dotnet-trace` to capture a CPU sampling profile. Converting this trace into a flame graph identifies the specific methods consuming the most CPU time under load.

What is the best way to find memory leaks in .NET?▼

The best way to find .NET memory leaks is using `dotnet-dump` to capture and analyze memory dumps. This isolates heap issues and memory leaks by inspecting the allocated objects directly.

Can I monitor .NET GC pressure and runtime metrics in real-time?▼

You can monitor real-time .NET runtime metrics, including GC pressure, memory, and CPU activity, by observing key counters with `dotnet-counters` during application execution.

How does event tracing work for profiling .NET performance issues?▼

Event tracing for .NET profiling works by using `dotnet-trace` to capture detailed execution traces. Analyzing these traces enables allocation tracking and flame graph generation for CPU hot paths.

When should I use dotnet-dump instead of dotnet-trace?▼

Use `dotnet-dump` instead of `dotnet-trace` when investigating memory leaks and heap issues. `dotnet-trace` is better suited for capturing execution traces and analyzing CPU-bound performance problems.

Do I need special dependencies to analyze .NET flame graphs and memory dumps?▼

No special dependencies are required to analyze .NET flame graphs and memory dumps. The Skill utilizes built-in .NET diagnostic tools directly to interpret profiling data for optimization.