Agent skill · software engineering · github
nuget-manager
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.
Why this skill is useful
Adds specific commands and workflows for managing NuGet packages that the AI wouldn't reliably generate on its own.
What it needs
Requires dotnet, jq installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
NuGet Manager Overview This skill ensures consistent and safe management of NuGet packages across .NET projects. It prioritizes using the dotnet CLI to maintain project integrity and enforces a strict verification and restoration workflow for version updates. Prerequisites .NET SDK installed (typically .NET 8.0 SDK or later, or a version compatible with the target solution). dotnet CLI available on your PATH. jq (JSON processor) OR PowerShell (for version verification using dotnet package search). Core Rules 1. NEVER directly edit .csproj, .props, or Directory.Packages.props files to add or remove packages. Always use dotnet add package and dotnet remove package commands. 2. DIRECT EDITING is ONLY permitted for changing versions of existing packages. 3. VERSION UPDATES must follow the mandatory workflow: Verify the target version exists on NuGet. Determine if versions are managed per-project (.csproj) or centrally (Directory.Packages.props). Update the version string in the appropriate file. Immediately run dotnet restore to verify compatibility. Workflows Adding a Package Use dotnet add [<PROJECT>] package <PACKAGENAME> [--version <VERSION>]. Example: dotnet add src/MyProject/MyProject.csproj package Newtonsoft.Json Removing a Package Use dotnet remove [<PROJECT>] package <PACKAGENAME>. Example: dotnet remove src/MyProject/MyProject.csproj package Newtonsoft.Json Updating Package Versions When updating a version, follow these steps: 1. Verify Version Existence: Check if the version exists using the dotnet package search command with exact match and JSON formatting. Using jq: dotnet package search <PACKAGENAME> --exact-match --format json jq -e '.searchResult[].packages[] select(.version == "<VERSION>")' Using PowerShell: (dotnet package search <PACKAGENAME> --exact-match --format json ConvertFrom-Json).searchResult.packages Where-Object { $.version -eq "<VERSION>" } 2. Determine Version Management: Search for Directory.Packages.props in the solution root. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/nuget-manager