theoros

Run a repo REPL in a named tmux session with read-only spectator workflow.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ajbarea/techne --skill theoros
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: theoros
Source: https://github.com/ajbarea/techne/tree/main/plugins/techne/skills/theoros
Command: npx skills add https://github.com/ajbarea/techne --skill theoros

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces friction when you want to explore or debug an interactive REPL together, by keeping the human from wrestling with typing while still letting them judge what “feels right” during the run.

Core Features & Use Cases

  • Observed live REPL driving: Claude launches and operates the interactive REPL inside a dedicated named tmux session while the human spectates read-only.
  • Aesthetic vs operational discipline: Claude handles operational verification via pane capture and log/command queries, while the human provides aesthetic feedback.
  • Repo-specific configuration: Reads per-repo facts from the ## theoros section in .claude/skill-context.md to know which REPL command and tmux session name to use.

Quick Start

Start a theoros session for your repo by invoking the theoros skill so Claude drives the tmux-launched REPL and you attach with tmux attach -t <session_name> -r.

Frequently Asked Questions about theoros

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

FAQPage Schema
How do I run an interactive REPL in tmux for collaborative debugging?

You can run an interactive REPL in tmux for collaborative debugging by launching it inside a named tmux session and attaching as a read-only spectator. Claude drives the REPL via tmux send-keys while you observe the live output and operational logs.

What's the best way to automate live smoke tests and capture terminal output?

Automating live smoke tests and capturing terminal output is done by running the interactive REPL in a dedicated tmux session and using tmux capture-pane to verify operational outcomes from the pane output and logs.

How do I configure a repo-specific REPL command for an automated debugging loop?

To configure a repo-specific REPL command for an automated debugging loop, define the repl_command, session_name, and optional ops_command in the theoros section of your .claude/skill-context.md file.

Can I spectate a tmux debugging session read-only while Claude operates the terminal?

Yes, you can spectate a tmux debugging session read-only while Claude operates the terminal by attaching to the named tmux session with tmux attach -t <session_name> -r, allowing you to provide aesthetic feedback without typing.

Does tmux send-keys work for executing commands in an automated exploratory REPL session?

Tmux send-keys works for executing commands in an automated exploratory REPL session by programmatically sending keystrokes to the named tmux session, enabling Claude to drive the interactive loop and capture output for verification.

What are the limitations of terminal-driven debugging with a read-only spectator?

Terminal-driven debugging with a read-only spectator requires a repo-configured repl_command and session_name, and the spectator cannot type or interact directly, limiting real-time intervention during the live debugging loop.