← Search

MSBuild binlog generation for .NET build diagnostics
Developer tools 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit 3d38ac3
Install test only, on the date shown. This does not guarantee the code is safe.
🔎 Install prompt analysis · 2026-10-13 : runs commands
⚙ Needs: .NET SDK (8+ for the `{}` unique-name placeholder…

MSBuild binlog generation for .NET build diagnostics

Add /bl to every MSBuild command for failure-proof build traces — unique names, CI naming, cleanup rules

At a glance
What
Add /bl to every MSBuild command for failure-proof build traces — unique names, CI naming, cleanup rules
Cost
Free
Needs
.NET SDK (8+ for the `{}` unique-name placeholder, or MSBuild 17.8+)
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

MSBuild binlog generation is a free Muse skill, the .NET team's discipline for MSBuild logs: add /bl to every dotnet build, test, pack, publish or restore command so a build trace exists before anything fails. It uses unique generated names, PowerShell escaping, explicit CI naming, binlog preservation during git clean, and verification that a .binlog was produced.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 3d38ac3

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: .NET SDK (8+ for the `{}` unique-name placeholder, or MSBuild 17.8+) Install "MSBuild binlog generation for .NET build diagnostics" for me. Give my agent the official .NET discipline for generating MSBuild binary logs — the `/bl:{}` convention on every build command, unique names, PowerShell escaping, CI naming and binlog preservation Repository: https://raw.githubusercontent.com/dotnet/skills/3d38ac343faf65054f7e8d45ca06925273e867e2/plugins/dotnet-msbuild/skills/binlog-generation/SKILL.md Pinned version: install the code at commit 3d38ac343faf65054f7e8d45ca06925273e867e2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the dotnet-skills-binlog-generation skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "dotnet-skills-binlog-generation". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — start adding `/bl:{}` to builds). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
  • It can run commands on your Muse’s computer.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 3d38ac3 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : registry.npmjs.org
🔎 Install prompt analysis · 2026-10-13 : runs commands
What the scan found — excerpts from the install prompt
  • runs commands — Install "MSBuild binlog generation for .NET build diagnostics" for me. Give my agent the official .NET discipl · Installe-moi « Génération de binlogs MSBuild pour diagnostic de builds .NET ». Donne à mon agent la discipline
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
3d38ac3 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 18, 2026 · Observed during the install test: registry.npmjs.org
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : runs commands

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.