dotnet-cli-packaging

Package .NET CLI tools for Homebrew, apt, winget, Scoop, and Chocolatey.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-cli-packaging-rudironsoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-cli-packaging
Source: https://github.com/rudironsoni/dotnet-agent-harness/tree/main/.rulesync/skills/dotnet-cli-packaging
Command: npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-cli-packaging-rudironsoni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of packaging .NET CLI tools for distribution across various package managers, ensuring your tools are easily accessible to users on different platforms.

Core Features & Use Cases

  • Multi-Platform Packaging: Supports Homebrew, apt/deb, winget, Scoop, and Chocolatey.
  • dotnet tool & NuGet: Facilitates packaging as .NET global or local tools and distribution via NuGet.
  • Use Case: You've developed a new .NET CLI tool and need to make it available to macOS users via Homebrew, Windows users via winget, and other .NET developers via dotnet tool install. This Skill provides the guidance to create the necessary manifests and packages for each.

Quick Start

Use the dotnet-cli-packaging skill to create a Homebrew formula for your tool.

Frequently Asked Questions about dotnet-cli-packaging

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

FAQPage Schema
How do I package a .NET CLI tool for distribution across multiple platforms?

To package a .NET CLI tool for distribution, you create manifests and packages for target package managers like Homebrew, winget, and NuGet. This ensures cross-platform accessibility for your CLI application.

Can I distribute a dotnet tool using Homebrew and winget?

Yes, you can distribute a dotnet tool using Homebrew and winget. You need to generate the specific Homebrew formula for macOS and the winget manifest for Windows to support both platforms.

What is the best way to make a .NET CLI application available to other developers via NuGet?

The best way to make a .NET CLI application available via NuGet is to package it as a .NET global or local tool. This allows developers to install it directly using the dotnet tool install command.

Which package managers are supported for packaging .NET CLI tools?

Supported package managers for .NET CLI tools include Homebrew, apt/deb, winget, Scoop, and Chocolatey. This allows you to target macOS, Linux, and Windows environments within a single distribution workflow.

Do I need to create separate packages for Linux users when distributing a dotnet tool?

Yes, you need to create separate packages for Linux users, specifically apt/deb packages. Creating these packages ensures your .NET CLI tool is accessible to users on Debian-based Linux distributions.

When should I package my .NET CLI application as a global tool instead of using Chocolatey or Scoop?

You should package your .NET CLI application as a global tool when targeting .NET developers using the dotnet tool install command. Use Chocolatey or Scoop when distributing to general Windows users who rely on those system package managers.