subagent-overseer
Monitor sub-agent health and progress via a pull-based bash daemon. Use when spawning sub-agents that need progress tracking, staleness detection, and automatic status reporting. Replaces manual heartbeat polling with a deterministic status file the agent reads every 3 minutes. Zero AI tokens for monitoring — pure OS-level process checks and filesystem diffs.
Why use this skill?
Optimize your OpenClaw agents with the sub-agent-overseer. Implement token-free background health monitoring, staleness detection, and deterministic status reporting for long-running workflows.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/globalcaos/subagent-overseerWhat This Skill Does
The subagent-overseer skill is a sophisticated, non-intrusive monitoring daemon designed for complex OpenClaw multi-agent workflows. Instead of relying on expensive, token-heavy LLM polling cycles to check on the progress of background sub-agents, this skill utilizes a lightweight bash-based daemon. By performing periodic checks on the /proc filesystem and tracking changes to the local directory, the overseer provides a real-time, deterministic status report in a structured JSON file. This architectural decision ensures that your agent remains focused on high-level reasoning tasks while the OS-level monitor manages the tedious background oversight, reducing latency and avoiding redundant AI overhead.
Installation
To integrate this monitoring capability into your OpenClaw environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/globalcaos/subagent-overseer
Ensure that you have appropriate write permissions for the /tmp/overseer/ directory, as the daemon requires this location to maintain the status.json file used for heartbeat synchronization.
Use Cases
- Autonomous Research Chains: Monitor long-running research sub-agents that are writing data to files over extended periods to ensure they haven't crashed.
- Complex Development Tasks: Keep track of multiple code-generation agents spawned for distinct tasks, preventing zombie processes from consuming CPU cycles.
- System Health Monitoring: When building agent swarms, use the overseer to verify the
openclaw-gatewayhealth to ensure the entire infrastructure remains operational.
Example Prompts
- "Initialize the overseer for the current project directory with a 60-second interval and enable voice alerts for stuck agents."
- "Check the current sub-agent status file and report if any agents are flagged as stuck or in warning mode."
- "The sub-agent overseer is reporting a stale process in the current workspace; list the active sessions and kill the one marked as stuck."
Tips & Limitations
- Token Efficiency: Because the overseer writes a clean JSON file, your agent can read the status in a single pass without needing to trigger a full environment scan.
- Performance: For high-load environments, keep the
--intervalabove 180 seconds to minimize I/O overhead. - Limitations: The skill is primarily designed for Linux environments. macOS users may encounter compatibility issues due to differences in
/procfilesystem implementation.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-globalcaos-subagent-overseer": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, code-execution
Related Skills
jarvis-voice
Turn your AI into JARVIS. Voice, wit, and personality — the complete package. Humor cranked to maximum.
shell-security-ultimate
Classify every shell command as SAFE, WARN, or CRIT before your agent runs it.
memory-pioneer
Benchmark your agent's memory. Contribute anonymized scores to open research. Citizen science for AI memory.
agent-memory-ultimate
Give your OpenClaw agent a memory system that actually works across sessions. Research-backed. Open source.
model-router
Automatic LLM model selection for sub-agent tasks. Classifies tasks by complexity and type, then routes to the optimal model (cost vs capability). Use when spawning sub-agents, choosing models for cron jobs, or deciding which model to use for any task. Eliminates manual model specification by providing a decision tree and optional cheap-model classifier for ambiguous cases.