check

Check tmux and container agent statuses with state classification and next-step suggestions.

6|3|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/dollspace-gay/crosslink --skill check-dollspace-gay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/dollspace-gay/crosslink/tree/main/crosslink/resources/claude/skills/check
Command: npx skills add https://github.com/dollspace-gay/crosslink --skill check-dollspace-gay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI coding agents running background feature tasks in tmux sessions or containers have no built-in visibility into their progress, forcing users to manually inspect sessions, logs, or worktrees to determine if agents are working, stuck, waiting for input, or finished, which breaks workflow efficiency and wastes time.

Core Features & Use Cases

  • Dual backend support: Checks both container-based and tmux-based feature agents launched via the /kickoff command, matching agents to the current repository via git worktree paths.
  • State classification: Accurately reports each agent's status as Working, Idle, Waiting, Done, Error, or CI Failed, along with recent output and resource usage for container agents.
  • Use case: If you launched 3 separate agents to work on different feature branches, use this skill to get a single summary of all their progress, identify which need input, and get suggested next steps without manually attaching to each session.

Quick Start

Use the check skill to see the current status of all active background feature agents working on this repository.

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 sessions?

To check tmux agent status, use this skill to classify each background feature agent's state as Working, Idle, or Done, and capture recent output without manually attaching to tmux sessions.

What is the best way to monitor multiple AI coding agents working on different feature branches?

Monitoring multiple AI coding agents requires a centralized status check that matches agents to your repository via git worktree paths, reporting state classification and resource usage across container and tmux backends.

Can I track Docker container resource usage for background feature agents?

Yes, you can track Docker container resource usage for background feature agents, as this skill reports current resource consumption and recent output specifically for container-based agent backends.

How do I know if a background feature agent is stuck, waiting for input, or finished?

To know if a background feature agent is stuck or finished, this skill classifies each agent's exact status—Working, Idle, Waiting, Done, Error, or CI Failed—and provides actionable next-step suggestions.

Does this agent monitoring skill work with both Docker and tmux backends?

Yes, this agent monitoring skill works with both Docker/Podman containers and tmux sessions, matching active feature agents to the current repository via git worktree paths for unified status tracking.