Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Misleading ResolveProjectReferences Time — measured AI agent skill | DecimalAI

dotnet/resolve-project-references

NewSkillScoreMaintained

Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Activate when ResolveProjectReferences appears as the most expensive target and developers are trying to optimize it directly. Explains that the reported time includes wait time for dependent project builds and is misleading. Guides users to focus on task self-time instead. Do not activate for general build performance -- use build-perf-diagnostics instead.

by dotnet

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

decimalai skills pull dotnet-resolve-project-references

Get this skill — curl · raw file

curl -fsSL https://app.decimal.ai/s/dotnet-resolve-project-references/SKILL.md

Raw file: /s/dotnet-resolve-project-references/SKILL.md ↗ · machine-readable summary at /s/dotnet-resolve-project-references.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 11h ago

—-24% tokens0% turns91% of whole cases pass with skill (20/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	-8%	0%
case-06	✗→✓	▲ Improved	-17%	0%
case-07	✗→✓	▲ Improved	-2%	0%
case-08	✗→✓	▲ Improved	-15%	0%
case-13	✗→✓	▲ Improved	-14%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

dotnet / skills

plugins/dotnet-msbuild/skills/resolve-project-references/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

Skill contents

SKILL.md

Misleading ResolveProjectReferences Time

Prevent misguided optimization of ResolveProjectReferences by explaining that its reported time is wall-clock wait time, not CPU work.

When to Use

ResolveProjectReferences appears as the most expensive target in the Target Performance Summary
A developer is trying to optimize ResolveProjectReferences directly
Build performance analysis shows a single target consuming 50-80% of total build time

When Not to Use

General build performance optimization (use build-perf-diagnostics instead)
The bottleneck is clearly a different target (e.g., Csc, ResolveAssemblyReference)
The user has not yet captured a binlog or performance summary

Inputs

| Input | Required | Description | |-------|----------|-------------| | Build log or binlog | Yes | A diagnostic build log or binlog containing the Target Performance Summary |

Workflow

Step 1: Confirm the misleading symptom

Verify that ResolveProjectReferences appears as the top target in the Target Performance Summary. This is the misleading metric.

Step 2: Explain why it is misleading

The reported time includes waiting for dependent projects to build while the MSBuild node is yielded (see dotnet/msbuild#3135). During this wait, the node may be doing useful work on other projects. The target itself does very little work.

Step 3: Redirect to task self-time

Use the Task Performance Summary to identify the real bottleneck.

Primary: binlog MCP (preferred)

Use the binlog MCP server expensive_tasks tool to get task self-time rankings directly from the binlog.

Fallback: text-log replay (when MCP is unavailable)

bash
dotnet msbuild build.binlog -noconlog -fl "-flp:v=diag;logfile=full.log;performancesummary"
grep "Task Performance Summary" -A 50 full.log

Focus on self-time of actual tasks:

Csc: see build-perf-diagnostics skill (Section 2: Roslyn Analyzers)
ResolveAssemblyReference: see build-perf-diagnostics skill (Section 1: RAR)
Copy: see build-perf-diagnostics skill (Section 4: File I/O)
Serialization bottlenecks: see build-parallelism skill

Validation

] Task Performance Summary was used instead of Target Performance Summary
] ResolveProjectReferences was not set as the optimization target
] A concrete task (e.g., Csc, Copy, ResolveAssemblyReference) was identified as the true bottleneck

Want to see if dotnet/resolve-project-references would activate on your phrasing? Try it before you install — no LLM call, no signup.

Other measured skills in the registry, with their headline benchmark lift.