Individual skill
control-cli
Drive and inspect an interactive CLI or TUI with a repeatable local harness, deterministic input, transcripts, and optional profiling. Use for CLI UX checks, prompt flows, startup regressions, hangs, interrupts, resize behavior, or memory growth. Do not use for a non-interactive command that a normal test can cover.
skills/development/control-cli/SKILL.md
Source commit 849719987d9c0d6ed973bdbce8ed37b266d3b1f3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 214
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude Repository topic
- claude-code Repository topic
- llm Repository topic
- machine-learning Repository topic
- prompt-engineering Repository topic
- skills Repository topic
- mcp Repository topic
- agent-harness Repository topic
- harness Repository topic
- design Derived category
- marketing Derived category
- testing Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,545 bytes
Read excerpt
# Control CLI
Exercise an interactive terminal program through a small, repeatable harness.
Prefer a repository-native demo or test harness; only assemble a temporary PTY
or terminal session when the project has no suitable one.
## Harness Loop
1. Identify the command, smallest fixture, expected ready marker, and cleanup
condition.
2. Discover existing package scripts, PTY helpers, expect scripts, demo
recorders, or TUI tests.
3. Launch in an isolated environment with deterministic variables and local
disposable data.