SkillVaultskills Browse all 1,000+ skills

Performance · Version 1.3.0 · Reviewed 2026-08-02

.NET Performance Advisor

Locate and remove the dominant bottleneck in allocation profiling and thread-pool diagnosis with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Analyzes .NET allocation profiles, async usage, thread-pool starvation, database access, JIT behavior, and hot-path runtime costs.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools, with a raw SKILL.md fallback for every other compatible IDE or agent.

See the complete graphical installation and usage guide

What this skill helps you do

  • Allocation profiling
  • Thread-pool diagnosis
  • Async performance

How .NET Performance Advisor works

You provide

Baseline measurements, workload shape, and the target

It inspects

Dominant cost mechanism behind allocation profiling

It decides

A thread-pool diagnosis change ranked by impact and risk

You verify

Re-measure under representative load with guardrails

What it checks first

.NET Performance Advisor analyzes .NET allocation profiles, async usage, thread-pool starvation, database access, JIT behavior, and hot-path runtime costs. Use it when the work involves Allocation profiling, Thread-pool diagnosis, Async performance.

  1. A measured baseline and the user-visible target, since optimization without both is guesswork.
  2. Whether the cost is CPU, memory, I/O wait, or lock contention — they have opposite fixes.
  3. The p99 path and how many round trips it contains.
  4. Whether the bottleneck moves after a change, which determines if the gain is real.

Failure modes it recognizes

  • Optimizing a component that is not on the critical path, producing no end-to-end change.
  • A garbage-collection pause misread as slow application code.
  • Memory pressure causing swapping, which presents as unpredictable latency spikes.
  • A micro-optimization that improves the benchmark and regresses the real workload.

Answers it will reject

  • Tuning configuration flags before profiling where time is actually spent.
  • Measuring in a warmed-up loop that does not resemble production access patterns.
  • Reporting an improvement without the guardrail metric that would show a shifted bottleneck.

Decision rules it applies

  • Profile before changing anything, and attribute cost to a specific phase.
  • Optimize the dominant cost first; everything else is rounding.
  • Re-measure under representative load and keep a guardrail metric.

Evidence it asks for

  • Capture a profile during the real workload rather than a synthetic benchmark.
  • Record allocation rate and pause time alongside latency.
  • Compare before and after at the same percentile, not at the mean.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to allocation profiling.
  2. Trace concrete failure or abuse paths for thread-pool diagnosis; do not report checklist items without a mechanism.
  3. Prioritize async performance findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Allocation profiling assessment
  • Thread-pool diagnosis decision and action plan
  • Async performance verification checklist

Evidence requirements

  • Profiles, traces, timings, resource metrics, and workload shape
  • Baseline and target percentile
  • Environment, concurrency, and payload details

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Our ASP.NET API latency rises under moderate load while CPU stays below forty percent.

Expected output

Thread-pool workers are blocked on synchronous database calls, so requests wait for workers while CPU remains idle. Convert the full call chain to async and verify the connection pool is not the next limit...

Boundaries and compatibility

Ideal for

  • Allocation profiling: produce a decision or artifact grounded in supplied evidence.
  • Thread-pool diagnosis: produce a decision or artifact grounded in supplied evidence.
  • Async performance: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Optimizing without a baseline
  • Using averages where tail latency determines experience

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.