[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EKJK5QMQT6DBP15HGCMCSX":3,"skill-same:01M7EKJK5QMQT6DBP15HGCMCSX":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M7EKJK5QMQT6DBP15HGCMCSX","eval-performance",null,"'Guide for diagnosing and improving MSBuild project evaluation performance. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin\u002Fobj), deep impor","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcloud\u002Feval-performance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: eval-performance\ndescription: \"'Guide for diagnosing and improving MSBuild project evaluation performance. USE FOR: builds slow before any compilation starts, high evaluation time in binlog analysis, expensive glob patterns walking large directories (node_modules, .git, bin\u002Fobj), deep impor\"\ncategory: cloud\nversion: 1.0.0\ndisable-model-invocation: false\nrisk: low\nsource:\n  repository: \"microsoft\u002Fskills\"\n  commit: \"8f3b1a2c\"\n  path: \"plugins\u002Fdotnet-msbuild\u002Fskills\u002Feval-performance\u002FSKILL.md\"\n  license: \"MIT\"\n  imported_at: \"2026-09-20\"\n---\n# Diagnosing MSBuild Evaluation Performance\n\nEvaluation is the work MSBuild does *before* any target runs — reading project\nfiles, processing imports, expanding globs. This skill helps you **find and\nconfirm** evaluation bottlenecks. Measure first; recommend a change only when a\nmeasurement proves it is warranted.\n\n## Confirm the problem before changing anything\n\nEngage only when evaluation is *measurably* the bottleneck. Do NOT act when:\n\n- **The slowness is during compilation or target execution, not evaluation.**\n  That is not an evaluation problem — use `build-perf-diagnostics` instead.\n- **The complaint is \"rebuilds too much\" \u002F incremental build.** Use\n  `incremental-build` instead.\n- **You have no measurement.** If no binlog or timing summary shows evaluation\n  is slow, gather one first (see below). Do not guess from reading project files.\n- **A pattern below appears but evaluation is already fast.** Broad globs, deep\n  imports, or `EnableDefaultItems` are only worth flagging when the numbers show\n  they cost real time. A project that evaluates quickly needs no change.\n\nWhen a pattern is present but unmeasured, **report it as an observation and let\nthe user decide** — do not rewrite working configuration to match a \"best\npractice\" without evidence it costs measurable evaluation time. Prefer the\nsmallest, most targeted change; never disable SDK defaults as a first move.\n\n## MSBuild Evaluation Phases\n\nFor a comprehensive overview of MSBuild's evaluation and execution model, see [Build process overview](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview).\n\n1. **Initial properties**: environment variables, global properties, reserved properties\n2. **Imports and property evaluation**: process `\u003CImport>`, evaluate `\u003CPropertyGroup>` top-to-bottom\n3. **Item definition evaluation**: `\u003CItemDefinitionGroup>` metadata defaults\n4. **Item evaluation**: `\u003CItemGroup>` with `Include`, `Remove`, `Update`, glob expansion\n5. **UsingTask evaluation**: register custom tasks\n\nKey insight: evaluation happens BEFORE any targets run. Slow evaluation = slow build start even when nothing needs compiling.\n\n## Diagnosing Evaluation Performance\n\n### Primary: binlog MCP (preferred)\n\nUse the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the `binlog` MCP namespace) to analyze evaluation performance:\n\n1. Use the evaluations tool to list all evaluations and their durations\n2. Use evaluation_global_properties to check for multiple evaluations with differing global properties\n3. Use evaluation_properties to inspect evaluated properties for a specific project+TFM\n4. Use imports tool to analyze the import chain depth and structure\n5. Use properties tool to check for expensive property function evaluations\n\n### Fallback: text-log replay and preprocessing (when MCP is unavailable)\n\n### Using binlog\n\n1. Replay the binlog: `dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log`\n2. Search for evaluation events: `grep -i 'Evaluation started\\|Evaluation finished' full.log`\n3. Multiple evaluations for the same project = overbuilding\n4. Look for \"Project evaluation started\u002Ffinished\" messages and their timestamps\n\n### Using \u002Fpp (preprocess)\n\n- `dotnet msbuild -pp:full.xml MyProject.csproj`\n- Shows the fully expanded project with ALL imports inlined\n- Use to understand: what's imported, import depth, total content volume\n- Large preprocessed output (>10K lines) = heavy evaluation\n\n### Using \u002Fclp:PerformanceSummary\n\n- Add to build command for timing breakdown\n- Shows evaluation time separately from target\u002Ftask execution\n\n## Expensive Glob Patterns\n\nOnly pursue these remedies once a measurement shows item evaluation is slow and\nthe globs are the cause; a custom glob that isn't walking large trees is fine.\n\n- Globs like `**\u002F*.cs` walk the entire directory tree\n- Default SDK globs are optimized, but custom globs may not be\n- Problem: globbing over `node_modules\u002F`, `.git\u002F`, `bin\u002F`, `obj\u002F` — millions of files\n- Remedy: use `\u003CDefaultItemExcludes>` to exclude large directories\n- Remedy: be specific with glob paths: `src\u002F**\u002F*.cs` instead of `**\u002F*.cs`\n- Remedy: use `\u003CEnableDefaultItems>false\u003C\u002FEnableDefaultItems>` only as a last resort (loses SDK defaults) — prefer the two options above first\n- Check: grep for Compile items in the diagnostic log → if Compile items include unexpected files, globs are too broad\n\n## Import Chain Analysis\n\n- Deep import chains (>20 levels) slow evaluation\n- Each import: file I\u002FO + parse + evaluate\n- Common causes: NuGet packages adding .props\u002F.targets, framework SDK imports, Directory.Build chains\n- Diagnosis: `\u002Fpp` output → search for `\u003C!-- Importing` comments to see import tree\n- Remedy (only if the chain is measurably costly): reduce transitive package imports where possible, consolidate imports\n\n## Multiple Evaluations\n\n- A project evaluated multiple times = wasted work\n- Common causes: referenced from multiple other projects with different global properties\n- Each unique set of global properties = separate evaluation\n- Diagnosis: `grep 'Evaluation started.*ProjectName' full.log` → if count > 1, check for differing global properties\n- Fix: normalize global properties, use graph build (`\u002Fgraph`)\n\n## TreatAsLocalProperty\n\n- Prevents property values from flowing to child projects via MSBuild task\n- Overuse: declaring many TreatAsLocalProperty entries adds evaluation overhead\n- Correct use: only when you genuinely need to override an inherited property\n\n## Property Function Cost\n\n- Property functions execute during evaluation\n- Most are cheap (string operations)\n- Expensive: `$([System.IO.File]::ReadAllText(...))` during evaluation — reads file on every evaluation\n- Expensive: network calls, heavy computation\n- Rule: property functions should be fast and side-effect-free\n\n## Optimization Checklist\n\n- [ ] Check preprocessed output size: `dotnet msbuild -pp:full.xml`\n- [ ] Verify evaluation count: should be 1 per project per TFM\n- [ ] Exclude large directories from globs\n- [ ] Avoid file I\u002FO in property functions during evaluation\n- [ ] Minimize import depth\n- [ ] Use graph build to reduce redundant evaluations\n- [ ] Check for unnecessary UsingTask declarations\n","# Diagnosing MSBuild Evaluation Performance\n\nEvaluation is the work MSBuild does *before* any target runs — reading project\nfiles, processing imports, expanding globs. This skill helps you **find and\nconfirm** evaluation bottlenecks. Measure first; recommend a change only when a\nmeasurement proves it is warranted.\n\n## Confirm the problem before changing anything\n\nEngage only when evaluation is *measurably* the bottleneck. Do NOT act when:\n\n- **The slowness is during compilation or target execution, not evaluation.**\n  That is not an evaluation problem — use `build-perf-diagnostics` instead.\n- **The complaint is \"rebuilds too much\" \u002F incremental build.** Use\n  `incremental-build` instead.\n- **You have no measurement.** If no binlog or timing summary shows evaluation\n  is slow, gather one first (see below). Do not guess from reading project files.\n- **A pattern below appears but evaluation is already fast.** Broad globs, deep\n  imports, or `EnableDefaultItems` are only worth flagging when the numbers show\n  they cost real time. A project that evaluates quickly needs no change.\n\nWhen a pattern is present but unmeasured, **report it as an observation and let\nthe user decide** — do not rewrite working configuration to match a \"best\npractice\" without evidence it costs measurable evaluation time. Prefer the\nsmallest, most targeted change; never disable SDK defaults as a first move.\n\n## MSBuild Evaluation Phases\n\nFor a comprehensive overview of MSBuild's evaluation and execution model, see [Build process overview](https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Fvisualstudio\u002Fmsbuild\u002Fbuild-process-overview).\n\n1. **Initial properties**: environment variables, global properties, reserved properties\n2. **Imports and property evaluation**: process `\u003CImport>`, evaluate `\u003CPropertyGroup>` top-to-bottom\n3. **Item definition evaluation**: `\u003CItemDefinitionGroup>` metadata defaults\n4. **Item evaluation**: `\u003CItemGroup>` with `Include`, `Remove`, `Update`, glob expansion\n5. **UsingTask evaluation**: register custom tasks\n\nKey insight: evaluation happens BEFORE any targets run. Slow evaluation = slow build start even when nothing needs compiling.\n\n## Diagnosing Evaluation Performance\n\n### Primary: binlog MCP (preferred)\n\nUse the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the `binlog` MCP namespace) to analyze evaluation performance:\n\n1. Use the evaluations tool to list all evaluations and their durations\n2. Use evaluation_global_properties to check for multiple evaluations with differing global properties\n3. Use evaluation_properties to inspect evaluated properties for a specific project+TFM\n4. Use imports tool to analyze the import chain depth and structure\n5. Use properties tool to check for expensive property function evaluations\n\n### Fallback: text-log replay and preprocessing (when MCP is unavailable)\n\n### Using binlog\n\n1. Replay the binlog: `dotnet msbuild build.binlog -noconlog -fl -flp:v=diag;logfile=full.log`\n2. Search for evaluation events: `grep -i 'Evaluation started\\|Evaluation finished' full.log`\n3. Multiple evaluations for the same project = overbuilding\n4. Look for \"Project evaluation started\u002Ffinished\" messages and their timestamps\n\n### Using \u002Fpp (preprocess)\n\n- `dotnet msbuild -pp:full.xml MyProject.csproj`\n- Shows the fully expanded project with ALL imports inlined\n- Use to understand: what's imported, import depth, total content volume\n- Large preprocessed output (>10K lines) = heavy evaluation\n\n### Using \u002Fclp:PerformanceSummary\n\n- Add to build command for timing breakdown\n- Shows evaluation time separately from target\u002Ftask execution\n\n## Expensive Glob Patterns\n\nOnly pursue these remedies once a measurement shows item evaluation is slow and\nthe globs are the cause; a custom glob that isn't walking large trees is fine.\n\n- Globs like `**\u002F*.cs` walk the entire directory tree\n- Default SDK globs are optimized, but custom globs may not be\n- Problem: globbing over `node_modules\u002F`, `.git\u002F`, `bin\u002F`, `obj\u002F` — millions of files\n- Remedy: use `\u003CDefaultItemExcludes>` to exclude large directories\n- Remedy: be specific with glob paths: `src\u002F**\u002F*.cs` instead of `**\u002F*.cs`\n- Remedy: use `\u003CEnableDefaultItems>false\u003C\u002FEnableDefaultItems>` only as a last resort (loses SDK defaults) — prefer the two options above first\n- Check: grep for Compile items in the diagnostic log → if Compile items include unexpected files, globs are too broad\n\n## Import Chain Analysis\n\n- Deep import chains (>20 levels) slow evaluation\n- Each import: file I\u002FO + parse + evaluate\n- Common causes: NuGet packages adding .props\u002F.targets, framework SDK imports, Directory.Build chains\n- Diagnosis: `\u002Fpp` output → search for `\u003C!-- Importing` comments to see import tree\n- Remedy (only if the chain is measurably costly): reduce transitive package imports where possible, consolidate imports\n\n## Multiple Evaluations\n\n- A project evaluated multiple times = wasted work\n- Common causes: referenced from multiple other projects with different global properties\n- Each unique set of global properties = separate evaluation\n- Diagnosis: `grep 'Evaluation started.*ProjectName' full.log` → if count > 1, check for differing global properties\n- Fix: normalize global properties, use graph build (`\u002Fgraph`)\n\n## TreatAsLocalProperty\n\n- Prevents property values from flowing to child projects via MSBuild task\n- Overuse: declaring many TreatAsLocalProperty entries adds evaluation overhead\n- Correct use: only when you genuinely need to override an inherited property\n\n## Property Function Cost\n\n- Property functions execute during evaluation\n- Most are cheap (string operations)\n- Expensive: `$([System.IO.File]::ReadAllText(...))` during evaluation — reads file on every evaluation\n- Expensive: network calls, heavy computation\n- Rule: property functions should be fast and side-effect-free\n\n## Optimization Checklist\n\n- [ ] Check preprocessed output size: `dotnet msbuild -pp:full.xml`\n- [ ] Verify evaluation count: should be 1 per project per TFM\n- [ ] Exclude large directories from globs\n- [ ] Avoid file I\u002FO in property functions during evaluation\n- [ ] Minimize import depth\n- [ ] Use graph build to reduce redundant evaluations\n- [ ] Check for unnecessary UsingTask declarations\n",{"name":5,"risk":24,"source":25,"version":30,"category":31,"description":7,"disable-model-invocation":20},"low",{"path":26,"commit":27,"license":15,"repository":28,"imported_at":29},"plugins\u002Fdotnet-msbuild\u002Fskills\u002Feval-performance\u002FSKILL.md","8f3b1a2c","microsoft\u002Fskills","2026-09-20","1.0.0","cloud","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcloud\u002Feval-performance","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill eval-performance",{"tool":44,"command":45},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill eval-performance",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill eval-performance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcloud\u002Feval-performance\u002FSKILL.md",true,[],[53,61,68,75,82,89],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":60},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":60},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":60},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":60},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":60},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":60},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]