How should autoupdate be configured?

Set autoupdate.url to a versioned download URL using $version where appropriate.

How can I test the manifest before publishing?

Validate the JSON and try a local or sandbox Scoop install to ensure the manifest resolves correctly.

scoop-manifest-generator

npx machina-cli add skill a5c-ai/babysitter/scoop-manifest-generator --openclaw

Files (1)

SKILL.md

759 B

Scoop Manifest Generator

Generate Scoop manifest for Windows distribution.

Generated Patterns

{
  "version": "1.0.0",
  "description": "My CLI application",
  "homepage": "https://github.com/myuser/myapp",
  "license": "MIT",
  "url": "https://github.com/myuser/myapp/releases/download/v1.0.0/myapp-win-x64.zip",
  "hash": "sha256:abc123...",
  "bin": "myapp.exe",
  "checkver": "github",
  "autoupdate": {
    "url": "https://github.com/myuser/myapp/releases/download/v$version/myapp-win-x64.zip"
  }
}

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/scoop-manifest-generator/SKILL.md

View on GitHub

Overview

This skill generates a Scoop manifest JSON tailored for Windows CLI distributions. It outputs the standard fields (version, description, homepage, license, url, hash, bin, checkver, and autoupdate) as demonstrated in the sample. This enables straightforward package-manager-publishing and cli-binary-distribution workflows.

How This Skill Works

You provide release metadata (version, download URL, hash, executable name) and the skill assembles a valid Scoop manifest. The output mirrors the pattern shown in the Generated Patterns block and can be dropped into a Scoop bucket for distribution.

When to Use It

Preparing a new Windows CLI tool for Scoop distribution
Updating an existing manifest after a new release (version/hash)
Automating manifest creation as part of a release pipeline
Publishing a tool with a GitHub Releases URL and autoupdate
Converting a manual manifest into a Scoop-compatible structure

Quick Start

Step 1: Collect release data (version, asset URL, and sha256 hash).
Step 2: Fill manifest fields (description, homepage, license, bin, checkver, autoupdate).
Step 3: Validate JSON and add to your Scoop bucket.

Best Practices

Ensure version and file URL point to the correct release artifact
Use the correct binary path (bin) for the executable
Keep homepage and license accurate and up to date
Use the autoupdate URL pattern with $version
Validate the generated JSON against the Scoop schema before publishing

Example Use Cases

myapp v1.0.0 on GitHub Releases with sha256 hash and myapp-win-x64.zip
mytool v2.1.3 by Acme, with autoupdate to v$version
qwikcli v0.9.8 releasing a Windows binary
funcli v3.0.0 with custom homepage and MIT license
sampletool v1.2.0 using github as checkver and autoupdate URL

Frequently Asked Questions

Add this skill to your agents