check

Report status of background feature agents from .kickoff-status sentinel files.

27|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/forecast-bio/ferray --skill check-forecast-bio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/forecast-bio/ferray/tree/main/.claude/skills/check
Command: npx skills add https://github.com/forecast-bio/ferray --skill check-forecast-bio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates visibility into background feature agents by aggregating their state, recent output, and health, reducing manual ad-hoc checks.

Core Features & Use Cases

  • Monitor container-based and tmux-based agents across worktrees
  • Provide status summaries (Working, Idle, Waiting, Done, Error) and recent logs
  • Trigger guided next-steps commands for remediation or progress tracking

Quick Start

Start a check to report the current status of all active agents or a named agent.

Frequently Asked Questions about check

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

FAQPage Schema
How do I monitor background agents launched in Docker or tmux sessions?

Track agent status by reading the .kickoff-status sentinel file and capturing recent logs to classify states. It reports Working, Idle, Waiting, Done, and Error across Docker containers and tmux sessions in all worktrees.

What status states can I identify for background feature agents?

Identify background agent status as Working, Idle, Waiting, Done, or Error. The classification is derived from the .kickoff-status sentinel file and recent log output to guide your next debugging or remediation steps.

How do I check the progress of agents across multiple worktrees?

Check agent progress across all worktrees by aggregating their current state and recent output. It provides status summaries and recent logs for background feature agents launched via /kickoff to support real-time debugging.

Can I monitor tmux-based sessions and Docker containers with the same status check?

Yes, you can monitor both container-based agents and tmux-based sessions. It applies to both environments across all worktrees, reading the .kickoff-status sentinel file and capturing logs to derive state classifications.

What should I do when a background agent reports an Error state?

When a background agent reports an Error state, trigger the guided next-steps commands provided by the status check for remediation. It derives state classifications from recent logs and the sentinel file to guide your debugging actions.