chocolatey-package-generator
npx machina-cli add skill a5c-ai/babysitter/chocolatey-package-generator --openclawFiles (1)
SKILL.md
839 B
Chocolatey Package Generator
Generate Chocolatey package for Windows distribution.
Generated Patterns
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">
<metadata>
<id>myapp</id>
<version>1.0.0</version>
<title>My App</title>
<authors>My Name</authors>
<projectUrl>https://github.com/myuser/myapp</projectUrl>
<licenseUrl>https://github.com/myuser/myapp/blob/main/LICENSE</licenseUrl>
<description>My CLI application</description>
<tags>cli tools</tags>
</metadata>
</package>
Target Processes
- package-manager-publishing
- cli-binary-distribution
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/specializations/cli-mcp-development/skills/chocolatey-package-generator/SKILL.mdView on GitHub Overview
Generates a Chocolatey package Nuspec for Windows CLI distribution. The output is a ready-to-use XML template including id, version, title, authors, projectUrl, licenseUrl, description, and tags, following the Nuspec structure shown in the example. This enables repeatable packaging and smooth publishing via Chocolatey.
How This Skill Works
The tool reads package metadata and emits a Chocolatey Nuspec XML snippet. It mirrors the Nuspec structure from the sample, populating fields such as id, version, title, authors, projectUrl, licenseUrl, description, and tags for a ready-to-publish package.
When to Use It
- You need to publish a Windows CLI tool to Chocolatey.
- You want a ready-to-use NuSpec template for Chocolatey packaging.
- You’re packaging multiple CLI tools and want a consistent nuspec structure.
- You’re automating the packaging step as part of CI/CD or release pipelines.
- You need a starting point aligned with package-manager-publishing or cli-binary-distribution workflows.
Quick Start
- Step 1: Prepare your metadata: id, version, title, authors, projectUrl, licenseUrl, description, and tags.
- Step 2: Run the generator to produce a Nuspec XML snippet similar to the sample shown in the Skill documentation.
- Step 3: Use the generated Nuspec in your Chocolatey packaging workflow (package-manager-publishing and cli-binary-distribution) and publish.
Best Practices
- Provide accurate metadata: id, version, title, and authors.
- Include valid URLs: projectUrl and licenseUrl.
- Describe the CLI clearly in description and use meaningful tags (e.g., cli tools).
- Validate the Nuspec against Chocolatey packaging guidelines.
- Keep versioning consistent with releases and update the Nuspec accordingly.
Example Use Cases
- Example 1: Packaging MyApp CLI. id=myapp, version=1.0.0, title=My App, authors=My Name, projectUrl=https://github.com/myuser/myapp, licenseUrl=https://github.com/myuser/myapp/blob/main/LICENSE, description=My CLI application, tags=cli tools
- Example 2: Packaging AWS CLI Tool. id=aws-cli-tool, version=2.1.0, title=AWS CLI Tool, authors=Dev Team, projectUrl=https://github.com/org/aws-cli-tool, licenseUrl=https://github.com/org/aws-cli-tool/blob/main/LICENSE, description=CLI utility for AWS, tags=aws cli tools
- Example 3: Packaging Kubectl Helper. id=kubectl-helper, version=0.9.5, title=Kubectl Helper, authors=Ops Team, projectUrl=https://github.com/org/kubectl-helper, licenseUrl=https://github.com/org/kubectl-helper/blob/main/LICENSE, description=Utilities around kubectl, tags=kubernetes cli
- Example 4: Packaging Git Fast. id=git-fast, version=3.0.0, title=Git Fast, authors=DevOps, projectUrl=https://github.com/org/git-fast, licenseUrl=https://github.com/org/git-fast/blob/main/LICENSE, description=Accelerated Git workflows, tags=cli tools
- Example 5: Minimal CLI Package. id=mycli, version=0.1.0, title=MyCLI, authors=Developer, projectUrl=https://github.com/org/mycli, licenseUrl=https://github.com/org/mycli/blob/main/LICENSE, description=Lightweight CLI utility, tags=cli tools
Frequently Asked Questions
Add this skill to your agents