[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XHKMAG2NWC4BYAWBTPKX5":3,"skill-same:01M79XHKMAG2NWC4BYAWBTPKX5":53},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79XHKMAG2NWC4BYAWBTPKX5","deniz-dotnet-general.platform-detection",null,"Identify a .NET project's test platform, framework, command mode, and SDK-style vs classic project system. Use only for \"which test platform\u002Fframework?\", \"VSTest or MTP?\", or \"what runner does this project use?\", including bridge settings, UseVSTest opt-outs, and incompatible or conflicting VSTest\u002FMTP configuration. Resolves global.json, project, packages.config, Directory.Build.props, and Directory.Packages.props precedence for MSTest\u002FxUnit\u002FNUnit\u002FTUnit. DO NOT USE when the user asks to run\u002Ffilter tests or for commands, flags, TRX\u002Fdumps, or test-command\u002Ffilter errors; use run-tests directly. Do not route hot-reload or migration requests here as the entry skill; mtp-hot-reload may use this skill internally for platform detection.","Blind-Striker\u002Fagent-skills-and-plugins","Blind-Striker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1965259?v=4","01M79WFXTE5PH0C1VB7B54ANMN","Deniz İrgin","01M79WFXV5KZ5GST1K8G035DM5",1,"MIT","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.platform-detection\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: deniz-dotnet-general.platform-detection\ndescription: Identify a .NET project's test platform, framework, command mode,\n  and SDK-style vs classic project system. Use only for \"which test\n  platform\u002Fframework?\", \"VSTest or MTP?\", or \"what runner does this project\n  use?\", including bridge settings, UseVSTest opt-outs, and incompatible or\n  conflicting VSTest\u002FMTP configuration. Resolves global.json, project,\n  packages.config, Directory.Build.props, and Directory.Packages.props\n  precedence for MSTest\u002FxUnit\u002FNUnit\u002FTUnit. DO NOT USE when the user asks to\n  run\u002Ffilter tests or for commands, flags, TRX\u002Fdumps, or test-command\u002Ffilter\n  errors; use run-tests directly. Do not route hot-reload or migration requests\n  here as the entry skill; mtp-hot-reload may use this skill internally for\n  platform detection.\n---\n\n# Test Platform and Framework Detection\n\nDetermine **which test platform** (VSTest or Microsoft.Testing.Platform) and **which test framework** (MSTest, xUnit, NUnit, TUnit) a project uses.\n\n## Response contract\n\nHonor the user's requested labels and order exactly, substituting the actual\nclassification for every placeholder. Start with the verdict: never put a\nheading, scratch analysis, tool syntax, or an echoed template before it. Follow\nwith one concise evidence sentence naming the repository facts needed to justify\nevery requested classification. When `Framework` is requested, name the package\nor project SDK that identifies it. Use a second sentence only for a conflict, an\nincomplete configuration, or target-framework-specific differences.\n\n`Platform` means the platform that actually executes tests: **VSTest** or\n**MTP**. If conflicting or incomplete configuration prevents execution, report\nit as unavailable rather than inventing a successful platform.\n\nNever classify the executed platform from `global.json` `test.runner` alone.\nThat setting selects `dotnet test` command mode; even an explicit `VSTest`\nvalue can bridge to an executable MTP application, except on SDK 10+ with\nMicrosoft.Testing.Platform 2.x (see the classification order below). Continue through the project\nrunner, bridge, and output-shape signals before writing `Platform:`.\n\nApply this scope gate before drafting the evidence:\n\n| User asks for | Evidence to include | Omit |\n|---------------|---------------------|------|\n| Platform and framework | Final runner selector and its winning source; package or project SDK identifying the framework; when needed, the property that makes it executable | Command mode; common SDK facts; `OutputType` unless it is missing or conflicting |\n| The single deciding signal | That runner-selection property, why its source wins, and why a competing package does not select or imply VSTest; still name the package or project SDK identifying a requested framework | Bridge, `OutputType`, SDK mode, and unrelated prerequisites when the configuration is complete |\n| Platforms per target framework | Only the conditional final values that differ by target | Common properties and project-wide SDK commentary |\n| Explicit opt-out | Final `UseVSTest` value and its winning source | Superseded defaults unless they create a conflict |\n| `dotnet test` mode | The separate command-mode and executed-platform classifications | None of the requested axes |\n\nIf the requested labels omit `dotnet test mode`, do not state or explain command\nmode anywhere in the response. An exact bridge property may still be decisive\nplatform evidence, but do not turn it into SDK or CLI-mode commentary.\nWhen the user asks which single signal decides between an explicit runner\nproperty and `Microsoft.NET.Test.Sdk`, the evidence sentence must say both that\nthe runner property selects MTP and that `Microsoft.NET.Test.Sdk` does not\nselect or imply VSTest.\n\nWhen import precedence decides a property, state why the winning source wins\n(for example, it is imported later or its condition applies), not merely that it\ncontains the final value or overrides another assignment.\n\nKeep the explanation on the requested axis:\n\n- An SDK version pin in `global.json` is context, not a platform selector. Claim\n  that `global.json` selects VSTest or native MTP only when its `test.runner`\n  setting actually does so.\n- If `UseVSTest=true` is decisive, say that directly. Do not speculate about an\n  absent `test.runner` or describe SDK pinning as an additional platform choice.\n- If command mode was not requested, do not add it, even when it was needed\n  internally to determine the executed platform.\n\nWhen a classic-project request also asks for the command family, add a direct\nline such as `Command family: MSBuild + vstest.console.exe`; do not turn it into\nan optional alternative or add an unnecessary build qualifier.\n\nFor a file-backed request, enumerate the following configuration names once,\nthen read every relevant file that is present in one batched operation:\n`global.json`, `.csproj`, `packages.config`, `Directory.Build.props`,\n`Directory.Build.targets`, `Directory.Packages.props`, and explicit imported\n`.props` \u002F `.targets`. A setting absent from the project file may be defined by\nan import, so never infer its final value from the `.csproj` alone. Do not search\nthe web or inspect unrelated files when repository configuration is sufficient.\n\nResolve properties in the actual MSBuild import order, not with a fixed\n\"project beats props\" rule. For every applicable target framework:\n\n1. Follow the import graph and conditions. A later applicable assignment wins.\n   `Directory.Build.props` is normally imported before the project body, so an\n   unconditional project assignment normally overrides it; later `.targets`\n   can override the project again.\n2. Record the final value and its winning source for `UseVSTest`, the framework\n   runner selector, `TestingPlatformDotnetTestSupport`, and `OutputType`.\n3. Treat `Directory.Packages.props` as version evidence unless it also contains\n   relevant properties. Resolve package\u002FSDK versions before applying\n   version-dependent defaults.\n4. Never infer a property from package presence. A package or SDK default counts\n   only when that resolved version actually supplies it and no later assignment\n   overrides it.\n\n## Detecting the project system\n\nClassify the project before selecting a CLI:\n\n- Root `Sdk` attribute or `\u003CSdk>` declaration: SDK-style.\n- `ToolsVersion`, `Microsoft.Common.props` \u002F `Microsoft.CSharp.targets` imports,\n  explicit `\u003CReference>` and `\u003CCompile Include>` items: classic non-SDK.\n- `packages.config`: classic NuGet dependency management.\n\nClassic projects can still use VSTest-compatible adapters, but `dotnet test` is\nnot automatically a valid invocation. Preserve repository scripts\u002FCI commands,\ncommonly MSBuild followed by `vstest.console.exe`. Mention `MSTest.exe` only\nwhen repository configuration or documentation establishes that legacy runner.\n\n## Detecting the test framework\n\nRead the `.csproj`, adjacent `packages.config`, and\n`Directory.Build.props` \u002F `Directory.Packages.props` and look for:\n\n| Package or SDK reference | Framework |\n|--------------------------|-----------|\n| `MSTest` metapackage, `\u003CProject Sdk=\"MSTest.Sdk[\u002Fversion]\">`, or `\u003CSdk Name=\"MSTest.Sdk\">` | MSTest |\n| `MSTest.TestFramework` + `MSTest.TestAdapter` | MSTest (also valid for v3\u002Fv4) |\n| `xunit`, `xunit.v3`, `xunit.v3.mtp-v1`, `xunit.v3.mtp-v2`, `xunit.v3.core.mtp-v1`, `xunit.v3.core.mtp-v2` | xUnit |\n| `NUnit` + `NUnit3TestAdapter` | NUnit |\n| `TUnit` | TUnit (MTP only) |\n\nIn classic projects, package IDs and versions may appear only in\n`packages.config`, while the project contains assembly `\u003CReference>` elements\nwith `HintPath` values. Use both sources.\n\n## Detecting the executed test platform\n\nIf the user explicitly requests `dotnet test` mode, read\n[`references\u002Fcommand-mode.md`](references\u002Fcommand-mode.md) before answering.\nDo not load that reference or mention command mode for a\nplatform\u002Fframework-only request.\n\nFor an SDK 8\u002F9 request that explicitly asks about command mode and has no\neffective bridge, state all three facts in one causal sentence: the runner makes\nthe project MTP-capable, `dotnet test` remains in VSTest mode, and the missing\nbridge means VSTest actually executes the tests. Mention that native MTP command\nmode starts with SDK 10 only when it helps explain that result.\n\nWhen execution is permitted and neither the prompt nor `global.json` identifies\nthe SDK, run `dotnet --version` once. For read-only identification requests that\nprohibit execution, do not probe the installed SDK; use repository facts and\nstate any necessary SDK assumption.\n\nAfter resolving final property values, classify in this order:\n\n1. Final `UseVSTest=true` selects VSTest. If `global.json` simultaneously\n   selects native MTP command mode, report `Platform: unavailable` because the\n   command mode and project opt-out conflict.\n2. A native-MTP selection in `global.json` executes a compatible MTP\n   application with final `OutputType=Exe` on MTP. A VSTest-only,\n   library-output, or opted-out project is unavailable.\n3. On SDK 8\u002F9, an enabled MTP runner plus final\n   `TestingPlatformDotnetTestSupport=true` plus final `OutputType=Exe` executes\n   on MTP.\n4. On SDK 10+ in VSTest command mode, an MTP runner from\n   Microsoft.Testing.Platform 2.x (current TUnit brings it in transitively) is\n   unavailable. The `_MTPBeforeVSTest` target of Microsoft.Testing.Platform.MSBuild\n   fails the build (\"Testing with VSTest target is no longer supported by\n   Microsoft.Testing.Platform on .NET 10 SDK and later\") whatever\n   `TestingPlatformDotnetTestSupport` says, so no bridge executes it. Name the\n   remedy: `global.json` `\"test\": { \"runner\": \"Microsoft.Testing.Platform\" }`\n   selects native MTP mode (step 2).\n5. If the runner is enabled but the bridge is absent or false, a dual-capable\n   MSTest, NUnit, or xUnit project remains on VSTest: the runner establishes MTP\n   capability, but SDK 8\u002F9 `dotnet test` cannot reach it and the VSTest adapter\n   executes the tests instead. If the bridge is true but no runner is enabled,\n   the project also remains on VSTest.\n6. A runner and bridge with non-executable output is incomplete and unavailable.\n   An MTP-only framework that cannot be reached by the selected SDK path is also\n   unavailable, not VSTest.\n\nKeep each signal's role exact:\n\n- The runner property selects the test application.\n- `TestingPlatformDotnetTestSupport=true` lets SDK 8\u002F9 `dotnet test` reach that\n  application.\n- `OutputType=Exe` supplies the executable host shape. It does **not** select or\n  enable MTP.\n\nDo not confuse the `MSTest` metapackage with the `MSTest.Sdk` project SDK.\n`PackageReference Include=\"MSTest\"` plus `EnableMSTestRunner=true` enables the\nMSTest MTP runner, but it does **not** implicitly set\n`TestingPlatformDotnetTestSupport`.\n\nMSTest.Sdk enables the MTP runner by default. Check its resolved version and\nevaluated properties for bridge behavior: version 3.8 supplies\n`TestingPlatformDotnetTestSupport` unless a later assignment overrides it,\nwhile newer SDKs on .NET 10 may expect native MTP mode instead.\n`\u003CUseVSTest>true\u003C\u002FUseVSTest>` opts back into VSTest.\n\n| Signal | Meaning |\n|--------|---------|\n| `\u003CProject Sdk=\"MSTest.Sdk...\">` with no `UseVSTest` | MTP application; inspect the resolved SDK version and evaluated bridge property |\n| `MSTest` metapackage + `\u003CEnableMSTestRunner>true>` | MTP runner enabled; does not imply the VSTest-to-MTP bridge |\n| `\u003CUseMicrosoftTestingPlatformRunner>true` | Deciding xUnit runner-selection signal |\n| `\u003CEnableMSTestRunner>true>` \u002F `\u003CEnableNUnitRunner>true>` | Deciding MSTest\u002FNUnit runner-selection signal |\n| `TestingPlatformDotnetTestSupport=true` | Execution prerequisite for a VSTest-to-MTP bridge, not the runner-selection signal |\n| `Microsoft.Testing.Platform` package | MTP-capable application; not decisive by itself |\n| `TUnit` | MTP-only framework |\n| Final evaluated `\u003COutputType>Exe\u003C\u002FOutputType>` | Required executable host shape for package-based MTP applications |\n\n`Microsoft.NET.Test.Sdk` alone is not decisive; it can remain for compatibility\nin an MTP-enabled project. When an explicit override decides the result, name\nthe final override and its source, not the superseded default.\nWhen a runner-selection property competes with `Microsoft.NET.Test.Sdk`, say\nthat the runner property selects MTP and `Microsoft.NET.Test.Sdk` does **not**\nselect or imply VSTest. It may remain as compatibility support, but that is\nsecondary. `TestingPlatformDotnetTestSupport=true` is a bridge prerequisite, not\nthe runner-selection signal; never say that this property alone enables the\nbridge. For a request asking which single signal decides, stop there. Omit\nbridge or host-shape prerequisites when the configuration is complete, and add\nthem only when needed to explain why the selected runner cannot execute.\nLikewise, when an enabled runner is overridden or unreachable, state both axes\ncausally: the runner property makes the project MTP-capable, but the final\n`UseVSTest`\u002Fbridge\u002Foutput setting determines which platform actually executes.\nName the runner selector before using a package reference only to identify the\nframework.\n\nUse causal evidence, not a bag of signals. For example:\n\n```text\nPlatform: MTP\nFramework: NUnit\n\nDirectory.Build.props supplies final EnableNUnitRunner=true and\nTestingPlatformDotnetTestSupport=true, so NUnit executes on MTP.\n```\n\nFor an incompatible configuration, give one minimal alignment choice after the\nverdict without modifying files: either select the project's configured\nplatform globally or remove the project opt-out to use the globally selected\nplatform.\n\n### Conditional and per-target-framework properties\n\nEvaluate runner and bridge properties for each target framework. If conditions\nproduce different executed platforms, report each target explicitly (for\nexample, `net8.0: VSTest`, `net9.0: MTP`) rather than collapsing the project to\none global platform.\n","# Test Platform and Framework Detection\n\nDetermine **which test platform** (VSTest or Microsoft.Testing.Platform) and **which test framework** (MSTest, xUnit, NUnit, TUnit) a project uses.\n\n## Response contract\n\nHonor the user's requested labels and order exactly, substituting the actual\nclassification for every placeholder. Start with the verdict: never put a\nheading, scratch analysis, tool syntax, or an echoed template before it. Follow\nwith one concise evidence sentence naming the repository facts needed to justify\nevery requested classification. When `Framework` is requested, name the package\nor project SDK that identifies it. Use a second sentence only for a conflict, an\nincomplete configuration, or target-framework-specific differences.\n\n`Platform` means the platform that actually executes tests: **VSTest** or\n**MTP**. If conflicting or incomplete configuration prevents execution, report\nit as unavailable rather than inventing a successful platform.\n\nNever classify the executed platform from `global.json` `test.runner` alone.\nThat setting selects `dotnet test` command mode; even an explicit `VSTest`\nvalue can bridge to an executable MTP application, except on SDK 10+ with\nMicrosoft.Testing.Platform 2.x (see the classification order below). Continue through the project\nrunner, bridge, and output-shape signals before writing `Platform:`.\n\nApply this scope gate before drafting the evidence:\n\n| User asks for | Evidence to include | Omit |\n|---------------|---------------------|------|\n| Platform and framework | Final runner selector and its winning source; package or project SDK identifying the framework; when needed, the property that makes it executable | Command mode; common SDK facts; `OutputType` unless it is missing or conflicting |\n| The single deciding signal | That runner-selection property, why its source wins, and why a competing package does not select or imply VSTest; still name the package or project SDK identifying a requested framework | Bridge, `OutputType`, SDK mode, and unrelated prerequisites when the configuration is complete |\n| Platforms per target framework | Only the conditional final values that differ by target | Common properties and project-wide SDK commentary |\n| Explicit opt-out | Final `UseVSTest` value and its winning source | Superseded defaults unless they create a conflict |\n| `dotnet test` mode | The separate command-mode and executed-platform classifications | None of the requested axes |\n\nIf the requested labels omit `dotnet test mode`, do not state or explain command\nmode anywhere in the response. An exact bridge property may still be decisive\nplatform evidence, but do not turn it into SDK or CLI-mode commentary.\nWhen the user asks which single signal decides between an explicit runner\nproperty and `Microsoft.NET.Test.Sdk`, the evidence sentence must say both that\nthe runner property selects MTP and that `Microsoft.NET.Test.Sdk` does not\nselect or imply VSTest.\n\nWhen import precedence decides a property, state why the winning source wins\n(for example, it is imported later or its condition applies), not merely that it\ncontains the final value or overrides another assignment.\n\nKeep the explanation on the requested axis:\n\n- An SDK version pin in `global.json` is context, not a platform selector. Claim\n  that `global.json` selects VSTest or native MTP only when its `test.runner`\n  setting actually does so.\n- If `UseVSTest=true` is decisive, say that directly. Do not speculate about an\n  absent `test.runner` or describe SDK pinning as an additional platform choice.\n- If command mode was not requested, do not add it, even when it was needed\n  internally to determine the executed platform.\n\nWhen a classic-project request also asks for the command family, add a direct\nline such as `Command family: MSBuild + vstest.console.exe`; do not turn it into\nan optional alternative or add an unnecessary build qualifier.\n\nFor a file-backed request, enumerate the following configuration names once,\nthen read every relevant file that is present in one batched operation:\n`global.json`, `.csproj`, `packages.config`, `Directory.Build.props`,\n`Directory.Build.targets`, `Directory.Packages.props`, and explicit imported\n`.props` \u002F `.targets`. A setting absent from the project file may be defined by\nan import, so never infer its final value from the `.csproj` alone. Do not search\nthe web or inspect unrelated files when repository configuration is sufficient.\n\nResolve properties in the actual MSBuild import order, not with a fixed\n\"project beats props\" rule. For every applicable target framework:\n\n1. Follow the import graph and conditions. A later applicable assignment wins.\n   `Directory.Build.props` is normally imported before the project body, so an\n   unconditional project assignment normally overrides it; later `.targets`\n   can override the project again.\n2. Record the final value and its winning source for `UseVSTest`, the framework\n   runner selector, `TestingPlatformDotnetTestSupport`, and `OutputType`.\n3. Treat `Directory.Packages.props` as version evidence unless it also contains\n   relevant properties. Resolve package\u002FSDK versions before applying\n   version-dependent defaults.\n4. Never infer a property from package presence. A package or SDK default counts\n   only when that resolved version actually supplies it and no later assignment\n   overrides it.\n\n## Detecting the project system\n\nClassify the project before selecting a CLI:\n\n- Root `Sdk` attribute or `\u003CSdk>` declaration: SDK-style.\n- `ToolsVersion`, `Microsoft.Common.props` \u002F `Microsoft.CSharp.targets` imports,\n  explicit `\u003CReference>` and `\u003CCompile Include>` items: classic non-SDK.\n- `packages.config`: classic NuGet dependency management.\n\nClassic projects can still use VSTest-compatible adapters, but `dotnet test` is\nnot automatically a valid invocation. Preserve repository scripts\u002FCI commands,\ncommonly MSBuild followed by `vstest.console.exe`. Mention `MSTest.exe` only\nwhen repository configuration or documentation establishes that legacy runner.\n\n## Detecting the test framework\n\nRead the `.csproj`, adjacent `packages.config`, and\n`Directory.Build.props` \u002F `Directory.Packages.props` and look for:\n\n| Package or SDK reference | Framework |\n|--------------------------|-----------|\n| `MSTest` metapackage, `\u003CProject Sdk=\"MSTest.Sdk[\u002Fversion]\">`, or `\u003CSdk Name=\"MSTest.Sdk\">` | MSTest |\n| `MSTest.TestFramework` + `MSTest.TestAdapter` | MSTest (also valid for v3\u002Fv4) |\n| `xunit`, `xunit.v3`, `xunit.v3.mtp-v1`, `xunit.v3.mtp-v2`, `xunit.v3.core.mtp-v1`, `xunit.v3.core.mtp-v2` | xUnit |\n| `NUnit` + `NUnit3TestAdapter` | NUnit |\n| `TUnit` | TUnit (MTP only) |\n\nIn classic projects, package IDs and versions may appear only in\n`packages.config`, while the project contains assembly `\u003CReference>` elements\nwith `HintPath` values. Use both sources.\n\n## Detecting the executed test platform\n\nIf the user explicitly requests `dotnet test` mode, read\n[`references\u002Fcommand-mode.md`](references\u002Fcommand-mode.md) before answering.\nDo not load that reference or mention command mode for a\nplatform\u002Fframework-only request.\n\nFor an SDK 8\u002F9 request that explicitly asks about command mode and has no\neffective bridge, state all three facts in one causal sentence: the runner makes\nthe project MTP-capable, `dotnet test` remains in VSTest mode, and the missing\nbridge means VSTest actually executes the tests. Mention that native MTP command\nmode starts with SDK 10 only when it helps explain that result.\n\nWhen execution is permitted and neither the prompt nor `global.json` identifies\nthe SDK, run `dotnet --version` once. For read-only identification requests that\nprohibit execution, do not probe the installed SDK; use repository facts and\nstate any necessary SDK assumption.\n\nAfter resolving final property values, classify in this order:\n\n1. Final `UseVSTest=true` selects VSTest. If `global.json` simultaneously\n   selects native MTP command mode, report `Platform: unavailable` because the\n   command mode and project opt-out conflict.\n2. A native-MTP selection in `global.json` executes a compatible MTP\n   application with final `OutputType=Exe` on MTP. A VSTest-only,\n   library-output, or opted-out project is unavailable.\n3. On SDK 8\u002F9, an enabled MTP runner plus final\n   `TestingPlatformDotnetTestSupport=true` plus final `OutputType=Exe` executes\n   on MTP.\n4. On SDK 10+ in VSTest command mode, an MTP runner from\n   Microsoft.Testing.Platform 2.x (current TUnit brings it in transitively) is\n   unavailable. The `_MTPBeforeVSTest` target of Microsoft.Testing.Platform.MSBuild\n   fails the build (\"Testing with VSTest target is no longer supported by\n   Microsoft.Testing.Platform on .NET 10 SDK and later\") whatever\n   `TestingPlatformDotnetTestSupport` says, so no bridge executes it. Name the\n   remedy: `global.json` `\"test\": { \"runner\": \"Microsoft.Testing.Platform\" }`\n   selects native MTP mode (step 2).\n5. If the runner is enabled but the bridge is absent or false, a dual-capable\n   MSTest, NUnit, or xUnit project remains on VSTest: the runner establishes MTP\n   capability, but SDK 8\u002F9 `dotnet test` cannot reach it and the VSTest adapter\n   executes the tests instead. If the bridge is true but no runner is enabled,\n   the project also remains on VSTest.\n6. A runner and bridge with non-executable output is incomplete and unavailable.\n   An MTP-only framework that cannot be reached by the selected SDK path is also\n   unavailable, not VSTest.\n\nKeep each signal's role exact:\n\n- The runner property selects the test application.\n- `TestingPlatformDotnetTestSupport=true` lets SDK 8\u002F9 `dotnet test` reach that\n  application.\n- `OutputType=Exe` supplies the executable host shape. It does **not** select or\n  enable MTP.\n\nDo not confuse the `MSTest` metapackage with the `MSTest.Sdk` project SDK.\n`PackageReference Include=\"MSTest\"` plus `EnableMSTestRunner=true` enables the\nMSTest MTP runner, but it does **not** implicitly set\n`TestingPlatformDotnetTestSupport`.\n\nMSTest.Sdk enables the MTP runner by default. Check its resolved version and\nevaluated properties for bridge behavior: version 3.8 supplies\n`TestingPlatformDotnetTestSupport` unless a later assignment overrides it,\nwhile newer SDKs on .NET 10 may expect native MTP mode instead.\n`\u003CUseVSTest>true\u003C\u002FUseVSTest>` opts back into VSTest.\n\n| Signal | Meaning |\n|--------|---------|\n| `\u003CProject Sdk=\"MSTest.Sdk...\">` with no `UseVSTest` | MTP application; inspect the resolved SDK version and evaluated bridge property |\n| `MSTest` metapackage + `\u003CEnableMSTestRunner>true>` | MTP runner enabled; does not imply the VSTest-to-MTP bridge |\n| `\u003CUseMicrosoftTestingPlatformRunner>true` | Deciding xUnit runner-selection signal |\n| `\u003CEnableMSTestRunner>true>` \u002F `\u003CEnableNUnitRunner>true>` | Deciding MSTest\u002FNUnit runner-selection signal |\n| `TestingPlatformDotnetTestSupport=true` | Execution prerequisite for a VSTest-to-MTP bridge, not the runner-selection signal |\n| `Microsoft.Testing.Platform` package | MTP-capable application; not decisive by itself |\n| `TUnit` | MTP-only framework |\n| Final evaluated `\u003COutputType>Exe\u003C\u002FOutputType>` | Required executable host shape for package-based MTP applications |\n\n`Microsoft.NET.Test.Sdk` alone is not decisive; it can remain for compatibility\nin an MTP-enabled project. When an explicit override decides the result, name\nthe final override and its source, not the superseded default.\nWhen a runner-selection property competes with `Microsoft.NET.Test.Sdk`, say\nthat the runner property selects MTP and `Microsoft.NET.Test.Sdk` does **not**\nselect or imply VSTest. It may remain as compatibility support, but that is\nsecondary. `TestingPlatformDotnetTestSupport=true` is a bridge prerequisite, not\nthe runner-selection signal; never say that this property alone enables the\nbridge. For a request asking which single signal decides, stop there. Omit\nbridge or host-shape prerequisites when the configuration is complete, and add\nthem only when needed to explain why the selected runner cannot execute.\nLikewise, when an enabled runner is overridden or unreachable, state both axes\ncausally: the runner property makes the project MTP-capable, but the final\n`UseVSTest`\u002Fbridge\u002Foutput setting determines which platform actually executes.\nName the runner selector before using a package reference only to identify the\nframework.\n\nUse causal evidence, not a bag of signals. For example:\n\n```text\nPlatform: MTP\nFramework: NUnit\n\nDirectory.Build.props supplies final EnableNUnitRunner=true and\nTestingPlatformDotnetTestSupport=true, so NUnit executes on MTP.\n```\n\nFor an incompatible configuration, give one minimal alignment choice after the\nverdict without modifying files: either select the project's configured\nplatform globally or remove the project opt-out to use the globally selected\nplatform.\n\n### Conditional and per-target-framework properties\n\nEvaluate runner and bridge properties for each target framework. If conditions\nproduce different executed platforms, report each target explicitly (for\nexample, `net8.0: VSTest`, `net9.0: MTP`) rather than collapsing the project to\none global platform.\n",{"name":5,"description":7},"master","b30b1c1908dbc56a8184128f18803053d762ccb5","opencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.platform-detection",0,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins","https:\u002F\u002Fgithub.com\u002FBlind-Striker","denizirgin.com","VP of Engineering - \r\n@armutcom @homeruntech @prontopro\r\n |  Speaker \r\n@CodeFiction\r\n, http:\u002F\u002Fcodefiction.tech | Developer, gamer, blogger, maiden iron fan","2026-11-13 00:23:18",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.platform-detection",{"tool":39,"command":40},"bunx","bunx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.platform-detection",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Blind-Striker\u002Fagent-skills-and-plugins --skill deniz-dotnet-general.platform-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.platform-detection\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fcommand-mode.md","REFERENCE","参考文档",1198,"https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fopencode\u002Fdeniz-dotnet-general\u002Fskills\u002Fdeniz-dotnet-general.platform-detection\u002Freferences\u002Fcommand-mode.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79YGWBJ52PHMSTKJ3RJ3AWR","writing-tunit-tests","Write tests in TUnit — the attributes, the async assertion model, data-driven cases, lifecycle hooks, and the parallelism rules. USE FOR writing or fixing a test in a TUnit project, translating a test idea into TUnit syntax, or reviewing TUnit test code for API mistakes. DO NOT USE FOR deciding what to test, judging whether a test is any good, or running tests.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fwriting-tunit-tests\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79YGR3Y9RCRS6TD71D0KKP8","dotnet-walls","Walls for a .NET change in a repository without its own quality gates — pinned, ephemeral analyzer, format, clone and scanner commands for the verify step, their identity ratchet, and the build traps. Use during a walls preflight, or when a worker's verify step needs .NET quality gates.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fdotnet-walls\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79YGFNJBST7D803NQW3SBYM","csharp-15","Write, review and modernize C# 15 (.NET 11) code correctly. Covers every C# 15 feature - collection expression arguments (`[with(...), ...]`), union types (`union`, `[Union]`, `IUnion`, custom unions), closed class hierarchies (`closed`), extension indexers, labeled `break`\u002F`continue`, non-virtual static interface members on runtimes without default interface methods, and the preview memory-safety model (`unsafe(expr)`, `safe`, requires-unsafe members). Use when code targets net11.0 or LangVersion 15\u002Fpreview, when the user mentions any of these features, when replacing marker interfaces, OneOf-style results, `goto`\u002Fflag loop exits or capacity\u002Fcomparer boilerplate, or when the build reports CS8121, CS8509, CS8655, CS8510, CS0121\u002FCS0411 on a `with(...)` element, CS9370, CS9380 or CS9363.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-dotnet-general\u002Fcsharp-15\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79YGAV031473HSX6FN87ENH","verified-waves","Run one task as verified multi-agent waves. Plans the fan-out, sends findings to fresh skeptics, keeps a ledger, and reports N of M done; small tasks stay solo.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fverified-waves\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79YG6QXNND4WRPP3GATSY8J","harness","The bundled dispatch harness, which runs a task file on worker models through OpenCode or Codex, fences their writes, escalates their asks to the operator, settles each result from git and its verify commands, and records every step in a ledger. Its commands, task file, modes and write fence, configuration, runs and their recovery, ledger and exit codes.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fharness\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79YG2P5S91SDTA5912XJ4FV","delegating-to-worker-models","Use when you hand off implementation, a plan, research a decision will rely on, or a review, and you brief the worker and check what comes back. A subagent that searches, reads in parallel, or keeps your context small is ordinary tool use. Covers what stays with you, the mechanism, assigning work by strength, the walls preflight, prompts without contradictions, the worker contract and model profiles, evidence from your own run, review, and the fix-up loop.","https:\u002F\u002Fgithub.com\u002FBlind-Striker\u002Fagent-skills-and-plugins\u002Fblob\u002Fmaster\u002Fskills\u002Fdeniz-coordination\u002Fdelegating-to-worker-models\u002FSKILL.md",[],[]]