What problem does it solve?
When updating the lingtai-tui terminal client, the correct update path depends on how it was originally installed (native installer, Homebrew, or unknown). Choosing the wrong method can leave stale binaries, duplicate installs, or broken PATH resolution. This Skill determines the actual install method conservatively before any update action is taken.
Core Features & Use Cases
- Metadata-based detection: Reads and validates
~/.lingtai-tui/install.json against the lingtai.tui.install/v1 schema to identify source/user-local installs.
- Homebrew recognition: Identifies Homebrew installs from executable paths and prefixes such as
/opt/homebrew, /usr/local, and /home/linuxbrew/.linuxbrew, without running brew unnecessarily.
- Duplicate install handling: Detects the
DuplicateNativeInstall state where a native install exists but the resolved executable is still the old Homebrew binary, routing users to manual removal instead of re-running the installer.
- Use Case: A user on an Apple-Silicon Mac runs
/update-tui; detection finds valid native metadata but the resolved lingtai-tui still points to the Homebrew Cellar copy, so the update flow reports that migration is incomplete rather than silently reinstalling.
Quick Start
Ask the agent to determine how the currently running lingtai-tui was installed before performing an update.