Dotnet10 Pack Tool
CheckedThis tool simplifies .NET 6+ project packaging for deployment by automating NuGet package creation and management – saving development time.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add rysweet/amplihack --skill dotnet10-pack-tool -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
rysweet
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned rysweet/amplihack at 84424457d5.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 84424457d5
- Scanned
- 3 files, 714 lines
About this skill
What it does
This skill simplifies creating hybrid .NET 10 tool packages, combining Native AOT for performance with CoreCLR fallback for broader compatibility. It guides you through configuring your project and building separate packages optimized for different platforms. The process involves generating a "pointer package" (metapackage), building Native AOT binaries for specified target RIDs, creating a CoreCLR fallback, and validating the final package structure.
When to use it
- You need to distribute a .NET 10 tool that performs well on select platforms while remaining compatible with others.
- You want to leverage Native AOT compilation for improved performance in specific environments (e.g., macOS arm64, Linux arm64/x64).
- You are building a cross-platform .NET tool and need to manage package creation for multiple runtime identifiers (RIDs).
- You're familiar with .csproj configuration and command-line build processes.
Key capabilities
- Configures
.csprojfiles withToolPackageRuntimeIdentifiersandPublishAot=true. - Generates a pointer package (metapackage) that references RID-specific packages.
- Builds Native AOT packages for specified target RIDs using the
-rflag. - Creates CoreCLR fallback packages using
-r anywithPublishAot=false. - Validates the overall package structure.
Example prompts
- "pack .NET tool"
- "dotnet pack AOT"
- "Create a hybrid .NET tool package for macOS arm64 and Linux x64."
Tips & gotchas
- Requires familiarity with
.csprojfile editing and thedotnetcommand-line interface. - Native AOT compilation cannot cross-compile operating systems, so builds must be performed on each target platform.
- The skill relies on manual execution of
dotnet packcommands with specific parameters for each RID.