How do I install the Dotnet Package skill?

Run npx skillmds@latest add tomevault-io/dotnet-package in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dotnet Package safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dotnet Package?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dotnet Package free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dotnet Package?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dotnet Package by tomevault-io — Agent Skill

Name: Dotnet Package
Author: tomevault-io

Dotnet Package

Manage NuGet packages using dotnet CLI commands. Use when adding, removing, or updating packages in .NET projects. Never edit .csproj or Directory.Packages.props files directly. Use when this capability is needed.

tomevault-io e006c2f 2 files · 3.4 KB Updated Sep 17, 2026

File contents

dotnet-package Skill

Core Rules

NEVER directly edit .csproj, .props, or Directory.Packages.props files
ALWAYS use dotnet CLI commands for all package operations
VERIFY changes with dotnet restore or dotnet build

Commands

Add Package

dotnet add [<PROJECT>] package <PACKAGE_NAME> [--version <VERSION>]

Latest version (no --version flag):

dotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Aspire.Hosting.Kafka

Specific version:

dotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Testcontainers --version 3.7.0

Remove Package

dotnet remove [<PROJECT>] package <PACKAGE_NAME>

Example:

dotnet remove tests/Microcks.Aspire.Tests/Microcks.Aspire.Tests.csproj package Refit

Update Package

Use dotnet add package with --version to update existing packages:

dotnet add <PROJECT> package <PACKAGE_NAME> --version <VERSION>

When version not specified, find latest:

LATEST_VERSION=$(dotnet package search <PACKAGE_NAME> --exact-match --format json | jq -r '.searchResult[].packages[0].version')
dotnet add <PROJECT> package <PACKAGE_NAME> --version $LATEST_VERSION

Verify Changes

Always verify after operations:

dotnet restore
# or
dotnet build

Examples

Add latest version:

dotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Aspire.Hosting.Redis

Add specific version:

dotnet add tests/Microcks.Aspire.Testing/Microcks.Aspire.Testing.csproj package Aspire.Hosting.Testing --version 9.1.0

Update to specific version:

dotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Testcontainers --version 3.9.0
dotnet restore

Update to latest version:

LATEST_VERSION=$(dotnet package search Aspire.Hosting.Kafka --exact-match --format json | jq -r '.searchResult[].packages[0].version')
dotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Aspire.Hosting.Kafka --version $LATEST_VERSION
dotnet restore

Remove package:

dotnet remove tests/Microcks.Aspire.Tests/Microcks.Aspire.Tests.csproj package Refit

Notes

Central Package Management (Directory.Packages.props) is handled automatically by the CLI
dotnet add package without --version uses latest stable version
Failures leave project files unchanged, ensuring integrity

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: dotnet-packagedescription: Manage NuGet packages using dotnet CLI commands. Use when adding, removing, or updating packages in .NET projects. Never edit .csproj or Directory.Packages.props files directly. Use when this capability is needed.---# dotnet-package Skill## Core Rules1. **NEVER** directly edit `.csproj`, `.props`, or `Directory.Packages.props` files2. **ALWAYS** use `dotnet` CLI commands for all package operations3. **VERIFY** changes with `dotnet restore` or `dotnet build`## Commands### Add Package```bashdotnet add [<PROJECT>] package <PACKAGE_NAME> [--version <VERSION>]```**Latest version** (no --version flag):```bashdotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Aspire.Hosting.Kafka```**Specific version**:```bashdotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Testcontainers --version 3.7.0```### Remove Package```bashdotnet remove [<PROJECT>] package <PACKAGE_NAME>```Example:```bashdotnet remove tests/Microcks.Aspire.Tests/Microcks.Aspire.Tests.csproj package Refit```### Update PackageUse `dotnet add package` with `--version` to update existing packages:```bashdotnet add <PROJECT> package <PACKAGE_NAME> --version <VERSION>```**When version not specified**, find latest:```bashLATEST_VERSION=$(dotnet package search <PACKAGE_NAME> --exact-match --format json | jq -r '.searchResult[].packages[0].version')dotnet add <PROJECT> package <PACKAGE_NAME> --version $LATEST_VERSION```### Verify ChangesAlways verify after operations:```bashdotnet restore# ordotnet build```## Examples**Add latest version:**```bashdotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Aspire.Hosting.Redis```**Add specific version:**```bashdotnet add tests/Microcks.Aspire.Testing/Microcks.Aspire.Testing.csproj package Aspire.Hosting.Testing --version 9.1.0```**Update to specific version:**```bashdotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Testcontainers --version 3.9.0dotnet restore```**Update to latest version:**```bashLATEST_VERSION=$(dotnet package search Aspire.Hosting.Kafka --exact-match --format json | jq -r '.searchResult[].packages[0].version')dotnet add src/Microcks.Aspire/Microcks.Aspire.csproj package Aspire.Hosting.Kafka --version $LATEST_VERSIONdotnet restore```**Remove package:**```bashdotnet remove tests/Microcks.Aspire.Tests/Microcks.Aspire.Tests.csproj package Refit```## Notes- Central Package Management (`Directory.Packages.props`) is handled automatically by the CLI- `dotnet add package` without `--version` uses latest stable version- Failures leave project files unchanged, ensuring integrity---> Converted and distributed by [TomeVault](https://tomevault.io/claim/microcks) — claim your Tome and manage your conversions.

Frequently asked questions