dotnet-nuget-authoring

Create and manage NuGet packages for .NET libraries with SDK-style configurations.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-nuget-authoring-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-nuget-authoring
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-nuget-authoring
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-nuget-authoring-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating, validating, and signing NuGet packages for .NET libraries, ensuring professional and reliable distribution to consumers.

Core Features & Use Cases

  • SDK-Style Packaging: Configure .csproj files for automatic NuGet package generation.
  • Source Generator Packaging: Correctly package Roslyn source generators and analyzers.
  • Multi-TFM Support: Build packages compatible with multiple .NET target frameworks.
  • Symbol & Signing: Generate symbol packages and implement package signing for security and debugging.
  • Validation: Ensure package quality and API compatibility before publishing.
  • Use Case: You've developed a new C# library and need to publish it as a NuGet package. This Skill guides you through setting up your project, including metadata, multi-targeting, and preparing it for release.

Quick Start

Configure your SDK-style .NET project to include package metadata like ID, version, authors, description, and license.

Frequently Asked Questions about dotnet-nuget-authoring

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

FAQPage Schema
How do I configure an SDK-style csproj file to generate a NuGet package?

Configure your SDK-style csproj file by adding package metadata properties like ID, version, authors, description, and license to enable automatic NuGet package generation for your .NET library.

How do I package Roslyn source generators and analyzers for NuGet distribution?

Packaging Roslyn source generators requires specific SDK-style project configurations to ensure the analyzer assemblies are correctly included. This process guarantees the source generators function properly when consumers install the NuGet package.

Can I build a NuGet package that supports multiple .NET target frameworks?

Yes, you can build a single NuGet package supporting multiple .NET target frameworks. Multi-TFM support configures your SDK-style project to compile for various .NET runtimes, ensuring broad compatibility for consumers.

What is the process for adding package signing and symbol packages to a .NET library?

Adding package signing and generating symbol packages enhances security and debugging. You implement these through SDK-style project configurations to ensure your NuGet package is reproducible, secure, and provides source debugging capabilities.

How does API validation ensure NuGet package quality before publishing?

API validation ensures package quality and API compatibility before publishing. By verifying the public API surface, you guarantee your .NET library maintains reproducible and compatible standards across various .NET runtimes.

When do I need to generate symbol packages for my .NET library?

You need to generate symbol packages when providing source debugging capabilities for your .NET library consumers. This ensures your NuGet package distribution includes the necessary debugging symbols alongside the compiled assemblies.