check

Inspect status and output of background feature agents running in tmux sessions or containers.

1.4k|335|Updated Jun 10, 2014
One-click install
npx skills add https://github.com/openwpm/OpenWPM --skill check-openwpm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/openwpm/OpenWPM/tree/main/.claude/skills/check
Command: npx skills add https://github.com/openwpm/OpenWPM --skill check-openwpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you launch background feature agents via /kickoff, they run detached in tmux sessions or docker/podman containers, making it hard to know whether they are still working, stuck, waiting for input, or finished. This Skill gives you a consolidated status report without manually attaching to each session. ## Core Features & Use Cases - Multi-backend discovery: Finds agents both as docker/podman containers (via crosslink-agent labels) and as tmux sessions (feat-*), matched to this repo's git worktrees. - State classification: Reports each agent as Working, Idle, Waiting, Done, Error, or CI Failed by inspecting sentinel files (.kickoff-status), container state, and recent output. - Actionable next steps: Suggests follow-up commands such as viewing logs, attaching to tmux, reviewing committed changes, or relaying answers to waiting prompts. - Use Case: After kicking off three parallel feature agents, ask for a status check and get a compact table showing one agent still implementing, one done, and one waiting for your input on a CLI question. ## Quick Start Ask the assistant to check on the agents, for example by saying "check on the agents" or naming a specific session like feat-add-batch-retry.

Frequently Asked Questions about check

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

FAQPage Schema
How do I check the status of background agents running in tmux?

List feat-* tmux sessions with tmux list-sessions, then capture recent output using tmux capture-pane -t <session> -p -S -80. Classify the agent as Working, Waiting, Error, or Done based on visible tool calls, prompts, or the .kickoff-status sentinel file.

How do I monitor AI agents running inside docker containers?

Filter containers by the crosslink-agent=true label with docker ps, then use docker inspect for exit state and docker logs --tail 80 for recent output. A .kickoff-status file containing DONE or CI_FAILED in the worktree indicates completion.

Can I check both container and tmux agents at the same time?

Yes. When no agent name is given, the check covers both backends: containers matched via crosslink-task labels to git worktree names, and tmux sessions whose session_path matches a worktree of the current repo. Results appear in one summary table.

What does it mean when an agent is waiting for input?

A waiting agent has displayed a question or prompt in its tmux session and is paused until it receives a response. You can read the captured prompt, decide on an answer, and send it with tmux send-keys -t <session> "<response>" Enter.

Why does the check report no active feature agents?

This happens when no containers carry the crosslink-agent label matching this repo's worktrees and no feat-* tmux sessions point at its worktree paths. Verify agents were launched via /kickoff and that you are running the check from the correct repository.