What problem does it solve? Publishing NuGet packages with long-lived API keys creates security risks from leaked or stale secrets that must be manually rotated. This Skill replaces those keys with OIDC-based short-lived tokens via NuGet trusted publishing, guiding the full setup on GitHub Actions repos. ## Core Features & Use Cases - Repo Assessment: Classifies packable projects (library, dotnet tool, MCP server, template) by inspecting .csproj and Directory.Build.props, then validates required properties and version consistency. - Guided nuget.org Policy Setup: Walks the user through creating a trusted publishing policy with the exact repository owner, repo name, and workflow filename, plus an optional GitHub Environment for secret scoping. - Workflow Creation and Migration: Generates a tag-triggered publish workflow using NuGet/login@v1 with id-token: write, or migrates an existing API-key workflow in place. - Use Case: A maintainer wants to remove secrets.NUGET_API_KEY from their repo. The Skill inspects the project, guides the nuget.org policy creation, rewrites the publish workflow to use OIDC tokens, and provides troubleshooting for common failures like 403 errors or filename mismatches. ## Quick Start Set up NuGet trusted publishing with OIDC for my GitHub Actions repo and migrate my publish workflow away from API keys.
