[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M699CD99N43B2KZR361Y9P1J":3,"skill-same:01M699CD99N43B2KZR361Y9P1J":65},{"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":23,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M699CD99N43B2KZR361Y9P1J","binlog-failure-analysis",null,"Diagnose existing MSBuild .binlog failures with MCP\u002Freplay; not log capture or non-MSBuild failures.","microsoft\u002Ftestfx","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M699C71CJ91B5WZ3AXG3GG2M",1059,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbinlog-failure-analysis\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36],"binlog failure analysis","analysis","failure analysis","MCP","msbuild","diagnose","capture","log","replay","with mcp","with","Existing","log capture","2026-11-10 10:12:30",false,"---\nname: binlog-failure-analysis\ndescription: \"Diagnose existing MSBuild .binlog failures with MCP\u002Freplay; not log capture or non-MSBuild failures.\"\nlicense: MIT\n---\n\n# Analyzing MSBuild Failures with Binary Logs\n\n## Scope and routing\n\nAnalyze 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.\n\nThis skill diagnoses MSBuild build failures from a `.binlog` file. The preferred\npath uses the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the\n`binlog` MCP namespace) which is bundled with this plugin. If the MCP server is\nnot available, fall back to the **binlog replay** workflow at the bottom.\n\n## Primary workflow — binlog MCP\n\nThe MCP server exposes structured tools for inspecting a `.binlog` without\nparsing text logs. Call them directly instead of replaying the binlog to a text\nfile. Call `tools\u002Flist` for the MCP first if you are unsure which tools are available.\n\n**Important constraints:**\n- 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.\n- The **original source\u002Fproject 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\u002Fsource file retrieval).\n- **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.\n\nUse the available MCP server tools to query the binary log for:\n- Build errors and warnings\n- MSBuild properties and their values\n- MSBuild items (PackageReference, ProjectReference, etc.)\n- Project evaluation data\n- Target execution details\n- File contents embedded in the binlog\n\n## Fallback workflow — text-log replay (when MCP is unavailable)\n\nUse this only when the MCP server cannot be started (for example, on an older\nSDK or in an offline environment).\n\n### Replay the binlog to text logs\n\n```bash\ndotnet msbuild build.binlog -noconlog \\\n  -fl  \"-flp:v=diag;logfile=full.log;performancesummary\" \\\n  -fl1 \"-flp1:errorsonly;logfile=errors.log\" \\\n  -fl2 \"-flp2:warningsonly;logfile=warnings.log\"\n```\n\n> **PowerShell note:** Use `-flp:\"v=diag;logfile=full.log;performancesummary\"`\n> (quoted semicolons).\n\n### Search the text logs\n\n```bash\ncat errors.log\ngrep -n -B2 -A2 \"CS0246\" full.log\ngrep -i \"CoreCompile.*FAILED\\|Build FAILED\\|error MSB\" full.log\ngrep 'Target \"CoreCompile\"' full.log | grep -oP 'project \"[^\"]*\"'\n```\n\n## Generating a binlog (only if none exists)\n\n```bash\ndotnet build \u002Fbl:build.binlog\n```\n","# Analyzing MSBuild Failures with Binary Logs\n\n## Scope and routing\n\nAnalyze 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.\n\nThis skill diagnoses MSBuild build failures from a `.binlog` file. The preferred\npath uses the **binlog MCP server** (`Microsoft.AITools.BinlogMcp`, exposed under the\n`binlog` MCP namespace) which is bundled with this plugin. If the MCP server is\nnot available, fall back to the **binlog replay** workflow at the bottom.\n\n## Primary workflow — binlog MCP\n\nThe MCP server exposes structured tools for inspecting a `.binlog` without\nparsing text logs. Call them directly instead of replaying the binlog to a text\nfile. Call `tools\u002Flist` for the MCP first if you are unsure which tools are available.\n\n**Important constraints:**\n- 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.\n- The **original source\u002Fproject 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\u002Fsource file retrieval).\n- **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.\n\nUse the available MCP server tools to query the binary log for:\n- Build errors and warnings\n- MSBuild properties and their values\n- MSBuild items (PackageReference, ProjectReference, etc.)\n- Project evaluation data\n- Target execution details\n- File contents embedded in the binlog\n\n## Fallback workflow — text-log replay (when MCP is unavailable)\n\nUse this only when the MCP server cannot be started (for example, on an older\nSDK or in an offline environment).\n\n### Replay the binlog to text logs\n\n```bash\ndotnet msbuild build.binlog -noconlog \\\n  -fl  \"-flp:v=diag;logfile=full.log;performancesummary\" \\\n  -fl1 \"-flp1:errorsonly;logfile=errors.log\" \\\n  -fl2 \"-flp2:warningsonly;logfile=warnings.log\"\n```\n\n> **PowerShell note:** Use `-flp:\"v=diag;logfile=full.log;performancesummary\"`\n> (quoted semicolons).\n\n### Search the text logs\n\n```bash\ncat errors.log\ngrep -n -B2 -A2 \"CS0246\" full.log\ngrep -i \"CoreCompile.*FAILED\\|Build FAILED\\|error MSB\" full.log\ngrep 'Target \"CoreCompile\"' full.log | grep -oP 'project \"[^\"]*\"'\n```\n\n## Generating a binlog (only if none exists)\n\n```bash\ndotnet build \u002Fbl:build.binlog\n```\n",{"name":5,"license":15,"description":7},"main","f8f2bfd77819bb789d4736ce7db4a567a37fcf7e",".agents\u002Fskills\u002Fbinlog-failure-analysis",315,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-14 14:01:43",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add microsoft\u002Ftestfx --skill binlog-failure-analysis",{"tool":57,"command":58},"bunx","bunx skills add microsoft\u002Ftestfx --skill binlog-failure-analysis",{"tool":60,"command":61},"pnpm","pnpm dlx skills add microsoft\u002Ftestfx --skill binlog-failure-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fbinlog-failure-analysis\u002FSKILL.md",true,[],[66,93,121,142,162,186],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":37},"01M70GYY0AV0JGMTHE2CN6TNYK","dotnet-breaking-changes","Use before changing .NET\u002FC# code whose callers you do not control: a NuGet library, or a repo with PublicAPI.Shipped\u002FUnshipped.txt, ApiCompat, multiple TargetFrameworks, InternalsVisibleTo, or generated (.g.cs) partials. Green builds miss silent breaks from optional parameters, parameter names, sealing, const values, nullability, and #if. USE FOR: \"without breaking existing callers\"; adding a public method, overload, optional parameter, or interface member to a shipped library; renaming a public method or an internal helper a friend assembly uses; consolidating duplicated logic; changing a signature, nullability, default, or attribute; adding a target framework; RS0016\u002FRS0017 or ApiCompat errors; \"is this PR breaking?\". For a rename, extract, or merge, also invoke csharp-refactoring. DO NOT USE FOR: an executable whose callers all live in one project; renaming a local variable or private member, even in a shipped library; formatting; framework\u002FSDK\u002FNuGet upgrades (use dotnet-upgrade).","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdotnet-breaking-changes\u002FSKILL.md",[],[73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92],"dotnet","dotnet breaking changes","changes","green","project","default","local","errors","interface","generated","upgrade","invoke","you","code","refactoring","merge","rename","library","live","assembly",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":102,"publishedAt":37},"01M699HHE9DTZWAMPB1ZR7ZKSW","testfx-test-value-evidence","Apply the vendored test-value-evidence skill with TestFx toolchain, assertion, parallel-safety, packed-consumer, and review conventions. Use when implementing or reviewing behavior-changing TestFx PRs or commits, including source-only changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-test-value-evidence\u002FSKILL.md",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,34,75,118,119,120],"test","testfx test value evidence","test value evidence","evidence","value","review","parallel","toolchain","commits","implementing","prs","only","use","when","apply","behavior","Safety","conventions",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":37},"01M699HEYWH1B9XGNBFY8J2FZS","testfx-parallel-safety-preflight","Check concurrency and isolation before implementing or refactoring TestFx tests, lifecycle code, helpers, shared-state declarations, or production paths those tests exercise. Use before narrowing DoNotParallelize or ResourceLock, changing parallelization settings, or introducing asynchronous workers; repeat against the final diff.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-parallel-safety-preflight\u002FSKILL.md",[],[128,119,129,109,130,131,112,132,86,133,87,134,135,136,137,138,139,140,115,141],"testfx parallel safety preflight","preflight","shared","asynchronous","exercise","concurrency","paths","isolation","helpers","diff","parallelization","lifecycle","tests","workers",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":37},"01M699HC61ZV9GJ2C8JV03951G","testfx-localization-validation","Validate generated TestFx localization catalogs, resource IDs, placeholders and locked tokens. Use for RESX\u002FXLF changes, OneLoc PRs, localization build failures, duplicate targets or units, and orphaned translation entries.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-localization-validation\u002FSKILL.md",[],[149,150,151,152,153,154,155,156,157,113,82,115,158,159,75,160,161],"testfx localization validation","validation","localization","validate","translation","ids","for","tokens","entries","units","duplicate","targets","build",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":37},"01M699H9J2NWQXE4BDT6R0FH7S","testfx-acceptance-validation","Validate TestFx shipping paths and capable CI execution using packed consumers, package\u002Fcache provenance, exact exits and artifacts, and selected-versus-executed test evidence. Use for acceptance regressions, package\u002FMSBuild\u002Flauncher\u002Fprotocol changes, or skipped-only CI results; not for unrelated unit-only or documentation changes.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftestfx-acceptance-validation\u002FSKILL.md",[168],{"categoryNo":100,"categoryName":101,"taxonomyType":21,"taxonomyTypeDesc":22},[170,171,150,103,28,106,172,173,174,114,175,115,176,177,178,179,180,181,182,183,184,185,134,155],"testfx acceptance validation","acceptance","launcher","ci","execution","package","cache","artifacts","provenance","documentation","unrelated","shipping","results","protocol","unit","ci results",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":37},"01M699H70BB999BT4F627T1PHE","session-delivery-hygiene","Gate local-session scope, persistent delivery, live PR state, integration provenance, and owned cleanup. Use before implementing guidance changes, changing or pushing PR work, diagnosing package\u002Foutput mismatches, or handing off implementation.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002Ftestfx\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fsession-delivery-hygiene\u002FSKILL.md",[],[193,194,195,196,197,112,79,198,199,91,200,175,115,178,201,202,75,203,204,205],"session delivery hygiene","delivery","session","hygiene","scope","cleanup","work","pr","output","state","integration","guidance","gate"]