agentleFS
Sign inStart free
dprakash2101dprakash2101/dotnet-production-agent-skills/skills/performance-diagnostics-dotnet/SKILL.md

performance-diagnostics-dotnet

Skill4 starsChanged 51 days agoMITView on GitHub

Use when investigating or improving measured .NET performance, allocations, garbage collection, thread-pool starvation, latency, or throughput.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use existing profiling tools and representative workloads.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Performance Diagnostics Dotnet

Establish the workload, baseline, target, environment and measurement method before changing code. Separate CPU, allocation/GC, contention, thread-pool, database and external dependency hypotheses using evidence.

Use existing profiling tools and representative workloads. Choose bounded diagnostic collection appropriate to the environment; production dump capture may include sensitive data and requires appropriate authorization. Compare like-for-like measurements and account for warmup, variability and collection overhead.

Change the smallest proven bottleneck while preserving behavior. Verify correctness and measure again. Avoid speculative micro-optimizations, premature pooling, or adding complexity unsupported by measured benefit. Report measurements, environment and residual uncertainty.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free