What problem does it solve? MSBuild build failures often produce console output that is too terse or too noisy to explain the root cause, especially in multi-project solutions where errors cascade. This Skill analyzes an existing .binlog file to pinpoint errors, warnings, target execution order, and project evaluation data. ## Core Features & Use Cases - Structured binlog inspection: Query errors, warnings, MSBuild properties, items, and target execution through the binlog MCP server instead of parsing raw text. - Text-log replay fallback: Replay the binlog into full, errors-only, and warnings-only text logs when the MCP server is unavailable, then grep for specific error codes like CS0246. - Embedded file retrieval: Read project files (.csproj, .props, .targets) embedded in the binlog even when the original sources are not on disk. - Use Case: A CI build fails with cascading errors across 20 projects. Provide the build.binlog file and get a diagnosis of which project failed first, which target failed, and why. ## Quick Start Analyze the attached build.binlog file and tell me which project failed first and what caused the build error.