Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/lingtai-update-command
Use when operating /update-tui or lingtai-tui self-update.
Passed 21 of 21 test cases with the skill, and 3 of 21 without it.
and 28 more in the full report
19 fixed3 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 18 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to manually clean up my old LingTai TUI Homebrew installation from the macOS shell after confirming native PATH resolution works. What exact brew command should I execute to uninstall it?
| Checked | Without skill | With skill |
|---|---|---|
| specifies running brew uninstall lingtai-ai/lingtai/lingtai-tui | Missed | Passed |
The instructions your model reads when the skill loads.
/update-tuiNested lingtai-update reference. /update-tui compares the running TUI with
the latest GitHub release, detects the install method, and requires explicit
confirmation before changing the TUI binary; the selected distribution may also
refresh the co-installed portal binary. It never updates the Python kernel,
presets, or utility library, and never auto-restarts the current TUI — relaunch
after a successful update.
https://raw.githubusercontent.com/Lingtai-AI/lingtai/<tag>/install.sh
with --update --prefix <native-prefix> --version <tag> --non-interactive,
accepting and updating existing managed runtime/receipt state in place while preserving the exact target tag
rather than using ordinary first-install mode.
then verifies the new install.json source metadata, the binary version at
the new bin_dir, and the Python runtime. On any migration failure the old
Homebrew formula/keg remains exactly as usable as before the attempt — the
migration step itself never runs brew.
Before reporting success, the migration also resolves lingtai-tui on PATH
and checks it against the freshly installed binary — on a standard
Apple-Silicon Homebrew host, /opt/homebrew/bin is earlier on PATH than
install.sh's default native bin dir, so a fresh native install alone does
not make the shell start running it. When PATH still resolves to
Homebrew, the migration reports "native installed, migration not complete"
instead of "Migrated!", and every update entry point (startup prompt,
self-update, doctor) re-detects and re-reports that same truthful state
on every subsequent run — it does not re-run the installer and does not
claim success until PATH actually resolves the native binary. Only once
that is confirmed does detectTUIInstallMethod report the install as
source/user-local going forward, so subsequent updates use the source path
below instead of brew.install.sh --update --prefix ... --version <tag> --non-interactive path and verifies the result.If a legacy ~/.lingtai-tui/runtime exists before a native receipt, the
installer's documented recovery path is a TUI-only install with
--skip-python (or --skip-venv): it preserves that runtime unchanged and
publishes the native binaries/receipt beside it. Use the standalone fix.sh
with an explicitly named free runtime child only after reviewing its
test cases passed, vs 3 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.