Eval Performance skill: what it does and how to install it
Diagnoses MSBuild project evaluation bottlenecks using binlogs, preprocessing and timing data, then targets costly globs, imports and repeated evaluations.
Summary generated from the skill's documentation.
Install
$ npx skills add dotnet/skills --skill eval-performanceRun it in a terminal. If your agent is already running, start a new session so it picks the skill up.
About this skill
What it does. Uses binlog analysis first to measure MSBuild evaluation time, count project evaluations, inspect global properties, import depth and property functions, and falls back to diagnostic logs, /pp preprocessing and performance summaries. It connects measured costs to targeted changes such as narrower globs, excluded directories, fewer imports or graph builds, while disabling SDK defaults only as a last resort.
When to use it. Use it when a build is slow before compilation and evaluation is shown to be the bottleneck. It does not cover compilation or target execution slowness, incremental-build problems or non-MSBuild systems.
History
Repo stars
5.6kAbout +410 since 9 Jul 2026
Before 1 Oct 2026 the curve is estimated from public event data.
Stars are counted for the whole repository, which holds 43 skills.
Show as a table
| Date | Repo stars |
|---|---|
| 5 Oct 2026 | 5,557 |
| 4 Oct 2026 | 5,551 |
| 3 Oct 2026 | 5,543 |
| 2 Oct 2026 | 5,540 |
| 1 Oct 2026 | 5,531 |
| 24 Sept 2026 (estimated) | 5,519 |
| 17 Sept 2026 (estimated) | 5,494 |
| 10 Sept 2026 (estimated) | 5,419 |
| 3 Sept 2026 (estimated) | 5,258 |
| 27 Aug 2026 (estimated) | 5,233 |
| 20 Aug 2026 (estimated) | 5,221 |
| 13 Aug 2026 (estimated) | 5,221 |
| 6 Aug 2026 (estimated) | 5,171 |
| 30 Jul 2026 (estimated) | 5,159 |
| 23 Jul 2026 (estimated) | 5,159 |
| 16 Jul 2026 (estimated) | 5,147 |
| 9 Jul 2026 (estimated) | 5,147 |
Installs
2.6k
Tracking since . A chart appears once there are 7 days of data.
Installs via skills.sh
Similar skills
- Diagnosing SuperpowersWorks out why a superpowers session went wrong: repeated work, ignored plans or a skill that did not fire.
- Using Git WorktreesSets up an isolated workspace with git worktrees before feature work or plan execution begins.
- Diagnosing BugsRuns a diagnosis loop for hard bugs and performance regressions.