Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/lingtai-tui-help
Anything you need to know about LingTai TUI. Read this first for the stable mental model, major-feature map, interface and slash-command help, or the correct source/manual route for a TUI question. It stays thin: exact command prose lives in the localized help assets, precise Go structure lives in `lingtai-tui-anatomy` plus the repository ANATOMY graph, and independent domains such as presets, Portal, tutorials, updates, and addons keep their own top-level skills.
Passed 15 of 21 test cases with the skill, and 3 of 21 without it.
and 21 more in the full report
13 fixed3 passed either way6 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.
An engineer wants to review Portal visualization, session topology, and execution replay documentation in LingTai. Which primary guide route handles this capability? Provide a concise route answer.
| Checked | Without skill | With skill |
|---|---|---|
| Identifies lingtai-portal-guide as the entry route for Portal visualization and replay. | Missed | Passed |
The instructions your model reads when the skill loads.
lingtai-tui and lingtai-portal are control and presentation surfaces. The
running agent is a separate LingTai kernel process with its own heartbeat,
listeners, lifecycle, and durable working directory.
/sleep, /suspend, /cpr, or
/refresh according to the intended transition; use lingtai-tui list --detailed or /projects to inspect current state.launchd is not the default remedy for ordinary persistence after TUI
exit. The agent already runs independently; adding another supervisor can
create duplicate-process races. Use a separate scheduler/service contract only
for a separately authorized advanced workflow.lingtai-tui-anatomy, start at the repository
root ANATOMY.md, and descend to tui/ANATOMY.md or portal/ANATOMY.md.
Kernel-side process, heartbeat, listener, and lifecycle internals belong to
lingtai-kernel-anatomy; cross-repo references stay narrative.Sanitized regression question: “关闭 TUI/终端后 agent 会不会停止？” No. UI exit
is not an agent lifecycle command; the agent continues until an explicit
lifecycle action or an external process failure stops it. Do not install a
launchd job merely to keep an ordinary agent alive after closing the TUI.
This YAML is the machine-readable map. Each route names the first owner to
load; next is optional deeper evidence.
- feature: runtime-lifecycle-source
route: lingtai-tui-anatomy
next: lingtai-kernel-anatomy
- feature: slash-commands-keyboard-interaction
route: assets/slash-commands.en.md
localized_routes: [assets/slash-commands.zh.md, assets/slash-commands.wen.md]
test cases passed, vs 3 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.