How do I install the Binlog Failure Analysis skill?

Run npx skillmds@latest add stanfish06/binlog-failure-analysis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Binlog Failure Analysis safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Binlog Failure Analysis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Binlog Failure Analysis free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Binlog Failure Analysis?

stanfish06 (@stanfish06) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Binlog Failure Analysis by stanfish06

Name: Binlog Failure Analysis
Rating: 4.2 (5 reviews)
Author: stanfish06

Binlog Failure Analysis

Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), non-MSBuild build systems.

stanfish06 Updated Sep 22, 2026

File contents

Analyzing MSBuild Failures with Binary Logs

This skill diagnoses MSBuild build failures from a .binlog file. The preferred path uses the binlog MCP server (Microsoft.AITools.BinlogMcp, exposed under the binlog MCP namespace) which is bundled with this plugin. If the MCP server is not available, fall back to the binlog replay workflow at the bottom.

Primary workflow — binlog MCP

The MCP server exposes structured tools for inspecting a .binlog without parsing text logs. Call them directly instead of replaying the binlog to a text file. Call tools/list for the MCP first if you are unsure which tools are available.

Important constraints:

The .binlog file is a binary format — do NOT try to cat, head, strings, or read it directly. Use only the MCP tools to query it.
The original source/project files might or might NOT be available on disk. Project files (.csproj, .props, .targets, App.config, etc.) - if you cannot locate them on disk, they can only be read from within the binlog via MCP tools (e.g., embedded/source file retrieval).
Synthesize findings as you go. Do not spend all available time investigating — once you have enough evidence, present your conclusions. A partial answer with clear reasoning is better than timing out mid-investigation.

Use the available MCP server tools to query the binary log for:

Build errors and warnings
MSBuild properties and their values
MSBuild items (PackageReference, ProjectReference, etc.)
Project evaluation data
Target execution details
File contents embedded in the binlog

Fallback workflow — text-log replay (when MCP is unavailable)

Use this only when the MCP server cannot be started (for example, on an older SDK or in an offline environment without access to the dotnet-tools NuGet feed).

Replay the binlog to text logs

dotnet msbuild build.binlog -noconlog \
  -fl  "-flp:v=diag;logfile=full.log;performancesummary" \
  -fl1 "-flp1:errorsonly;logfile=errors.log" \
  -fl2 "-flp2:warningsonly;logfile=warnings.log"

Quoting: the semicolons must be quoted in every shell — bash, zsh and PowerShell all treat a bare ; as a command separator, so an unquoted value is truncated to -flp:v=diag and the log is written to msbuild.log instead.

Search the text logs

cat errors.log
grep -n -B2 -A2 "CS0246" full.log
grep -i "CoreCompile.*FAILED\|Build FAILED\|error MSB" full.log
grep 'Target "CoreCompile"' full.log | grep -oP 'project "[^"]*"'

Generating a binlog (only if none exists)

dotnet build /bl:build.binlog

---name: binlog-failure-analysisdescription: Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating binlogs (use binlog-generation), non-MSBuild build systems.license: MIT---# Analyzing MSBuild Failures with Binary LogsThis skill diagnoses MSBuild build failures from a `.binlog` file. The preferredpath uses the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the`binlog` MCP namespace) which is bundled with this plugin. If the MCP server isnot available, fall back to the **binlog replay** workflow at the bottom.## Primary workflow — binlog MCPThe MCP server exposes structured tools for inspecting a `.binlog` withoutparsing text logs. Call them directly instead of replaying the binlog to a textfile. Call `tools/list` for the MCP first if you are unsure which tools are available.**Important constraints:**- The `.binlog` file is a **binary format** — do NOT try to `cat`, `head`, `strings`, or read it directly. Use only the MCP tools to query it.- The **original source/project files might or might NOT be available on disk**. Project files (.csproj, .props, .targets, App.config, etc.) - if you cannot locate them on disk, they can only be read from within the binlog via MCP tools (e.g., embedded/source file retrieval).- **Synthesize findings as you go.** Do not spend all available time investigating — once you have enough evidence, present your conclusions. A partial answer with clear reasoning is better than timing out mid-investigation.Use the available MCP server tools to query the binary log for:- Build errors and warnings- MSBuild properties and their values- MSBuild items (PackageReference, ProjectReference, etc.)- Project evaluation data- Target execution details- File contents embedded in the binlog## Fallback workflow — text-log replay (when MCP is unavailable)Use this only when the MCP server cannot be started (for example, on an olderSDK or in an offline environment without access to the `dotnet-tools` NuGet feed).### Replay the binlog to text logs```bashdotnet msbuild build.binlog -noconlog \ -fl "-flp:v=diag;logfile=full.log;performancesummary" \ -fl1 "-flp1:errorsonly;logfile=errors.log" \ -fl2 "-flp2:warningsonly;logfile=warnings.log"```> **Quoting:** the semicolons must be quoted in every shell — bash, zsh and PowerShell> all treat a bare `;` as a command separator, so an unquoted value is truncated to> `-flp:v=diag` and the log is written to `msbuild.log` instead.### Search the text logs```bashcat errors.loggrep -n -B2 -A2 "CS0246" full.loggrep -i "CoreCompile.*FAILED\|Build FAILED\|error MSB" full.loggrep 'Target "CoreCompile"' full.log | grep -oP 'project "[^"]*"'```## Generating a binlog (only if none exists)```bashdotnet build /bl:build.binlog```

Frequently asked questions