菜单
Safe NuGet package management rules for .NET projects. Enforces using dotnet CLI commands instead of manually editing .csproj files.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Self-contained CatHerder method and standards for plans and tasks: planning vs execution, execution loop, prompt precedence, persistence; plus prompt/spec/implementation/review/follow-up files, frontmatter, statuses, timestamps, the open-questions gate, and validation. Use when planning, creating, reviewing, executing, or validating planNNN folders, or fixing plan/task format drift.
Defines standards and best practices for authoring Agent Skill folders and SKILL.md files (frontmatter, descriptions/triggers, progressive disclosure, references/scripts/assets, and validation with skills-ref). Use when creating a new skill, reviewing or validating an existing skill, fixing skill discovery issues, or deciding what belongs in SKILL.md vs references/ vs scripts/. Use when user or you want to run skills-ref validation on a skill folder.
Use this skill when building applications with Gemini models, Gemini API, working with multimodal content (text, images, audio, video), implementing function calling, using structured outputs, or needing current model specifications. Covers SDK usage (google-genai for Python, @google/genai for JavaScript/TypeScript, com.google.genai:google-genai for Java, google.golang.org/genai for Go), model selection, and API capabilities.
| name | nuget-manager |
| description | Safe NuGet package management rules for .NET projects. Enforces using dotnet CLI commands instead of manually editing .csproj files. |
| user-invocable | false |
Safely manage NuGet packages in .NET projects.
Prevent common mistakes when adding, removing, or updating NuGet packages. The dotnet CLI is the only safe way to modify package references.
.csproj to Add or Remove Packages<PackageReference> elements to .csproj files<PackageReference> elements from .csproj filesdotnet add package and dotnet remove package CLI commandsWhen updating a package version that already exists:
dotnet package search <name> --exact-match --format json.csproj, Directory.Packages.props, or Directory.Build.props)dotnet restoredotnet builddotnet add <project.csproj> package <PackageName>
dotnet add <project.csproj> package <PackageName> --version <version>
dotnet remove <project.csproj> package <PackageName>
dotnet list <project.csproj> package
dotnet list <project.csproj> package --outdated
dotnet package search <name> --exact-match --format json
dotnet restore
1. Verify version exists
└─> dotnet package search Newtonsoft.Json --exact-match --format json
2. Check management location
└─> Is version in .csproj? Directory.Packages.props? Directory.Build.props?
3. Update the version string in the correct file
4. Restore and verify
└─> dotnet restore && dotnet build
| Mistake | Why It's Wrong | Correct Approach |
|---|---|---|
Edit .csproj to add package | May miss transitive dependencies, won't update lock file | dotnet add package |
Edit .csproj to remove package | May leave orphan transitive deps | dotnet remove package |
| Update version without verifying | Version may not exist on feed | dotnet package search first |
Skip dotnet restore after changes | Build will fail with missing refs | Always restore after changes |
This skill applies when:
.csproj, .fsproj, or centrally manageddotnet CLI is availableFor non-.NET projects, use the appropriate package manager:
npm install / npm uninstallpip install / pip uninstall