Monitor worker pane states and verify wakeup proofs via heartbeat checks.
npx skills add https://github.com/almazom/agents_slash_skills --skill observer-almazom
Please help me install this Agent Skill. Skill: observer Source: https://github.com/almazom/agents_slash_skills/tree/main/observer Command: npx skills add https://github.com/almazom/agents_slash_skills --skill observer-almazom
Observe WezTerm worker runs through mini-pane heartbeats, sleep-loop watchers, cron-friendly checks, and strict manager wakeup delivery. Use when Codex needs to (1) create a small observer pane under a visible worker, (2) watch active | idle | stuck | gone state over time, (3) wake a manager or Shehroz pane when a worker returns to idle, (4) prove inject -> submit -> 30s watch for manager wakeups, or (5) run recurring pane/process heartbeat checks through sleep loops or cron.
Launch the observer under a visible worker to start heartbeats monitoring and wakeup proof collection.
High-intent search queries and answers about installing and using this skill.
To monitor WezTerm worker heartbeats, you observe and verify state transitions for visible panes, tracking idle, active, stuck, and gone states through mini-pane observation, sleep-loop watchers, or cron-based checks.
A deterministic wakeup proof path is a strict verification workflow enforcing the sequence of inject, submit, and a 30-second watch to prove manager wakeups, reporting startup_proved when explicit evidence is collected.
You wake a manager pane when a WezTerm worker returns to idle by using configurable wrappers that monitor heartbeat state and trigger manager wakeup delivery once the idle transition is confirmed.
Yes, you can run recurring process heartbeat checks by deploying cron-friendly checks or sleep-loop watchers that continuously observe and log per-heartbeat truth about worker pane activity and tty state.
The observer does not run the worker itself; it is strictly used to monitor, prove, and wake the manager, enabling reliable orchestration by logging per-heartbeat truth about worker pane activity.
The best way to take a quick snapshot is using a one-shot inspect, which provides an immediate observation of the worker's current activity, tty state, and wrapper logs without a continuous loop.
OrinksOrchestrate OMX team execution across tmux panes with durable state management.
almazomCoordinates a manager with worker instances to run card-scoped sessions via Zellij and kanban.json.
cyzusSchedule cron-based tasks and persistent heartbeat monitoring for agent prompts.
pckienuitChain Bash commands and manage files with safe Unix scripting.
