PlugWiki

nuget-manager skill: manage NuGet packages with the dotnet CLI

Makes your agent add, remove and update NuGet packages through the dotnet CLI instead of editing project files.

Installs
14.4K
on skills.sh
Stars
40.7K
on GitHub
Updated
Oct 2026
last repo commit

This skill makes your agent use dotnet add package and dotnet remove package to add or remove NuGet packages, and never edit .csproj or props files for that. A direct file edit is allowed only to change the version of a package that is already there.

For a version update the agent verifies the version exists on NuGet, finds whether versions live in the project or in Directory.Packages.props, makes the edit, and runs dotnet restore. If restore fails it reverts. It needs the .NET SDK and jq or PowerShell.

Good for

  • .NET developers who want package changes done the safe way
  • Teams using central package management in Directory.Packages.props
  • Anyone bumping a package version across a solution

Install nuget-manager

Claude Code

  1. 1

    Copy this prompt.

    Install the nuget-manager skill in Claude Code. Run this command:
    
    npx skills add https://github.com/github/awesome-copilot --skill nuget-manager
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Manage NuGet packages in .NET projects/solutions. Use this skill when adding, removing, or updating NuGet package versions. It enforces using `dotnet` CLI for package management and provides strict procedures for direct file edits only when updating versions.

Sections in SKILL.md

  1. Overview
  2. Prerequisites
  3. Core Rules
  4. Workflows
  5. Adding a Package
  6. Removing a Package
  7. Updating Package Versions
  8. Examples
  9. User: "Add Serilog to the WebApi project"
  10. User: "Update Newtonsoft.Json to 13.0.3 in the whole solution"

Key facts

Installs on skills.sh
14,419 as of 2 Nov 2026
Last commit in the repo
2026-10-30

What it includes

  • CLI to add or remove; direct edits only to change versions

    Never hand-edit .csproj, .props or Directory.Packages.props to add or remove a package. Version changes follow a fixed four-step workflow.

    Read · Core rules

  • dotnet add [PROJECT] package NAME [--version V]

    Adds the package to the named project through the CLI.

    Try: “Add Serilog to the WebApi project.”

    Runs code · Add a package

  • dotnet remove [PROJECT] package NAME

    Removes the package through the CLI.

    Runs code · Remove a package

  • Verify, locate, edit, then dotnet restore

    Checks the version exists with dotnet package search --exact-match --format json (parsed with jq or PowerShell), decides between per-project and central versions, edits the version string, and runs dotnet restore. On errors it reverts the change.

    Try: “Update Newtonsoft.Json to 13.0.3 across the whole solution.”

    Runs code · Update a version

From the official docs

Permissions

Low risk

The agent edits your project and props files and runs dotnet commands that contact NuGet. Commit your work first so you can review the diff.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It changes project files

    Adds, removes and version edits alter your .csproj or Directory.Packages.props. Review the diff before committing. github.com

  • Third-party content from a community collection

    The awesome-copilot README says its customizations come from third-party developers and asks you to inspect them before installing. Read the SKILL.md first. github.com

Technical details
Turning on read-onlyThe SKILL.md defines no read-only switch.
Talks toNuGet, for package search and restore
Scopes
  • Runs dotnet add package, dotnet remove package, dotnet package search and dotnet restore

  • Edits the version in .csproj or Directory.Packages.props

  • Runs jq or a PowerShell snippet to read search results

Questions

What does the nuget-manager skill do?

It makes your agent manage NuGet packages in .NET projects with the dotnet CLI for adds and removes, and a checked, restore-verified edit for version changes.

How do I install it?

Use the install box on this page. It is a single SKILL.md, so adding the skill folder is the whole install. Your machine needs the .NET SDK, and jq or PowerShell for the version check.

Why does it refuse to edit my .csproj?

By its core rules, packages are added and removed only with the dotnet CLI. Editing the file by hand is allowed only to change the version of a package that is already referenced.

Does it handle central package management?

Yes. It looks for Directory.Packages.props in the solution root. If found, it edits the PackageVersion entry there. Otherwise it edits the PackageReference version in the .csproj.

Is it safe to run?

It edits project files and runs dotnet commands that reach NuGet. If restore fails, the skill tells it to revert the edit. Commit your work first so you can undo anything else.

Information

updated Nov 2, 2026

Folder
skills/nuget-manager

github/awesome-copilotskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 2
  1. nuget-manager SKILL.md · github.com
  2. awesome-copilot README · github.com

Updated Nov 2, 2026.