skills.rest
archibate
archibateCOMMUNITY
Explore all skills by this author →
Website𝕏@archibateGitHub

interactive-test

Guide terminal-based testing of GUI and TUI applications with Playwright or tmux.

103|21|Updated Feb 12, 2026
Search Tags:#testing#playwright#gui#tui#interactive apps#cli agent#pty tmux
One-click install
npx skills add https://github.com/archibate/dotfiles-opencode --skill interactive-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interactive-test
Source: https://github.com/archibate/dotfiles-opencode/tree/main/skills/interactive-test
Command: npx skills add https://github.com/archibate/dotfiles-opencode --skill interactive-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you test interactive applications (GUI/TUI) reliably while avoiding unsafe or confusing automation from a terminal-only agent.

Core Features & Use Cases

  • GUI/TUI-aware testing guidance: Explains why terminal-only execution cannot directly handle interactive TTY/GUI behavior, and what to do instead.
  • Safety guardrails: Enforces rules to avoid starting non-headless GUI apps without user permission to prevent disruptive popups.
  • Practical automation paths: Recommends headless browser automation for web GUIs and manual testing for traditional local GUIs, plus tmux-based PTY workflows for TUIs.

Quick Start

Ask your AI agent to run the interactive test plan for your current app and follow the GUI/TUI rules based on whether it is headless, web-based, or requires manual interaction.

Frequently Asked Questions about interactive-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test interactive TUI applications from a CLI agent safely?▼

Testing TUI applications from a CLI agent requires tmux-based PTY control to manage terminal keystrokes, preventing unsafe or confusing direct automation while enforcing strict CLI-only behavior.

What is the best way to automate web GUI testing without triggering disruptive popups?▼

Automating web GUI testing safely requires headless browser automation using Playwright, which validates interactive applications without launching non-headless GUI apps or causing disruptive popups.

Why does my terminal-only execution fail to handle interactive GUI and TUI behavior?▼

Terminal-only execution fails to handle interactive GUI and TUI behavior because it cannot directly manage TTY interactions, requiring explicit user permission and tool-based approaches for safe testing.

Does testing traditional local GUIs require explicit user permission during automation?▼

Testing traditional local GUIs requires explicit user permission before any non-headless launches to prevent disruptive popups, often relying on manual testing workflows rather than direct automation.

Can I use Playwright and tmux to test interactive apps in different scenarios?▼

Playwright supports headless web GUI testing, while tmux enables PTY control for TUI testing, providing distinct workflow paths to safely validate interactive applications from a CLI agent.

What are the limitations of using a CLI agent for interactive application testing?▼

Limitations of CLI agent testing include the inability to directly execute interactive TTY or GUI behavior, necessitating strict CLI-only rules and manual testing for traditional local GUIs.

Related Skills

Explore More Software Engineering Skills→
nicobailonnicobailon
561

interactive-shell

Control and supervise interactive CLI sessions via overlay or headless dispatch.

Community
Advanced
hkjanghkjang

tmux-real-user-testing

Automate real-user testing in tmux TUI sessions and generate readable logs.

Community
Advanced
ucirelloucirello
2

browser-bug-testing-workflow

Automate browser UI testing with Playwright and tmux server management.

Community
Advanced
liumeixinliumeixin
4

page-agent

Embed an Alibaba in-page GUI agent into web applications.

Community
Intermediate