qclaw-env

Diagnosing missing CLI tools and runtimes requires a detect-then-install workflow that enumerates existing package managers, resolves layered dependency chains, and validates the environment post-installation. This approach checks network reachability, selects correct installers based on OS and architecture, and provides manual fallback instructions when privileged actions are needed.

The correct installation order follows a strict layered dependency chain: network and mirror configuration first, then package manager installation, followed by runtimes, then CLIs, and finally environment variable configuration. Each layer is validated before proceeding to ensure a stable setup.

Yes, you can configure network mirrors for package managers when facing slow or blocked connections. The environment diagnosis process includes network reachability checks to key services and enforces mirror configuration to ensure reliable downloads of runtimes and CLI tools.

Yes, environment diagnosis supports both Homebrew on macOS and Scoop on Windows. It performs platform and architecture detection to select the correct installer, applies appropriate PATH adjustments, and ensures the selected package manager is validated before installing runtimes like node, python, or go.

CLI tool installation often fails due to missing layered dependencies or network blocks. When privileged actions or GUI interventions are required, the diagnosis process generates step-by-step, copy-paste friendly manual instructions to guide you through the necessary elevation or configuration steps.

The best way to prepare a workstation is to run a full environment diagnosis that detects your platform architecture, snapshots existing tools, and installs missing package managers, runtimes, and CLIs like ffmpeg and gh. This ensures all dependencies are resolved and validated before skill execution.