What problem does it solve? The correct dotnet test syntax depends on the test platform (VSTest vs Microsoft.Testing.Platform), the test framework (MSTest, xUnit, NUnit, TUnit), and the SDK version, and getting it wrong produces unrecognized-flag errors or silently skipped tests. This Skill detects the setup and produces the exact command, including the -- separator rules and platform-specific filter syntax. ## Core Features & Use Cases - Platform and framework detection: Inspects global.json, .csproj, Directory.Build.props, and Directory.Packages.props to determine VSTest vs MTP and MSTest/xUnit/NUnit/TUnit. - Correct command generation: Applies SDK-version rules such as the -- separator on SDK 8/9, direct MTP args on SDK 10+, --logger trx vs --report-trx, and --blame vs --blame-crash/--blame-hang-timeout. - Filtered test runs: Translates requests like "run the integration tests" into the right filter (--filter, --filter-class, --filter-trait, --filter-query, --treenode-filter) for the detected framework. - Use Case: A user asks to run only the smoke tests in a multi-TFM xUnit v3 project on .NET 10; the Skill detects MTP from global.json and produces dotnet test --project <path> --framework net10.0 --filter-trait "Category=Smoke". ## Quick Start Ask the assistant to run the tests in your .NET project, optionally naming a specific class, category, or target framework to filter.