Asynkron Profiler

What it does

When your agent uses it

• : Asynkron.Profiler setup
• Automation-friendly profiling output
• Heap investigation
• : unrelated stacks

Example prompts

• “/asynkron-profiler”

Requirements

• Compatibility (from SKILL.md): Requires the `asynkron-profiler` dotnet tool plus `dotnet-trace` and `dotnet-gcdump`; upstream guidance currently targets .NET SDK 10.x.

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

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

What it can do on your machine

Read from SKILL.md and the folder at commit 535dd55. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • dotnet

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Requires the `asynkron-profiler` dotnet tool plus `dotnet-trace` and `dotnet-gcdump`; upstream guidance currently targets .NET SDK 10.x.

  From compatibility in the SKILL.md frontmatter.

Context cost

Asynkron Profiler loads about 1.7k tokens when it runs, and up to ~4k if it reads all its reference files. Until then it costs about 141 tokens; SKILL.md has 588 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~141

When it runs · the whole SKILL.md, loaded when a task matches

~1.7k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from managedcode/dotnet-skills at commit 535dd55, republished under its MIT licence (© managedcode). 588 words, ~1,674 tokens.

name

asynkron-profiler

description

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. USE FOR: Asynkron.Profiler setup; automation-friendly profiling output; CPU, allocation, exception, contention, and heap investigation. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.

compatibility

Requires the `asynkron-profiler` dotnet tool plus `dotnet-trace` and `dotnet-gcdump`; upstream guidance currently targets .NET SDK 10.x.

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

dotnet tool install -g asynkron-profiler --prerelease

dotnet tool install -g dotnet-trace
dotnet tool install -g dotnet-gcdump

asynkron-profiler --help
dotnet-trace --version
dotnet-gcdump --version

dotnet build -c Release
asynkron-profiler --cpu -- ./bin/Release/<tfm>/MyApp

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

asynkron-profiler --contention -- ./MyApp.csproj
asynkron-profiler --exception -- ./MySolution.sln

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

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

© managedcode, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in catalog/Tools/Asynkron-Profiler/skills/asynkron-profiler of managedcode/dotnet-skills.

• SKILL.md
• manifest.json
• references/commands.md
• references/examples.md
• references/overview.md

Open the folder on GitHubat commit 535dd55