← Back to Skills Marketplace
zbflcy

TUI USE

by zbflcy · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
69
Downloads
1
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install tui-use
Description
Operate TUI (terminal user interface) programs through the tui-agent CLI tool. Use this skill whenever the user asks to interact with, automate, control, or...
Usage Guidance
Before installing or using this skill: 1) verify you actually have a trusted 'tui-agent' binary available (the registry metadata should have declared this dependency but it doesn't). 2) Do not blindly run the SKILL.md's install advice; the repo URL points to an arbitrary GitHub user and the suggested 'pip install -e tui-agent/' is ambiguous — prefer an official release package or inspect the repository contents before installing. 3) Understand that automating terminal programs lets the tool see everything shown in the terminal (potentially sensitive), and the external tui-agent daemon will spawn PTYs and run commands — audit the code if you will install it. 4) If you proceed, restrict usage to manual invocation (do not enable any always-on/autonomous behaviors for untrusted skills), and consider running the tool in a sandboxed environment until you confirm its safety.
Capability Analysis
Type: OpenClaw Skill Name: tui-use Version: 1.0.0 The `tui-use` skill enables an AI agent to launch and interact with arbitrary terminal programs via the `tui-agent` CLI, a high-risk capability involving process execution and screen capture. While the instructions in `SKILL.md` describe legitimate use cases like system monitoring and text editing, the tool's design allows for the execution of any command. Additionally, the skill references an external repository (`github.com/zbflcy/tui-use`) for installation, which poses a potential supply chain risk if the source is not verified.
Capability Assessment
Purpose & Capability
The name/description match the instructions: the skill is an instruction set for controlling TUI programs via a CLI called tui-agent. However, the registry metadata declares no required binaries while SKILL.md explicitly requires a 'tui-agent' CLI (and points to a GitHub repo). The missing declared dependency is an inconsistency: a legitimate TUI automation skill should list the CLI as a required binary or provide a proper install spec.
Instruction Scope
The SKILL.md stays on-topic: it documents starting sessions, capturing screens, sending keys, waiting for text, etc., and does not instruct reading arbitrary system files or exporting credentials. That said, the skill presumes the agent will run arbitrary terminal programs (editors, database clients, monitors) — these programs can expose sensitive data on screen. The instructions also point users to obtain code from a third-party GitHub repo and to run pip install -e tui-agent/, which is an action that downloads and executes external code (outside the skill bundle).
Install Mechanism
There is no install spec in the registry (instruction-only), but SKILL.md tells the user to clone or use a GitHub tree URL and run 'pip install -e tui-agent/'. That guidance is ambiguous (pip install -e expects a local path) and directs installing code from an external GitHub repository (zbflcy/tui-use). Installing arbitrary code from a third-party repo is higher risk and should be declared in install metadata or replaced with a clear, verifiable release URL or package. Because the skill encourages installing/executing external code without provenance, this is a concern.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. The SKILL.md likewise does not request secrets. This is proportionate. Note: automating terminal programs inherently gives the operator (or an agent using this skill) visibility into anything printed to the terminal (which could include secrets), so operational caution is warranted even though no explicit secret access is requested.
Persistence & Privilege
Flags show no 'always: true' and the skill is user-invocable only. Autonomous model invocation is allowed by default but not an additional privilege requested here. The skill does refer to a daemon started by the tui-agent runtime, but that daemon is part of the external tool rather than the skill package itself. No evidence the skill tries to modify other skills or system-wide agent settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install tui-use
  3. After installation, invoke the skill by name or use /tui-use
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
tui-use 1.0.0 – initial release - Introduces tui-agent CLI tool for automating and controlling terminal user interface (TUI) programs. - Supports starting, stopping, and managing multiple TUI application sessions. - Provides commands for screen capture, text typing, special key presses, and clipboard-style paste. - Enables mouse operations including click and scroll in TUI sessions. - Adds robust waiting mechanisms for program states and screen stability. - Documents best practices and example workflows for tools like vim and nano.
Metadata
Slug tui-use
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is TUI USE?

Operate TUI (terminal user interface) programs through the tui-agent CLI tool. Use this skill whenever the user asks to interact with, automate, control, or... It is an AI Agent Skill for Claude Code / OpenClaw, with 69 downloads so far.

How do I install TUI USE?

Run "/install tui-use" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is TUI USE free?

Yes, TUI USE is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does TUI USE support?

TUI USE is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created TUI USE?

It is built and maintained by zbflcy (@zbflcy); the current version is v1.0.0.

💬 Comments