원클릭으로 Manus에서 모든 스킬 실행

run-tui

스타17

포크3

업데이트2026년 7월 18일 16:34

Build the abi CLI and drive the interactive diagnostics dashboard (`abi dashboard` / `abi tui` / `abi --tui`) through a tmux pty — launch it, screenshot/capture the rendered pane, assert it painted, send the quit key, tear down. Use to run, launch, screenshot, or smoke-test the abi TUI/dashboard headlessly. The one abi surface that needs a real terminal.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

donaldfilimon

donaldfilimon/abi

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

run-tui — drive abi's interactive diagnostics dashboard

Driver: .agents/skills/run-tui/tui.sh (paths relative to repo root). abi dashboard/tui/--tui are interactive on a real TTY; this driver gives them a tmux pty, captures the rendered pane, asserts the dashboard painted, sends q, and kills the session. Evidence is the RESULT: line. Fully local.

Prerequisites

tmux (brew install tmux). The driver checks for it and fails fast if absent.

Run (agent path)

.agents/skills/run-tui/tui.sh              # drives `abi dashboard` (default)
.agents/skills/run-tui/tui.sh tui          # drive `abi tui` instead

Launches the command under tmux new-session (200x50 pane), waits for paint, captures the pane, and asserts the ABI Diagnostics Dashboard marker is present and there's no errno 19/tcgetattr/panic. Sends q (the quit key — isQuitKey accepts q/Q/Esc) and confirms the session tore down. Prints RESULT: PASS (exit 0) or a FAIL count.

To eyeball it yourself: tmux capture-pane -pt <session> shows the System pane (GPU backend, accelerated, native-linked) and the Plugins pane (16 registered).

Historical verification: PASS on the pin in .zigversion — dashboard box + System + Plugins panes render under the pty; q quits; session cleaned up. Do not hardcode a Zig nightly in this skill; read .zigversion for the live pin.

Gotchas (battle scars)

⚠️ Do NOT prepend /opt/homebrew/bin to PATH. Homebrew ships a zig (/opt/homebrew/bin/zig -> 0.16.0) that cannot compile this tree. Putting brew's bin first shadows the zvm 0.17 zig and the build fails with std API errors. The driver appends brew's bin (for tmux) so the zvm zig stays first — keep it that way.
A pty is mandatory for the interactive path. Piped stdin or /dev/null intentionally uses the one-shot fallback; use tmux when you need to prove the live loop paints and accepts q.
Give it time to paint. The driver sleeps 2.5s before capture; a busy machine may need more. A blank pane = captured too early, not a failure to run.
Accelerated: yes / Native Linked: yes in the System pane is the dashboard's own rendering of backend state; the CLI backends report phrases the same Metal-linked/CPU-fallback status differently — both are correct.
For the render loop and screen lifecycle internals, use the tui-navigation-guide subagent.

Troubleshooting

Symptom	Fix
`tmux not installed`	`brew install tmux`.
`build` FAIL right after adding brew to PATH	brew's `zig` 0.16 shadowed zvm — append, don't prepend (see Gotchas).
`dashboard did not paint`	Increase the `sleep`, or confirm the pane size (`-x/-y`) is large enough.
`tty error / panic in pane`	Regression in the interactive terminal path; confirm launch went through `tmux new-session`.

이 저장소의 다른 Skills

같은 저장소

abi-doc-claims-sync

donaldfilimon/abi

Synchronize ABI Markdown and docs claims with executable behavior. Use before editing README, AGENTS.md, CLAUDE.md, GEMINI.md, docs/**/*.mdx, walkthroughs, changelogs, or any old ABI Markdown that mentions WDBX, MCP, GPU, clustering, compression, FHE, agents, or benchmarks.

2026-07-1917

abi-claims-validator

donaldfilimon/abi

Validate ABI docs and external collateral against repo evidence and docs/contracts/external-claims-audit.mdx. Use when auditing claims, scanning docs for unsupported QPS/sharding/FHE/AES language, checking one claim before publish, or re-confirming the external-claims audit. Agent procedure only — not a CLI or slash command. Pair with abi-doc-claims-sync when editing docs.

2026-07-1817

abi-goal-orchestrator

donaldfilimon/abi

Plan and execute ABI repo work from the TODO board, roadmap/spec docs, Zig 0.17 constraints, and validation gates. Use when the user asks to find ABI todos/roadmaps, organize a large implementation from tasks/todo.md, or decide the next safe work slice. Distinct from the goals skill — that skill owns the persistent ledger tasks/goals.md; this skill plans from the active board and north-star specs.

2026-07-1817

abi-superpower-tui

donaldfilimon/abi

TUI/dashboard superpower. Launch interactive agent REPL, diagnostics dashboard panes, and slash commands via real abi CLI paths. Use when working on abi tui / dashboard / agent tui. There is no /abi-superpower-tui binary.

2026-07-1817

dashboard-smoke

donaldfilimon/abi

Build the abi CLI and non-interactively smoke the diagnostics dashboard — render `abi dashboard` one-shot (stdin from /dev/null forces the non-interactive fallback), assert exit 0 and all 5 panels (System, Plugins, WDBX Storage, Scheduler, Memory). Use to smoke-test `abi dashboard`/`abi tui`/`abi --tui` in CI or headless without hanging in the interactive TUI. Complements run-tui (which drives the interactive path via tmux).

2026-07-1817

goals

donaldfilimon/abi

Capture, track, and execute goals for the abi Zig project. Use when the user wants to record a goal, see outstanding goals, update goal status, or break a goal into a verified work slice. Distinct from abi-goal-orchestrator (which plans from the TODO board) — this skill owns a persistent goal ledger and drives goal-to-slice execution.

2026-07-1817

name	run-tui
description	Build the abi CLI and drive the interactive diagnostics dashboard (`abi dashboard` / `abi tui` / `abi --tui`) through a tmux pty — launch it, screenshot/capture the rendered pane, assert it painted, send the quit key, tear down. Use to run, launch, screenshot, or smoke-test the abi TUI/dashboard headlessly. The one abi surface that needs a real terminal.

run-tui — drive abi's interactive diagnostics dashboard

Prerequisites

tmux (brew install tmux). The driver checks for it and fails fast if absent.

Run (agent path)

.agents/skills/run-tui/tui.sh              # drives `abi dashboard` (default)
.agents/skills/run-tui/tui.sh tui          # drive `abi tui` instead

To eyeball it yourself: tmux capture-pane -pt <session> shows the System pane (GPU backend, accelerated, native-linked) and the Plugins pane (16 registered).

Gotchas (battle scars)

⚠️ Do NOT prepend /opt/homebrew/bin to PATH. Homebrew ships a zig (/opt/homebrew/bin/zig -> 0.16.0) that cannot compile this tree. Putting brew's bin first shadows the zvm 0.17 zig and the build fails with std API errors. The driver appends brew's bin (for tmux) so the zvm zig stays first — keep it that way.
A pty is mandatory for the interactive path. Piped stdin or /dev/null intentionally uses the one-shot fallback; use tmux when you need to prove the live loop paints and accepts q.
Give it time to paint. The driver sleeps 2.5s before capture; a busy machine may need more. A blank pane = captured too early, not a failure to run.
Accelerated: yes / Native Linked: yes in the System pane is the dashboard's own rendering of backend state; the CLI backends report phrases the same Metal-linked/CPU-fallback status differently — both are correct.
For the render loop and screen lifecycle internals, use the tui-navigation-guide subagent.

Troubleshooting

Symptom	Fix
`tmux not installed`	`brew install tmux`.
`build` FAIL right after adding brew to PATH	brew's `zig` 0.16 shadowed zvm — append, don't prepend (see Gotchas).
`dashboard did not paint`	Increase the `sleep`, or confirm the pane size (`-x/-y`) is large enough.
`tty error / panic in pane`	Regression in the interactive terminal path; confirm launch went through `tmux new-session`.