package-management

Manage NuGet packages in .NET projects via the dotnet CLI with Central Package Management.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/bbsbot/mac-md-win --skill package-management-bbsbot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package-management
Source: https://github.com/bbsbot/mac-md-win/tree/main/.claude/skills/dotnet/skills/package-management
Command: npx skills add https://github.com/bbsbot/mac-md-win --skill package-management-bbsbot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of NuGet packages in .NET projects, preventing version conflicts and simplifying updates through Central Package Management (CPM) and the dotnet CLI.

Core Features & Use Cases

  • Centralized Versioning: Use CPM to define package versions in a single file (Directory.Packages.props).
  • CLI-Driven Operations: Add, remove, and list packages using dotnet commands, avoiding direct XML edits.
  • Version Variables: Group related packages under shared version variables for easy, consistent updates.
  • Use Case: When adding a new logging library to a solution with multiple projects, use this Skill to add the package via dotnet add package and ensure its version is managed centrally.

Quick Start

Use the package-management skill to add the 'Serilog.Sinks.Console' package to your project.

Frequently Asked Questions about package-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage NuGet package versions across multiple .NET projects?

Central Package Management defines NuGet versions in a single Directory.Packages.props file to ensure consistent versions across solutions. This avoids conflicts and simplifies updates by treating dependencies centrally.

What is the best way to add a NuGet package without causing XML errors?

The best way to add NuGet packages is using dotnet CLI commands. The package-management Skill ensures all operations use the CLI to maintain file integrity and avoid manual XML errors.

Can I group related .NET dependencies under a shared version variable?

Yes, Central Package Management supports shared version variables. Grouping related dependencies under these variables allows consistent, centralized version updates across the entire solution.

Does Central Package Management work with the dotnet CLI?

Central Package Management works directly with the dotnet CLI. You can add, remove, and list packages using CLI commands while maintaining centralized versioning rules.

Why should I use Central Package Management instead of editing csproj files directly?

Central Package Management prevents version conflicts and manual XML errors by defining versions in Directory.Packages.props. It replaces direct edits with CLI commands to maintain project integrity.