true-input

Inject real HID keystrokes into terminal emulators across Linux, macOS, and Windows VMs.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/ElbertePlinio/dotfiles --skill true-input-elberteplinio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: true-input
Source: https://github.com/ElbertePlinio/dotfiles/tree/main/private_dot_factory/plugins/marketplaces/factory-plugins/plugins/droid-control/skills/true-input
Command: npx skills add https://github.com/ElbertePlinio/dotfiles --skill true-input-elberteplinio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the unreliability of synthetic terminal input and PTY distortion when testing terminal user interfaces, ensuring you can verify exactly what keystrokes a terminal emulator sends and how applications respond to them.

Core Features & Use Cases

  • Cross-Platform Real Input Injection: Drive real terminal emulators via native HID input paths on Linux Wayland (using cage + wtype), macOS QEMU VMs (via QEMU monitor sendkey), and Windows KVM/QEMU VMs (via virsh send-key), with no synthetic input artifacts.
  • Proof and Recording Capabilities: Capture scrubbed PTY logs, screenshots, and video recordings of actual terminal output to validate end-to-end behavior or create accurate demos.
  • Use Case: Validate that a terminal emulator correctly handles edge-case keystrokes like Shift+Enter, or record a demo of a TUI application that reflects real user input and rendering.

Quick Start

Use the true-input skill to verify that your Ghostty terminal correctly sends a Shift+Enter keystroke by launching an isolated headless test session and capturing the terminal output for validation.

Frequently Asked Questions about true-input

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

FAQPage Schema
How do I test terminal emulator keystroke handling without PTY distortion?

Verify edge-case keystrokes like Shift+Enter in terminal emulators by launching an isolated headless test session that injects real HID-level input. This captures actual terminal output for validation without relying on synthetic input artifacts or PTY wrappers.

How do I automate real keyboard input injection for TUI testing on Linux Wayland?

Automate real keyboard input for TUI testing on Linux Wayland by driving terminal emulators via cage and wtype. This injects native HID input paths directly, ensuring the terminal receives authentic keystrokes without synthetic input interference.

Can I send keystrokes to a macOS QEMU VM for terminal automation testing?

You can send keystrokes to a macOS QEMU VM for terminal automation testing by utilizing the QEMU monitor sendkey command. This drives real input injection into the virtual machine, validating end-to-end TUI application behavior natively.

What is the best way to record accurate TUI application demos with real user input?

Record accurate TUI application demos by capturing scrubbed PTY logs, screenshots, and video recordings during real HID-level input injection sessions. This ensures the demo reflects actual user input and native terminal rendering without synthetic artifacts.

Does terminal automation testing work across Windows KVM/QEMU VMs?

Terminal automation testing works across Windows KVM/QEMU VMs by utilizing the virsh send-key command for real input injection. This enables cross-platform keystroke validation and session-isolated test environment management within the virtual machine.

Why does my terminal TUI testing fail with synthetic input artifacts?

TUI testing fails with synthetic input artifacts because standard PTY wrappers distort native terminal encoding paths. Bypassing this requires real HID-level input injection to verify exactly what keystrokes the terminal emulator sends and how applications respond.