Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps, post-mortem investigation with lldb/windbg/dotnet-dump analyze, profiling or tracing, or for .NET Framework processes.
SkillScore86Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/9/2026
What it changes
Passed 18 of 21 test cases with the skill, and 9 of 21 without it.
Without skill41%
With skill86%
Checks it passed that the model alone missed
States that dump analysis is out of scope.
Refuses to write C# code for dump collection.
States that configuration must be environment-only.
and 8 more in the full report
10 fixed9 passed either way3 still failing0 broke
Pass-rate lift
+45 pp
Tokens
-1%
Agent turns
0%
Response time
-14%
Model gemini-3.6-flashMeasured 8/9/2026v119 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
We are setting up environment variables for automatic crash dumps to /var/dumps/dotnet. What step must be performed on /var/dumps/dotnet before launching the application?
What was checked, without and with the skill
Checked
Without skill
With skill
Directs verifying write permissions on /var/dumps/dotnet before launching the application.
Missed
Passed
case-12 · gemini-3.6-flash · 8/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md90 lines4 files
.NET Crash Dump Collection
This skill configures and collects crash dumps for modern .NET applications (CoreCLR and NativeAOT) on Linux, macOS, and Windows — including containers.
Stop Signals
🚨 Read before starting any workflow.
Stop after dumps are enabled or collected. Do not open, analyze, or triage dump files.
If the user already has a dump file, this skill does not cover analysis. Let them know analysis is out of scope.
Do not install analysis tools (dotnet-dump analyze, windbg). Only install collection tools (dotnet-dump collect). Using lldb for on-demand dump capture on macOS is allowed — it ships with Xcode command-line tools and is not being used for analysis.
Do not trace root cause of crashes. Report the dump file location and move on.
Do not modify application code. Configuration is environment-only (env vars, OS settings, container specs).
Step 1 — Identify the Scenario
Ask or determine:
Goal: Enable automatic crash dumps, or capture a dump from a running process right now?
Platform: Linux, macOS, or Windows? Running in a container (Docker/Kubernetes)?
Runtime: CoreCLR or NativeAOT?
Detecting CoreCLR vs NativeAOT
From a binary file (Linux/macOS):
# CoreCLR — has IL metadata / managed entry point
strings <binary> | grep -q "CorExeMain" && echo "CoreCLR"
# NativeAOT — has Redhawk runtime symbols
strings <binary> | grep -q "Rhp" && echo "NativeAOT"
# On macOS/Linux, also try:
nm <binary> 2>/dev/null | grep -qi "Rhp" && echo "NativeAOT"
From a binary file (Windows):
# CoreCLR — has a CLI header (IL entry point)
dumpbin /clrheader <binary.exe> | Select-String "CLI Header" -Quiet
Optimizes hot-path scalar loops in .NET 8+ with cross-platform Vector128/Vector256/Vector512 SIMD intrinsics, or replaces manual math loops with single TensorPrimitives API calls. Covers byte-range validation, character counting, bulk bitwise ops, cross-type conversion, fused multi-array computations, and float/double math operations.