dotnet-nuget-authoring

Create and validate NuGet packages for .NET libraries with MSBuild properties and tasks.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-nuget-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-nuget-authoring
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-nuget-authoring
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-nuget-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating robust, versioned, and secure NuGet packages for .NET libraries, ensuring they are ready for distribution and consumption by other developers.

Core Features & Use Cases

  • SDK-Style Project Packaging: Configure .csproj files for automatic NuGet package generation.
  • Source Generator Packaging: Correctly package Roslyn source generators and analyzers.
  • Multi-Targeting: Build packages compatible with multiple .NET TFM versions.
  • Symbol & Signing: Enable symbol packages for debugging and sign packages for authenticity.
  • Package Validation: Ensure API compatibility and catch issues before publishing.
  • Use Case: You've developed a new C# library and need to publish it to NuGet. This Skill guides you through setting up your project, including metadata, versioning, and validation, to create a high-quality package.

Quick Start

Configure your .NET project to create a NuGet package with all necessary metadata and validation enabled.

Frequently Asked Questions about dotnet-nuget-authoring

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

FAQPage Schema
How do I package a .NET library for NuGet distribution using an SDK-style csproj?

You package a .NET library for NuGet distribution by configuring SDK-style csproj files with MSBuild properties and tasks that handle metadata, versioning, and validation for reusable code components.

How do I correctly package a Roslyn source generator for NuGet?

Correctly packaging a Roslyn source generator for NuGet requires specific SDK-style csproj configurations to ensure analyzers and source generators are properly included in the distributed package.

How can I validate API compatibility before publishing a NuGet package?

You validate API compatibility before publishing a NuGet package by utilizing MSBuild package validation tasks to catch breaking changes and ensure cross-version compatibility during the build process.

Does NuGet packaging support multi-targeting for different .NET framework versions?

NuGet packaging supports multi-targeting by configuring your SDK-style csproj with multiple Target Framework Monikers (TFMs), ensuring the distributed package is compatible across different .NET versions.

How do I generate symbol packages and sign a NuGet package for authenticity?

To generate symbol packages and sign a NuGet package for authenticity, configure MSBuild properties in your SDK-style csproj to enable symbol generation for debugging and apply cryptographic signing.