What problem does it solve? The correct dotnet test syntax depends on the test platform (VSTest vs Microsoft.Testing.Platform), the SDK version, and the test framework, and getting it wrong produces unrecognized-flag errors or silently skipped tests. This Skill detects the environment and produces the exact command, flags, and filter syntax for the project. ## Core Features & Use Cases - Platform and framework detection: Inspects global.json, .csproj, Directory.Build.props, and Directory.Packages.props to identify VSTest vs MTP and MSTest, xUnit, NUnit, or TUnit. - Correct command generation: Handles the -- separator requirement on SDK 8/9 versus direct MTP arguments on SDK 10+, plus TRX reporting, crash/hang dumps, and code coverage flags per platform. - Filtered test runs: Translates requests like "run the integration tests" into the right filter (--filter, --filter-trait, --filter-query, --treenode-filter) for the detected framework. - Use Case: A user asks to run only smoke tests in a multi-TFM xUnit v3 project on .NET 9; the Skill detects MTP via TestingPlatformDotnetTestSupport and emits dotnet test --framework net9.0 -- --filter-trait "Category=Smoke". ## Quick Start Ask the assistant to run the integration tests in your .NET project and it will detect the platform and emit the correct dotnet test command.