{"slug":"dotnet-asynkron-profiler","title":"dotnet-asynkron-profiler","summary":"Use the open-source free `Asynkron.Profiler` dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-09-27T21:00:29.380107Z","repo":{"url":"https://github.com/Postpartum-genushyacinthus29/dotnet-skills","stars":12,"forks":1,"license":"MIT","updatedAt":"2026-09-27T19:34:14Z"},"bodyHtml":"
\n

name: dotnet-asynkron-profiler\nversion: \"1.0.0\"\ncategory: \"Metrics\"\ndescription: \"Use the open-source free Asynkron.Profiler dotnet tool for CLI-first CPU, allocation, exception, contention, and heap profiling of .NET commands or existing trace artifacts.\"\ncompatibility: \"Requires the asynkron-profiler dotnet tool plus dotnet-trace and dotnet-gcdump; upstream guidance currently targets .NET SDK 10.x.\"

\n

Asynkron.Profiler

\n

Trigger On

\n\n

Workflow

\n
    \n
  1. Decide whether the task is a new profile capture or rendering an existing trace artifact.
    2. \n
  2. Prefer built Release output over dotnet run so the trace represents the target app rather than restore/build noise.
    3. \n
  3. Install and verify all three tools before assuming the profiler is usable:\n\n
    4. \n
  4. Choose exactly one primary mode first:\n\n
    5. \n
  5. Use --input <path> when the trace already exists and the task is about rendering or narrowing the report, not recollecting data.
    6. \n
  6. Refine the output only after the baseline run:\n\n
    7. \n
  7. Treat profile-output/ as the stable output folder for review artifacts and reruns.
    8. \n
  8. If the task needs process attach, counters, or raw official diagnostics flows rather than this CLI frontend, hand off to dotnet-profiling.
    9. \n
\n

Architecture

\n
flowchart LR\n  A[\"Profiling task\"] --> B{\"New run or existing artifact?\"}\n  B -->|New run| C[\"Build target in Release\"]\n  C --> D[\"Run `asynkron-profiler --mode -- <command|csproj|sln>`\"]\n  D --> E[\"Collect via `dotnet-trace` or `dotnet-gcdump`\"]\n  E --> F[\"Write reports to `profile-output/`\"]\n  B -->|Existing artifact| G[\"Run `asynkron-profiler --input <path> [--mode]`\"]\n  G --> F\n  F --> H[\"Refine output with `--root`, `--filter`, and call tree flags\"]\n
\n

Install

\n\n
dotnet tool install -g asynkron-profiler --prerelease\n
\n\n
dotnet tool install -g dotnet-trace\ndotnet tool install -g dotnet-gcdump\n
\n\n
asynkron-profiler --help\ndotnet-trace --version\ndotnet-gcdump --version\n
\n

Practical Usage

\n

Capture a new profile

\n
dotnet build -c Release\nasynkron-profiler --cpu -- ./bin/Release/<tfm>/MyApp\n
\n

Framework-dependent apps can run through dotnet:

\n
asynkron-profiler --memory -- dotnet ./bin/Release/<tfm>/MyApp.dll\n
\n

Project and solution paths are also valid when the tool should build and run for you:

\n
asynkron-profiler --contention -- ./MyApp.csproj\nasynkron-profiler --exception -- ./MySolution.sln\n
\n

Render an existing trace

\n
asynkron-profiler --input ./profile-output/app.nettrace --cpu\nasynkron-profiler --input ./profile-output/app.etlx --memory\nasynkron-profiler --input ./profile-output/app.gcdump --heap\n
\n

Manual collection with the official tools still fits when the trace must be captured separately:

\n
dotnet-trace collect --output ./profile-output/app.nettrace -- dotnet run MyProject.sln\nasynkron-profiler --input ./profile-output/app.nettrace --cpu\n
\n

Option Patterns

\n\n

Constraints

\n\n

Deliver

\n\n

Validate

\n\n

References

\n\n","files":[{"path":"references/commands.md","sizeBytes":3035,"isText":true},{"path":"references/examples.md","sizeBytes":2803,"isText":true},{"path":"references/overview.md","sizeBytes":3404,"isText":true},{"path":"SKILL.md","sizeBytes":6382,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-27T21:01:46.530676Z","sha256":"D052F4CC48B2F90A8E193FDD8C900A0E085F956AD9E45DC7A61B4E8029AE780A","sizeBytes":6337},"review":null,"source":{"repositoryUrl":"https://github.com/Postpartum-genushyacinthus29/dotnet-skills","path":"skills/dotnet-asynkron-profiler","license":"MIT","commit":"bfa4ebd86f6bd674800f209ebf72ca770c2f026b","subtreeSha":"3F7FCBDA83303BEB4A1866241565597B9855409C37B89121C3019AFCA9508163","lastSyncedAt":"2026-09-27T21:00:28.368219Z"},"reviewedAt":"2026-09-27T21:09:46.579743Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/Postpartum-genushyacinthus29/dotnet-skills/tree/main/skills/dotnet-asynkron-profiler"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install postpartum-genushyacinthus29-dotnet-skills@llmmart"},{"target":"git","command":"git clone https://github.com/Postpartum-genushyacinthus29/dotnet-skills.git"}]}