fleet-idle

Scan idle fleet nodes for plans, messages, and untested commits to surface work.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-idle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-idle
Source: https://github.com/supportersimulator/multi-fleet/tree/main/skills/fleet-idle
Command: npx skills add https://github.com/supportersimulator/multi-fleet --skill fleet-idle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Idle fleet nodes sit idle, wasting compute cycles; this skill automatically scans potential work sources to surface actionable suggestions.

Core Features & Use Cases

  • Scans incomplete plan items in docs/plans for TODOs and unresolved tasks
  • Reads unprocessed fleet messages from per-node inboxes
  • Detects recently untested commits and surfaces candidate work
  • Broadcasts suggestions to fleet nodes to maintain momentum

Quick Start

Analyze idle nodes and surface concrete tasks to keep the fleet productive.

Frequently Asked Questions about fleet-idle

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

FAQPage Schema
How do I find productive work for idle fleet nodes?

To find productive work for idle fleet nodes, you can use a watchdog-driven idle scanner to automatically identify untested commits, unresolved plan TODOs, and unprocessed fleet messages, then surface those as actionable tasks.

How does a watchdog scanner detect tasks for idle compute nodes?

A watchdog scanner detects tasks by triggering after a node remains idle for a defined period, scanning plans, fleet inboxes, and recent commits, then writing actionable work suggestions to a temporary JSON file for broadcast.

What's the best way to surface untested commits to idle fleet nodes?

The best way to surface untested commits to idle fleet nodes is to run an automated idle scanner that detects recently untested code, evaluates it as candidate work, and broadcasts the suggestions across the fleet to maintain momentum.

Can I broadcast work suggestions across fleet nodes automatically?

Yes, you can broadcast work suggestions across fleet nodes automatically. The scanner compiles actionable tasks from unprocessed messages and plan items, writes them to a JSON file, and distributes them to other nodes.

How often does a fleet idle scanner check for available work?

A fleet idle scanner checks for available work using a 10-minute cooldown period. Once a node is identified as idle, the watchdog waits for this interval to elapse before scanning plans and commits again.

Does an idle fleet scanner require external dependencies to run?

No, an idle fleet scanner does not require external dependencies to run. It operates independently by reading local plan documents, scanning commit histories, and checking per-node inboxes to generate work suggestions.