nuget-trusted-publishing

Automate NuGet trusted publishing setup with GitHub Actions and OIDC.

Updated May 28, 2026
One-click install
npx skills add https://github.com/ojrojas/AgentsInstructions --skill nuget-trusted-publishing-ojrojas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nuget-trusted-publishing
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet/skills/nuget-trusted-publishing
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill nuget-trusted-publishing-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires GitHub Actions, NuGet.org account, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the issue of securely setting up NuGet trusted publishing on GitHub Actions, replacing traditional API keys with OIDC-based tokens for secure, keyless NuGet publishing.

Core Features & Use Cases

  • NuGet Trusted Publishing Setup: Guide users through setting up NuGet trusted publishing using GitHub Actions and OIDC.
  • API Key Replacement: Migrate from long-lived API keys to short-lived tokens for enhanced security.
  • Use Case: A developer needs to publish a NuGet package with secure publishing credentials, without relying on API keys.

Quick Start

Use the nuget-trusted-publishing skill to set up NuGet trusted publishing on your GitHub Actions workflow.

Frequently Asked Questions about nuget-trusted-publishing

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

FAQPage Schema
How do I set up NuGet trusted publishing with GitHub Actions and OIDC?

To set up NuGet trusted publishing, you configure GitHub Actions workflows to use OIDC for generating short-lived tokens, replacing traditional API keys for secure, keyless package publishing to NuGet.org.

What is OIDC-based trusted publishing for NuGet packages?

OIDC-based trusted publishing is a security mechanism that uses short-lived tokens generated via GitHub Actions to authenticate package publishing to NuGet.org, eliminating the need to store long-lived API keys.

How do I migrate my NuGet package publishing away from API keys?

You can migrate away from API keys by configuring trusted publishing policies on your NuGet.org account and updating your GitHub Actions CI/CD pipeline to request OIDC tokens for keyless authentication.

Do I need a NuGet.org account with trusted publishing policies configured to use this?

Yes, you must have a NuGet.org account with trusted publishing policies configured and an active GitHub Actions workflow environment to successfully automate keyless package publishing.

Why should I use OIDC tokens instead of API keys for NuGet publishing?

You should use OIDC tokens instead of API keys to enhance security by replacing long-lived credentials with short-lived tokens, reducing the risk of key leakage in your CI/CD pipelines.