What problem does it solve? Migrating .NET test projects from VSTest to Microsoft.Testing.Platform (MTP) involves many framework-specific configuration changes, CLI argument translations, and CI/CD updates that are easy to get wrong, such as mixing VSTest and MTP projects or hitting unexpected exit code 8 failures. ## Core Features & Use Cases - Runner Enablement: Configures the correct MTP opt-in property for MSTest (EnableMSTestRunner or MSTest.Sdk), NUnit (EnableNUnitRunner), xUnit.net v2 (YTest.MTP.XUnit2), and xUnit.net v3 (UseMicrosoftTestingPlatformRunner). - CLI Argument Translation: Converts VSTest arguments like --logger trx, --blame, and --collect into MTP equivalents, including xUnit.net v3 filter migration to --filter-class, --filter-trait, and --filter-query. - CI/CD and Config Updates: Updates Azure DevOps and GitHub Actions pipelines, configures global.json or TestingPlatformDotnetTestSupport based on SDK version, and centralizes settings in Directory.Build.props. - Use Case: A team with a solution of MSTest and xUnit projects wants to adopt MTP for Native AOT test execution; this Skill walks through assessment, runner setup, argument translation, pipeline updates, and verification. ## Quick Start Migrate the test projects in my solution from VSTest to Microsoft.Testing.Platform and update the CI pipeline accordingly.