Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →managedcode/pvanalyze
Use `pvanalyze` to inspect existing .NET `.nettrace` files from the command line, including GC, JIT, CPU stacks, allocation, DATAS, events, exceptions, timeline, and call-tree analysis with JSON or SpeedScope. USE FOR: the user mentions pvanalyze, PerfView-style CLI trace analysis, or cross-platform .nettrace inspection; the task starts from an existing .nettrace file and needs. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the reposito
Passed 21 of 22 test cases with the skill, and 3 of 22 without it.
and 27 more in the full report
18 fixed3 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
We captured a trace `multi.nettrace` that contains events from multiple .NET processes running concurrently. We need to run GC statistics specifically for the process named `WorkerService` in JSON format. What option selects this process?
| Checked | Without skill | With skill |
|---|---|---|
| Uses `--process WorkerService` with `pvanalyze gcstats multi.nettrace` to filter by process. | Missed | Passed |
The instructions your model reads when the skill loads.
pvanalyze, PerfView-style CLI trace analysis, or cross-platform .nettrace inspection.nettrace file and needs readable terminal or JSON output.nettraceUse dotnet-trace-collect or profiling first when the task is mostly about collecting the trace. Use pvanalyze once a trace artifact exists or when the user wants the specific command surface.
pvanalyze info <trace.nettrace> first to verify the file opens and contains the expected processes.gcstats for GC count, heap size, pause, and GC timeline questionsalloc for allocation-by-type questionsdatas for Dynamic Adaptation To Application Sizes heap-count tuningjitstats for JIT compilation costcpustacks for top CPU methods, module grouping, namespace grouping, or SpeedScope exportcalltree for hot paths and caller/callee explorationevents for provider, event type, payload, PID, or TID filteringexceptions for thrown exception summaries and detailstimeline or snapshot when an agent needs time-bucketed context--format json when another tool or agent will consume the output.--from and --to only after the baseline command confirms the interesting time window.pvanalyze clean <trace-or-directory> when generated .pvanalyze.etlx cache files should be removed.pvanalyze as a cross-platform .nettrace analyzer and explicitly says --help plus the README are the intended agent context rather than a separate upstream SKILL.md or AGENTS.md.The upstream README documents two install paths:
# .NET 10+ one-shot execution path
test cases passed, vs 3 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.