Create NuGet Package Skill
haiilong/create-nuget-package-skill
Scaffolding automático de repos NuGet .NET production-ready
Ver no GitHubSkill para Claude que scaffolda repositórios completos de pacotes .NET NuGet prontos para publicação. Gera estrutura multi-targeted (net8.0, net10.0), testes com xUnit, documentação, CI/CD com GitHub Actions e suporte a SourceLink e AOT a partir de nome e descrição.
Instalação
npx convez-ai haiilong/create-nuget-package-skill1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Criar novos pacotes NuGet com estrutura padrão e conventions
- Bootstrapar bibliotecas .NET com testes, docs e CI/CD pré-configurados
- Gerar projetos multi-targeted com suporte a AOT e source generators
- Automatizar setup inicial de pacotes para publicação em nuget.org
Veredito

Skill sólido e bem-documentado que automatiza todo o boilerplate de um pacote NuGet moderno. Ideal para desenvolvedores .NET que querem criar bibliotecas sem perder tempo com configuração inicial, com conventions sensatas e CI/CD OIDC pronto.
README
A tradução para o português deste README ainda está na fila.
create-nuget-package
A Claude Code skill that scaffolds a complete, publish-ready .NET NuGet package
repository from a small set of inputs (package name + description). It mirrors the
conventions of the CloudHttp, RefreshAhead.MemoryCache, and SingletonJob
packages that you can find in my repositories.
What it does
Given a package name and a one-line description, it generates a full repo:
- Multi-targeted library (
net8.0;net10.0) with complete NuGet packaging metadata, symbol packages (.snupkg), SourceLink, XML docs, and AOT/trim flags. .slnxsolution (modern XML format) with/samples/and/tests/folders.- xUnit + FluentAssertions test project (v2 by default, v3 optional).
- Sample project with an optional
Dockerfile/docker-compose.yml. docs/folder (index + getting-started).- CHANGELOG.md (Keep a Changelog + SemVer), README.md with badges, MIT LICENSE.
- Dotfiles:
.editorconfig,.gitignore,.gitattributes. - GitHub Actions:
ci.yml(build/test on PR) andrelease.yml(tag-driven, OIDC-based publish to nuget.org — no API key). - Optional AOT-safe Roslyn source generator, wired into the package's
analyzers/dotnet/csfolder.
How to invoke
In Claude Code, just describe the intent:
"Create a new NuGet package repo" "Bootstrap a .NET library called Acme.Widgets"
or call it directly: /create-nuget-package
The skill asks for the package name and description, applies sensible defaults for
everything else, scaffolds the repo, runs git init, and verifies it builds.
Inputs and defaults
| Input | Default |
|---|---|
| Package name | (required) |
| NuGet PackageId | same as package name |
| Description | (required) |
| Tags | derived from description |
| GitHub / nuget.org user | haiilong |
| Author | haiilong |
| Year | current year |
| Layout | src/ (flat optional) |
| xUnit version | v2 (v3 optional) |
| Source generator | no |
Folder structure
create-nuget-package/
├─ SKILL.md # instructions Claude follows
├─ reference.md # full conventions, rationale, edge cases
└─ templates/ # placeholder-tokenized template files
Templates use {{PACKAGE_NAME}}, {{PACKAGE_ID}}, {{DESCRIPTION}},
{{TAGS}}, {{GITHUB_USER}}, {{AUTHOR}}, {{YEAR}}, {{PACKAGE_CLASS}}.
Installing the skill
Copy the skill folder into a skills directory Claude Code reads:
- Personal (all projects):
~/.claude/skills/create-nuget-package/ - Project (shared with a repo's collaborators):
<repo>/.claude/skills/create-nuget-package/
The folder must contain SKILL.md at its root.
Customizing
Edit templates/ to change what gets generated (e.g. bump dependency versions,
swap the default xUnit version, adjust the CI matrix). Edit reference.md to
change the documented conventions and defaults. Keep SKILL.md's template→destination
map in sync if you add or rename template files.
License
MIT