agentleFS
Sign inStart free
nockawanockawa/NockMon/.claude/skills/profile/SKILL.md

profile

Skill1 starsChanged 17 days agoMITView on GitHub

Profile the steady state of the NockMon WinUI app with dotTrace sampling (CPU time), generate XML reports, and analyze hot spots per pipeline stage

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use apply, coverage and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • proficientlyjobsSkill

    apply

    Fill out a job application on Greenhouse, Lever, or Workday

    Also in 3 projects that use this

  • PydanticSkill

    coverage

    Fetch coverage diff from Codecov for the current branch or a specific PR. Shows uncovered lines, patch coverage, and overall coverage change.

    Also in 3 projects that use this

  • dragonflydbSkill

    benchmark

    Benchmark Dragonfly (and compare against Valkey/Redis) on local or remote cloud instances, then produce a performance + memory report with charts and a raw-data appendix. Use this whenever the user runs /benchmark, or asks to benchmark / load-test / measure throughput, QPS, latency, or memory efficiency of Dragonfly or another Redis-compatible server, to compare Dragonfly vs Valkey or Redis, or to generate a benchmark report. Trigger it even when the user just describes the goal ("see how fast Dragonfly is on this box", "compare memory per key vs Valkey") without saying the word "benchmark".

    Also in 3 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    docs

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

dotTrace profiling (NockMon)

Adapted from the Typhon /profile skill. Steady-state CPU profiling of a GUI app that is idle most of the time.

Tools

  • dottrace: global tool (JetBrains.dotTrace.GlobalTools), needs DOTNET_ROLL_FORWARD=LatestMajor (set by the script).
  • Reporter.exe: %USERPROFILE%\.nuget\packages\jetbrains.dottrace.commandlinetools.windows-x64\<latest>\tools\Reporter.exe (found automatically).
  • tools/profiling/profile.sh <name> [warmup=15] [collect=30] [measure=ThreadTime]: builds Release with -p:ProfilingBuild=true (optimized, honors NOCKMON_SKIP_ELEVATION=1 since profilers run non-elevated), launches under dottrace with collection off, starts collecting after the warm-up via ##dotTrace["start"] on stdin, snapshots, closes the app, then writes tools/profiling/out/<name>-report.xml (app frames, app-pattern.xml) and <name>-all.xml (all frames).
  • tools/profiling/analyze_profile.py <report.xml> [--top N] [--filter X] [--callers M] [--compare other.xml] [--json]: self/inclusive hot spots and a pipeline breakdown (probe, rates, history, chart draw, table refresh, status).
  • tools/profiling/thread-cpu.ps1 -ProcessId <pid> [-Seconds 30]: ground truth per-thread CPU (ms/s) of a running instance.

Workflow

  1. bash tools/profiling/profile.sh <name> 60 30 ThreadCycleTime (60 s warm-up: tiered JIT keeps recompiling for ~20–40 s; the first 20 s cost ~3× steady state).
  2. python tools/profiling/analyze_profile.py tools/profiling/out/<name>-all.xml --top 25, then the -report.xml for the breakdown.
  3. Cross-check totals against process CPU (thread-cpu.ps1, or TotalProcessorTime delta) before drawing conclusions.
  4. Comparison: analyze_profile.py out/<baseline>-report.xml --compare out/<name>-report.xml.

Pitfalls (measured on this project)

  • Use ThreadCycleTime. ThreadTime advances in 15.6 ms scheduler quanta: small functions read 0 and random ones read 16/47 ms.
  • dotTrace only sees threads with managed frames. WinUI composition/render and D3D threads are invisible; compare its total with the process CPU. Native attribution needs ETW (WPR/WPA, admin).
  • IApplicationStaticsMethods.Start self time = UI thread native work (XAML layout, render, message pump) under Application.Start.
  • WaitHandle.WaitOne self cycles are wait/wake transitions of the sampler thread, not busy time.
  • Sampling misattributes memory stalls and under-credits bursty parallel work: confirm candidates with Stopwatch A/B.
  • Process.Threads[].StartAddress always resolves to ntdll (RtlUserThreadStart): no module attribution that way.

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