herdr-throwaway-repro
FeaturedCreate and control a disposable named Herdr session from inside an existing Herdr session. Use for isolated Herdr runtime, pane, terminal, process, API, persistence, or agent reproductions that should be driven through the CLI/API without touching the default session.
Install
Quality Score: 91/100
Skill Content
Details
- Author
- herdrdev
- Repository
- herdrdev/herdr
- Created
- 5 months ago
- Last Updated
- today
- Language
- Rust
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
herdr
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, terminals, commands, or communication with another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.
herdr
Drive the Herdr terminal workspace manager from the CLI inside the Open Harness sandbox — inspect and control workspaces, tabs, panes, agents, and git worktrees over the Herdr socket API, and read or steer other running agents headlessly. TRIGGER when: asked to run a `herdr` command, list/read/send to another agent or pane, check what agents are running or whether one is idle, split/focus/close panes or tabs, open or create a worktree in Herdr, wait for a pane's output or an agent's status, check Herdr server/session status, or install a Herdr provider integration. Do NOT trigger for tmux-managed headless services (cron, Slack gateway, watchdog) — those stay in their own tmux sessions.
herdr
Working knowledge of herdr (herdr.dev), the terminal workspace manager and coding-agent orchestrator (client-server, tmux-like persistence, agent state tracking). Use this skill whenever the user mentions herdr, asks about terminal workspaces/panes/tabs, attaching/detaching/resuming terminal sessions, orchestrating multiple coding agents, remote-attaching to another machine's terminal, or herdr config. ALSO use it proactively whenever HERDR_ENV=1 appears in the environment — that means you are running inside a herdr pane and can orchestrate panes/agents via the herdr CLI (e.g. spawn a real-TTY pane for interactive prompts like `op signin`).