Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/lingtai-update-detection
Use when determining how the running lingtai-tui was installed.
Passed 19 of 21 test cases with the skill, and 7 of 21 without it.
and 12 more in the full report
13 fixed7 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
What advisory directive must be presented to the user across all update entry points when lingtai-tui detects a DuplicateNativeInstall condition?
| Checked | Without skill | With skill |
|---|---|---|
| The response states that migration is incomplete and the user must manually remove the Homebrew installation. | Missed | Passed |
The instructions your model reads when the skill loads.
Nested lingtai-update reference. Detection is deliberately conservative.
~/.lingtai-tui/install.json (or the configured global directory) and
validate the lingtai.tui.install/v1 metadata. Matching the running
executable, including the managed lingtai-tui alias, makes this a
source/user-local install./opt/homebrew, /usr/local, and
/home/linuxbrew/.linuxbrew patterns.brew merely because it
is available, and do not infer source ownership from a path alone when
source metadata says otherwise.Symlinks matter: a manually linked or development binary may not be the
Homebrew Cellar copy. Check lingtai-tui doctor output and the resolved
executable before choosing a manual command. This metadata is diagnostic and
routing information, not a credential store.
A Homebrew-detected install is not upgraded through brew: /update-tui and
lingtai-tui self-update migrate it to the native installer instead (see
reference/update-tui/SKILL.md). Migrating installs and verifies a native
binary, but does not by itself guarantee the shell will run it: on a standard
Apple-Silicon Homebrew host, /opt/homebrew/bin is earlier on PATH than
install.sh's default native bin dir, so the resolved lingtai-tui can still
be the old Homebrew one even after a "successful" install. Detection accounts
for this directly — when valid native (install.json) metadata exists but
does not match the currently resolved executable, and that executable still
resolves as Homebrew, detection reports DuplicateNativeInstall instead of
silently treating it as a plain fresh Homebrew install: the method stays
Homebrew (the resolved binary really is still Homebrew's), and every update
entry point surfaces "native installed, migration not complete, remove
Homebrew yourself" instead of re-prompting or re-running the installer. Only
once the resolved executable actually matches the native metadata does
detection report the install as source/user-local from then on — until then,
the Homebrew Cellar copy stays on disk. Removing it always requires a
concrete interactive "y" to the "Remove the old Homebrew installation now?"
prompt at startup (see reference/update-tui/SKILL.md); self-update and
doctor never uninstall it themselves, only report the manual command.
test cases passed, vs 7 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.