control-cli
Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services. Use for CLI UX checks, startup regressions, memory leaks, hangs, prompt flows, or terminal demos.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/cursor/plugins /tmp/plugins && ln -s /tmp/plugins/cursor-team-kit/skills/control-cli ~/.claude/skills/control-cliFrom README
Control CLI Use a repeatable local harness to exercise an interactive CLI instead of poking at it manually. First reuse the repo's own test/demo harness if it exists; otherwise assemble a temporary harness from standard local tools. What It Is Used For Reproducing CLI/TUI bugs with deterministic input. Verifying keyboard flows, prompts, interrupts, resize behavior, and terminal layout. Capturing before/after transcripts for bug fixes. Profiling startup time, slow operations, hangs, or memory growth. Recording a short terminal demo when output is easier to show than explain. Harness Loop Identify the command under test and the smallest reproducible workspace. Discover existing local harnesses: package scripts, e2e tests, demo recorders, expect scripts, or PTY helpers. If no harness exists, launch the CLI in an isolated terminal session with deterministic env vars. Capture the current screen before interacting. Send one action at a time: text, Enter, arrows, Escape, Ctrl-C, resize.