What problem does it solve? Managing NuGet packages across multi-project .NET solutions often leads to version conflicts, inconsistent dependency versions, and error-prone manual XML edits. This Skill provides CLI-first workflows and Central Package Management patterns to keep dependencies consistent and auditable. ## Core Features & Use Cases - CLI-First Package Operations: Add, remove, list, and update packages using dotnet CLI commands instead of editing .csproj XML directly. - Central Package Management (CPM): Set up Directory.Packages.props with shared version variables so related packages like Akka.NET or Aspire stay on synchronized versions. - Troubleshooting & Governance: Diagnose version conflicts, restore failures, and vulnerable or deprecated packages, with guidance on lock files and private feeds. - Use Case: When adding Serilog to a solution with CPM enabled, run dotnet add package Serilog so the version lands in Directory.Packages.props and the reference lands in the project file automatically. ## Quick Start Ask the assistant to add a specific NuGet package to your .NET project using Central Package Management and the dotnet CLI.