How do I install the Lingtai Update Install skill?

Run npx skillmds@latest add lingtai-ai/lingtai-update-install in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Lingtai Update Install skill do?

Use when installing or building the lingtai-tui and lingtai-portal binaries. It is listed under Coding & Dev Tools on SkillMD.

Is Lingtai Update Install safe to use?

SkillMD's automated safety review verdict for this skill is WARNING. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lingtai Update Install?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lingtai Update Install free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lingtai Update Install?

lingtai-ai (@lingtai-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lingtai Update Install by lingtai-ai

Name: Lingtai Update Install
Author: lingtai-ai

File contents

Install and build

Nested lingtai-update reference. The supported public first-install path is:

curl -fsSL https://lingtai.ai/install.sh | bash

install.sh resolves the latest release from GitHub; the source option selects the download route, not version authority (--source auto|github|mirror, default auto, or LINGTAI_SOURCE; --source gitee is retired), prefers a matching lingtai-<tag>-<os>-<arch>.tar.gz asset, and falls back to building the release source when no asset is available. It installs both binaries into a selected bin directory and prepares the TUI-managed runtime; that runtime is not a second TUI update path.

On the verified-bundle path the Python lingtai runtime is installed from the bundle's pinned kernel artifact by explicit local file path after a SHA256 check — never by requesting the package name lingtai from an index. Only that artifact's third-party dependencies use a package index, and exactly one: a non-empty LINGTAI_PYPI_INDEX_URL always wins, otherwise the provider that actually served the bundle manifest decides (the lingtai.ai mirror → https://mirrors.tuna.tsinghua.edu.cn/pypi/web/simple, GitHub → https://pypi.org/simple). There is no --extra-index-url. See reference/mainland-china/SKILL.md for the reachability reasoning; Windows (install.ps1) and --latest are outside this behavior.

For a deliberate source build, the current repository layout is:

cd tui && make build
cd ../portal && make build

The portal build first needs its checked-in web dependencies and frontend build (cd portal/web && npm ci && npm run build); portal/embed.go then embeds the result into lingtai-portal. Go and Node are build prerequisites, not runtime dependencies of the portal binary.

The installer accepts --version <tag>, --ref <ref>, --bin-dir <dir> or --prefix <dir>; its --update --prefix <prefix> --version <tag> --non-interactive form is the source updater contract. Prefer the public lingtai.ai URL for new installs. Homebrew remains a supported migration path; bare pip install/upgrade lingtai is kernel development/diagnosis guidance, not normal TUI update guidance.

---name: lingtai-update-installdescription: Use when installing or building the lingtai-tui and lingtai-portal binaries.---# Install and buildNested `lingtai-update` reference. The supported public first-install path is:```bashcurl -fsSL https://lingtai.ai/install.sh | bash````install.sh` resolves the latest release from GitHub; the source option selectsthe download route, not version authority(`--source auto|github|mirror`, default `auto`, or `LINGTAI_SOURCE`;`--source gitee` is retired), prefers a matching `lingtai-<tag>-<os>-<arch>.tar.gz`asset, and falls back to building the release source when no asset isavailable. It installs both binaries into a selected bin directory andprepares the TUI-managed runtime; that runtime is not a second TUI update path.On the verified-bundle path the Python `lingtai` runtime is installed from thebundle's pinned kernel artifact by explicit local file path after a SHA256check — never by requesting the package name `lingtai` from an index. Only thatartifact's third-party dependencies use a package index, and exactly one:a non-empty `LINGTAI_PYPI_INDEX_URL` always wins, otherwise the provider thatactually served the bundle manifest decides (the lingtai.ai mirror →`https://mirrors.tuna.tsinghua.edu.cn/pypi/web/simple`, GitHub →`https://pypi.org/simple`). There is no `--extra-index-url`. See`reference/mainland-china/SKILL.md` for the reachability reasoning; Windows(`install.ps1`) and `--latest` are outside this behavior.For a deliberate source build, the current repository layout is:```bashcd tui && make buildcd ../portal && make build```The portal build first needs its checked-in web dependencies and frontend build(`cd portal/web && npm ci && npm run build`); `portal/embed.go` then embeds theresult into `lingtai-portal`. Go and Node are build prerequisites, not runtimedependencies of the portal binary.The installer accepts `--version <tag>`, `--ref <ref>`, `--bin-dir <dir>` or`--prefix <dir>`; its `--update --prefix <prefix> --version <tag>--non-interactive` form is the source updater contract. Prefer the public`lingtai.ai` URL for new installs. Homebrew remains a supported migration path;bare `pip install/upgrade lingtai` is kernel development/diagnosis guidance, notnormal TUI update guidance.

Frequently asked questions

Lingtai Update Install