tui-test Skill
Drive, inspect, assert on, record, and watch a real terminal from the command line with the tui-test cli. Use when running shells (bash, zsh, fish, PowerShell, pwsh, cmd, xonsh, elvish, nushell) or TUI programs (vim, less, top, etc.) in a headless PTY; sending keystrokes, key combos, or mouse input; resizing, writing r Published by microsoft in shell-use.
Decision snapshot
Is this a fit?
Testing, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is tui-test Skill?
Drive, inspect, assert on, record, and watch a real terminal from the command line with the tui-test cli. Use when running shells (bash, zsh, fish, PowerShell, pwsh, cmd, xonsh, elvish, nushell) or TUI programs (vim, less, top, etc.) in a headless PTY; sending keystrokes, key combos, or mouse input; resizing, writing r Published by microsoft in shell-use. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Writing
- Testing use cases
- Writing use cases
Declared skill metadata
- Source file: SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use tui-test Skill
- Use it for testing.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/shell-use
- Skill file: SKILL.md
What it does
Drive, inspect, assert on, record, and watch a real terminal from the command line with the tui-test cli. Use when running shells (bash, zsh, fish, PowerShell, pwsh, cmd, xonsh, elvish, nushell) or TUI programs (vim, less, top, etc.) in a headless PTY; sending keystrokes, key combos, or mouse input; resizing, writing r
Skill instructions
tui-test tui-test controls a real terminal from the command line. It runs shells and TUI programs in a headless PTY behind a background daemon: a stateless cli front end talks to a daemon that owns the PTY and renders it into a full terminal emulator. Each call connects, acts, and exits, and they all share one live session. With it you can spawn a session, read the rendered screen, send keys and mouse input, wait for a condition, assert on the result, and record the session. Built for agents: self-documenting commands Three commands let an agent look up the rest of the surface instead of guessing: - tui-test agent-context: versioned JSON describing every command, flag, enum, default, and the exit-code taxonomy. It is generated from the cli, so it stays in sync. Read this first when you need exact argument shapes. - tui-test usage: a one-screen command cheatsheet. - tui-test skill: this guide. Core model - Sessions. --session <name (default default, env TUITESTSESSION) selects a termina
Verified compatibility and discovery
Frequently asked questions
What is tui-test?
tui-test is a open-source AI agent skill with Copy skill directory. Drive, inspect, assert on, record, and watch a real terminal from the command line with the tui-test cli.
Who is tui-test best for?
tui-test is best for reusing agent instructions, scripts, and references, testing workflows, writing workflows.
How do I install tui-test?
Install or run tui-test using Copy skill directory. Check tui-test for the latest setup command.
Is tui-test actively maintained?
tui-test may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
