Status

Report on everything running in the background. Goal: one compact block the user can read in five seconds.

1. Collect in parallel

Fire all of these at once — do NOT serialize. Each is cheap and independent.

tmux sessions

tmux list-sessions 2>/dev/null

For any session whose name suggests long-running work (matches download|embed|run-|batch|job|etl|watch), capture the last 10 lines:

tmux capture-pane -pS -10 -t 

Background job queue (optional — only if you run one)

If you have a local job-queue tool, list its pending/running/recent items here. Example with a `` CLI:

# Example — adapt to your own queue tool, or delete this block if you have none.
cd  &&  queue list 2>&1 | head -30

Note anything queued, in-progress, or recently completed. Flag overdue items. (If your queue CLI resolves dependencies relative to cwd — e.g. tsx does — cd into its directory first; running it from an absolute path can fail silently.)

Scheduled triggers (remote agents)

Use RemoteTrigger tool with action: list. Report:

• Active triggers with their next fire time
• Most recent run result per trigger

In-session crons

Use CronList tool. These are /loop or one-shot schedules created this session.

Long-running processes

Bound elapsed time to 10 min – 24 h to catch active work without drowning in machine-lifetime daemons:

ps -eo pid,etimes,cmd --sort=-etimes 2>/dev/null | awk 'NR==1 || ($2 > 600 && $2  —   (repeat per live session)
- Queue: N queued, M running — next:    (only if you run a queue)
- Triggers: N active, next fire , last  
- In-session crons: 
- Processes:    — (only if unexplained or >1h old)
- Background tasks: 

Flags: 

If nothing's running anywhere, just say "Background: nothing active." and stop.

4. Notes

• This skill is read-only. Never kill, restart, or modify anything. If the user wants to act on something surfaced here, they'll say so.
• If a probe fails (queue CLI path moved, tmux not installed, etc.), note it silently and continue with the others. Don't block the report on any single probe.
• For very long-running jobs (overnight batches, multi-day downloads), include a rough percent-done or elapsed-time estimate if the tmux capture makes it obvious.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: PropterMalone
• Source: PropterMalone/PropterMaltwo
• License: MIT

Install and usage instructions live in the source repository linked above.