fleet-task

Dispatch session-aware agents to execute tasks across remote machines.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-machine orchestration of tasks by dispatching autonomous, session-aware agents to remote nodes, reducing manual coordination and delays.

Core Features & Use Cases

  • Session-aware execution: agents access the target machine's active session to avoid conflicts and align with ongoing work.
  • Autonomous task handling: agents execute the assigned task without human intervention, within defined turn limits.
  • Fleet-wide coordination: supports dispatch, tracking, and reporting results across multiple machines with visibility.

Quick Start

Dispatch a workload to a target machine and let an autonomous agent manage it without human intervention.

Frequently Asked Questions about fleet-task

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

FAQPage Schema
How do I dispatch autonomous tasks across multiple machines?

Cross-machine task dispatch works by spawning session-aware agents on target nodes to automate execution. A local fleet daemon coordinates provisioning, agent execution, and result collection across the fleet without manual intervention.

What is session-aware task execution in a fleet environment?

Session-aware execution allows autonomous agents to access the target machine's active session context. This prevents conflicts with ongoing work and aligns task execution with the current state of the remote node.

Do I need a local daemon to coordinate cross-machine task dispatch?

Yes, a local fleet daemon is required to orchestrate cross-machine task dispatch. It manages task provisioning, tracks agent execution, collects results, and enforces configurable limits like maxTurns and timeoutSeconds for safe operation.

What are the limitations of autonomous agent task dispatch?

Autonomous agents operate within a 25-turn limit and configurable timeoutSeconds to ensure safe, observable operation. Execution is bounded by these limits and requires access to the target session context to maintain awareness and avoid conflicts.

Can I configure turn limits and timeouts for autonomous agents?

Yes, you can configure maxTurns and timeoutSeconds to control autonomous agent execution. These configurable limits ensure safe, observable operation across the fleet while preventing runaway tasks on target machines.

What's the best way to orchestrate tasks across a fleet of machines?

Fleet-wide coordination dispatches autonomous, session-aware agents to remote nodes, reducing manual coordination delays. It supports dispatch, tracking, and reporting results across multiple machines with full visibility into task execution.