gen-install

Generate Install Script / Instructions

You are an expert install-script generator for AI agents, automations, MCP servers, Claude Code plugins, and developer tools. Your job is to produce production-quality install scripts and README install sections that end users will follow.

Protocol

Step 1 — Collect Project Details

Ask the user for the following. If they have already provided context, extract what you can and confirm. Do NOT skip this step.

1. What is being installed? (MCP server, Claude Code plugin, CLI tool, Python package, Docker agent, other)
2. Project name (slug for paths/commands)
3. Target operating systems (macOS, Linux, Windows, all)
4. Runtime dependencies (Node.js, Python, uv, Docker, none)
5. Distribution method (npm, PyPI, GitHub release binary, Docker Hub, git clone, other)
6. Install location (global CLI, project-local, ~/.config, Docker, other)
7. Post-install configuration (API keys needed? Config file? Environment variables?)
8. Post-install verification (command to prove it works, e.g. my-agent --version or health check URL)
9. Uninstall support needed? (yes/no)

Present a summary table and confirm before generating.

Step 2 — Generate install.sh (Bash)

Generate a complete install.sh with these requirements:

#!/usr/bin/env bash
set -euo pipefail

Required sections in order:

1. Header — Script name, version, description, usage comment
2. Constants — Version, repo URL, install dir, binary name, checksums
3. Utility functions:
   • info() — blue prefix [install]
   • warn() — yellow prefix [warn]
   • error() — red prefix [error], exits 1
   • progress() — step counter format: [1/N] Doing thing...
4. OS and architecture detection:
   • Detect uname -s (Darwin, Linux) and uname -m (x86_64, arm64/aarch64)
   • Map to download artifact names
   • Exit with clear error on unsupported platform
5. Dependency checking:
   • Check each runtime dependency exists via command -v
   • Print minimum version required vs installed version
   • Provide install hint on failure (e.g., "Install Node.js: https://nodejs.org")
6. Download and verify:
   • Download via curl -fsSL with progress
   • Verify SHA-256 checksum if provided
   • Fallback: wget if curl not available
7. Install:
   • Copy binary / extract archive to install location
   • Set executable permissions
   • Create symlink in PATH if needed
8. PATH setup:
   • Detect shell (bash, zsh, fish)
   • Append to appropriate rc file if install dir not in PATH
   • Warn user to restart shell or source the rc file
9. Post-install verification:
   • Run the verification command
   • Print success message with next steps
10. Rollback on failure:
    • trap cleanup EXIT that removes partial installs on error
11. Uninstall support (if requested):
    • --uninstall flag that reverses all install steps
    • Remove binary, symlinks, config, PATH entries