machineconfig: Skill for Claude Code

Goal: produce one JSON object compatible with the live InstallerData shape used by src/machineconfig/jobs/installer/installer_data.json and safely upsert it into the installers array.

Mandatory execution rule:

• Run all helper scripts with uv run ....
• Never run these helpers with plain python.

When invoked, follow this process:

1. Read target repoURL, appName, and doc from the user request.
2. Resolve license:

• If the user explicitly supplied a license string, pass it to the builder with --license.
• Otherwise let the builder infer the license from GitHub repository metadata, then verify that inferred value before writing.

1. Scan releases and classify candidate binaries:

uv run .github/skills/make-github-installer-config/scripts/scan_github_releases.py \
  --repo-url "https://github.com/OWNER/REPO" \
  --limit 8 \
  --output ./.ai/tmp_scripts/make-github-installer-config/scan.json

1. Build inferred config and run latest-release presence checks:

uv run .github/skills/make-github-installer-config/scripts/build_installer_config.py \
  --repo-url "https://github.com/OWNER/REPO" \
  --app-name "appname" \
  --doc "short description" \
  --limit 8 \
  --output ./.ai/tmp_scripts/make-github-installer-config/entry.json

Optional license override:

uv run .github/skills/make-github-installer-config/scripts/build_installer_config.py \
  --repo-url "https://github.com/OWNER/REPO" \
  --app-name "appname" \
  --doc "short description" \
  --license "MIT License" \
  --limit 8 \
  --output ./.ai/tmp_scripts/make-github-installer-config/entry.json

1. Verify checks from entry.json before writing:

• If checks.latestPatternChecks is non-empty, treat as warning and explain why.
• If checks.licenseWarning is non-null, treat as warning and explain why.
• Do not silently ignore failed checks.

1. Perform a dry-run upsert first:

uv run .github/skills/make-github-installer-config/scripts/upsert_installer_data.py \
  --installer-data src/machineconfig/jobs/installer/installer_data.json \
  --entry-json ./.ai/tmp_scripts/make-github-installer-config/entry.json \
  --dry-run

1. If dry-run output is correct, run actual upsert:

uv run .github/skills/make-github-installer-config/scripts/upsert_installer_data.py \
  --installer-data src/machineconfig/jobs/installer/installer_data.json \
  --entry-json ./.ai/tmp_scripts/make-github-installer-config/entry.json

1. Validate resulting JSON file:

jq empty src/machineconfig/jobs/installer/installer_data.json

Output JSON entry must use this exact shape:

{
  "appName": "...",
  "license": "...",
  "repoURL": "https://github.com/OWNER/REPO",
  "doc": "...",
  "fileNamePattern": {
    "amd64": {
      "linux": "... or null",
      "darwin": "... or null",
      "windows": "... or null"
    },
    "arm64": {
      "linux": "... or null",
      "darwin": "... or null",
      "windows": "... or null"
    }
  }
}

Requirements:

• license is required. Prefer the GitHub repo license metadata unless the user explicitly overrides it.
• If GitHub does not declare a license, use "No license asserted" and call that out explicitly.
• If binaries are unavailable for a platform/architecture, set that value to null.
• Prefer Linux musl artifacts over gnu when both are available.
• Use stable, recurring filename patterns from recent releases.
• Keep appName lowercase and concise.
• Keep doc short and descriptive.
• Keep license short and literal; do not invent SPDX identifiers that upstream does not declare.
• Ensure selected non-null patterns match at least one asset in the latest inspected release.
• Return valid JSON only for the object itself (no surrounding prose) unless the user asks for explanation.

Safety and idempotency rules:

• Always check whether an entry with the same appName or repoURL already exists.
• If present, update in place instead of duplicating.
• If duplicate entries already exist, keep one and remove extras.
• Always perform dry-run before writing.
• Keep a backup when writing.
• Never mutate unrelated installer entries.