[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M756J6S0XDN0PY5PDPPE36SS":3,"skill-same:01M756J6S0XDN0PY5PDPPE36SS":45},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M756J6S0XDN0PY5PDPPE36SS","binlog-generation",null,"Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild\u002F.NET build context. USE FOR: adding \u002Fbl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ \u002F .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build \u002Fbl:{}).","weiflycc-cmd\u002Fskills","weiflycc-cmd","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250846518?v=4","01M756C4PFGZJWKK04WFB9S5XF","威飛工作室","01M756C4QJJ66QDXN2RN6SXY87",0,"MIT","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-msbuild\u002Fskills\u002Fbinlog-generation\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: binlog-generation\ndescription: \"Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. Only activate in MSBuild\u002F.NET build context. USE FOR: adding \u002Fbl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors or performance. Requires MSBuild 17.8+ \u002F .NET 8 SDK+ for {} placeholder; PowerShell needs -bl:{{}}. DO NOT USE FOR: non-MSBuild build systems (npm, Maven, CMake), analyzing an existing binlog (use binlog-failure-analysis instead). INVOKES: shell commands (dotnet build \u002Fbl:{}).\"\nlicense: MIT\n---\n\n# Generate Binary Logs\n\n**Pass the `\u002Fbl` switch when running any MSBuild-based command.** This is a non-negotiable requirement for all .NET builds.\n\n## Commands That Require \u002Fbl\n\nYou MUST add the `\u002Fbl:{}` flag to:\n- `dotnet build`\n- `dotnet test`\n- `dotnet pack`\n- `dotnet publish`\n- `dotnet restore`\n- `msbuild` or `msbuild.exe`\n- Any other command that invokes MSBuild\n\n## Preferred: Use `{}` for Automatic Unique Names\n\n> **Note:** The `{}` placeholder requires MSBuild 17.8+ \u002F .NET 8 SDK or later.\n\nThe `{}` placeholder in the binlog filename is replaced by MSBuild with a unique identifier, guaranteeing no two builds ever overwrite each other — without needing to track or check existing files.\n\n```bash\n# Every invocation produces a distinct file automatically\ndotnet build \u002Fbl:{}\ndotnet test \u002Fbl:{}\ndotnet build --configuration Release \u002Fbl:{}\n```\n\n**PowerShell requires escaping the braces:**\n\n```powershell\n# PowerShell: escape { } as {{ }}\ndotnet build -bl:{{}}\ndotnet test -bl:{{}}\n```\n\n## Why This Matters\n\n1. **Unique names prevent overwrites** - You can always go back and analyze previous builds\n2. **Failure analysis** - When a build fails, the binlog is already there for immediate analysis\n3. **Comparison** - You can compare builds before and after changes\n4. **No re-running builds** - You never need to re-run a failed build just to generate a binlog\n\n## Examples\n\n```bash\n# ✅ CORRECT - {} generates a unique name automatically (bash\u002Fcmd)\ndotnet build \u002Fbl:{}\ndotnet test \u002Fbl:{}\n\n# ✅ CORRECT - PowerShell escaping\ndotnet build -bl:{{}}\ndotnet test -bl:{{}}\n\n# ❌ WRONG - Missing \u002Fbl flag entirely\ndotnet build\ndotnet test\n\n# ❌ WRONG - No filename (overwrites the same msbuild.binlog every time)\ndotnet build \u002Fbl\ndotnet build \u002Fbl\n```\n\n## When a Specific Filename Is Required\n\nIf the binlog filename needs to be known upfront (e.g., for CI artifact upload), or if `{}` is not available in the installed MSBuild version, pick a name that won't collide with existing files:\n\n1. Check for existing `*.binlog` files in the directory\n2. Choose a name not already taken (e.g., by incrementing a counter from the highest existing number)\n\n```bash\n# Example: directory contains 3.binlog — use 4.binlog\ndotnet build \u002Fbl:4.binlog\n```\n\n## Cleaning the Repository\n\nWhen cleaning the repository with `git clean`, **always exclude binlog files** to preserve your build history:\n\n```bash\n# ✅ CORRECT - Exclude binlog files from cleaning\ngit clean -fdx -e \"*.binlog\"\n\n# ❌ WRONG - This deletes binlog files (they're usually in .gitignore)\ngit clean -fdx\n```\n\nThis is especially important when iterating on build fixes - you need the binlogs to analyze what changed between builds.\n","# Generate Binary Logs\n\n**Pass the `\u002Fbl` switch when running any MSBuild-based command.** This is a non-negotiable requirement for all .NET builds.\n\n## Commands That Require \u002Fbl\n\nYou MUST add the `\u002Fbl:{}` flag to:\n- `dotnet build`\n- `dotnet test`\n- `dotnet pack`\n- `dotnet publish`\n- `dotnet restore`\n- `msbuild` or `msbuild.exe`\n- Any other command that invokes MSBuild\n\n## Preferred: Use `{}` for Automatic Unique Names\n\n> **Note:** The `{}` placeholder requires MSBuild 17.8+ \u002F .NET 8 SDK or later.\n\nThe `{}` placeholder in the binlog filename is replaced by MSBuild with a unique identifier, guaranteeing no two builds ever overwrite each other — without needing to track or check existing files.\n\n```bash\n# Every invocation produces a distinct file automatically\ndotnet build \u002Fbl:{}\ndotnet test \u002Fbl:{}\ndotnet build --configuration Release \u002Fbl:{}\n```\n\n**PowerShell requires escaping the braces:**\n\n```powershell\n# PowerShell: escape { } as {{ }}\ndotnet build -bl:{{}}\ndotnet test -bl:{{}}\n```\n\n## Why This Matters\n\n1. **Unique names prevent overwrites** - You can always go back and analyze previous builds\n2. **Failure analysis** - When a build fails, the binlog is already there for immediate analysis\n3. **Comparison** - You can compare builds before and after changes\n4. **No re-running builds** - You never need to re-run a failed build just to generate a binlog\n\n## Examples\n\n```bash\n# ✅ CORRECT - {} generates a unique name automatically (bash\u002Fcmd)\ndotnet build \u002Fbl:{}\ndotnet test \u002Fbl:{}\n\n# ✅ CORRECT - PowerShell escaping\ndotnet build -bl:{{}}\ndotnet test -bl:{{}}\n\n# ❌ WRONG - Missing \u002Fbl flag entirely\ndotnet build\ndotnet test\n\n# ❌ WRONG - No filename (overwrites the same msbuild.binlog every time)\ndotnet build \u002Fbl\ndotnet build \u002Fbl\n```\n\n## When a Specific Filename Is Required\n\nIf the binlog filename needs to be known upfront (e.g., for CI artifact upload), or if `{}` is not available in the installed MSBuild version, pick a name that won't collide with existing files:\n\n1. Check for existing `*.binlog` files in the directory\n2. Choose a name not already taken (e.g., by incrementing a counter from the highest existing number)\n\n```bash\n# Example: directory contains 3.binlog — use 4.binlog\ndotnet build \u002Fbl:4.binlog\n```\n\n## Cleaning the Repository\n\nWhen cleaning the repository with `git clean`, **always exclude binlog files** to preserve your build history:\n\n```bash\n# ✅ CORRECT - Exclude binlog files from cleaning\ngit clean -fdx -e \"*.binlog\"\n\n# ❌ WRONG - This deletes binlog files (they're usually in .gitignore)\ngit clean -fdx\n```\n\nThis is especially important when iterating on build fixes - you need the binlogs to analyze what changed between builds.\n",{"name":5,"license":15,"description":7},"main","5810d492c9b301d8227f932bf87b5c954c4fa4d6","plugins\u002Fdotnet-msbuild\u002Fskills\u002Fbinlog-generation","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd","weiflycc.com","2026-11-10 03:26:55",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add weiflycc-cmd\u002Fskills --skill binlog-generation",{"tool":37,"command":38},"bunx","bunx skills add weiflycc-cmd\u002Fskills --skill binlog-generation",{"tool":40,"command":41},"pnpm","pnpm dlx skills add weiflycc-cmd\u002Fskills --skill binlog-generation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-msbuild\u002Fskills\u002Fbinlog-generation\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M76SGT4WG5682JQJ0V3NSK6X","system-text-json-net11","Provides guidance on new System.Text.Json APIs introduced in .NET 11. It covers typed JsonTypeInfo access via GetTypeInfo\u003CT> and TryGetTypeInfo\u003CT> on JsonSerializerOptions, and the new JsonNamingPolicy.PascalCase static property. Use when serializing or deserializing JSON in .NET 11 applications and needing typed metadata access or PascalCase property naming.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet11\u002Fskills\u002Fsystem-text-json-net11\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M76SGPNZYYV9BCZJW7BF7J8A","nuget-trusted-publishing","Set up NuGet trusted publishing (OIDC) on a GitHub Actions repo — replaces long-lived API keys with short-lived tokens. USE FOR: trusted publishing, NuGet OIDC, keyless NuGet publish, migrate from NuGet API key, NuGet\u002Flogin, secure NuGet publishing. DO NOT USE FOR: publishing to private feeds or Azure Artifacts (OIDC is nuget.org only). INVOKES: shell (powershell or bash), edit, create, ask_user for guided repo setup.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet\u002Fskills\u002Fnuget-trusted-publishing\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M76SGHVNBNVM1DMVDYTMAE5G","dotnet-pinvoke","Correctly call native (C\u002FC++) libraries from .NET using P\u002FInvoke and LibraryImport. Covers function signatures, string marshalling, memory lifetime, SafeHandle, and cross-platform patterns. USE FOR: writing new P\u002FInvoke or LibraryImport declarations, reviewing or debugging existing native interop code, wrapping a C or C++ library for use in .NET, diagnosing crashes, memory leaks, or corruption at the managed\u002Fnative boundary. DO NOT USE FOR: COM interop, C++\u002FCLI mixed-mode assemblies, or pure managed code with no native dependencies.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet\u002Fskills\u002Fdotnet-pinvoke\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M76SGDB9Z3GSB1CFW314NC84","csharp-scripts","Run file-based C# apps with the .NET CLI when the user explicitly wants C#\u002F.NET code without creating a project. Use for C# language\u002FAPI experiments, one-file C# apps, small multi-file C# apps composed with `#:include`\u002F`#:exclude`, or C# file-based apps linked with `#:ref`. Do not use for language-agnostic throwaway scripts, generic computations, Python\u002FPowerShell-style automation, full projects, or existing app integration.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet\u002Fskills\u002Fcsharp-scripts\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M76SG805T8W764WAKB1NP3CJ","thread-abort-migration","Guides migration of .NET Framework Thread.Abort usage to cooperative cancellation in modern .NET. USE FOR: modernizing code that calls Thread.Abort, catching ThreadAbortException, replacing Thread.ResetAbort, replacing Thread.Interrupt for thread termination, resolving PlatformNotSupportedException or SYSLIB0006 after retargeting to .NET 6+, migrating ASP.NET Response.End or Response.Redirect(url, true) which internally call Thread.Abort. DO NOT USE FOR: code that only uses Thread.Join, Thread.Sleep, or Thread.Start without any abort, interrupt, or ThreadAbortException usage — these APIs work identically in modern .NET and need no migration. Also not for projects staying on .NET Framework, or Thread.Abort usage inside third-party libraries you do not control.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-upgrade\u002Fskills\u002Fthread-abort-migration\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M76SG2588ZJBE5C51HYJJSKV","migrate-nullable-references","Enable nullable reference types in a C# project and systematically resolve all warnings. USE FOR: adopting NRTs in existing codebases, file-by-file or project-wide migration, fixing CS8602\u002FCS8618\u002FCS86xx warnings, annotating APIs for nullability, cleaning up null-forgiving operators, upgrading dependencies with new nullable annotations. DO NOT USE FOR: projects already fully migrated with zero warnings (unless auditing suppressions), fixing a handful of nullable warnings in code that already has NRTs enabled, suppressing warnings without fixing them, C# 7.3 or earlier projects. INVOKES: Get-NullableReadiness.ps1 scanner script.","https:\u002F\u002Fgithub.com\u002Fweiflycc-cmd\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fdotnet-upgrade\u002Fskills\u002Fmigrate-nullable-references\u002FSKILL.md",[],[]]