ava-fleet

Coordinates orchestrator and worker agents with missions, task tracking, and milestone-based reporting.

1|Updated Aug 14, 2026
One-click install
npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill ava-fleet-zhiyuan-zhang0206
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ava-fleet
Source: https://github.com/zhiyuan-zhang0206/Ava/tree/main/ava_builtins/plugins/ava_fleet/skills/ava-fleet
Command: npx skills add https://github.com/zhiyuan-zhang0206/Ava --skill ava-fleet-zhiyuan-zhang0206

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires redis, psycopg, and includes references (resource) components.

What problem does it solve? When a goal exceeds what a single agent run can accomplish, work must be decomposed, delegated, supervised, and aggregated across multiple agents without losing context or flooding the user with raw output. This Skill defines the operating rules for that multi-agent fleet: who spawns whom, how results roll up, and when the user is interrupted. ## Core Features & Use Cases - Orchestrator and worker role manuals: Reference guides cover spawning with missions and skill names, the explore-fork-join loop, goal watchers for supervision, and adversarial evaluation at reduce points. - Task-fleet interaction rules: Durable task registry conventions for creation, completion notification, blocker escalation, reassignment, cancellation, and automatic reminder escalation. - Effort and autonomy dials: Per-delegation control over model strength, decomposition depth, evaluation rigor, and how much the human decides, with budget ceilings metered by a usage script. - Use Case: You receive a goal too large for one run. You spawn a dedicated orchestrator that decomposes it, forks workers with named skills, supervises them with idle watchers, gathers results, and delivers one aggregated outcome while only decisions needing authorization reach the user. ## Quick Start Ask the agent to break a large goal into subtasks, spawn workers with named skills for each, and report back only at milestones or blockers.

Frequently Asked Questions about ava-fleet

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

FAQPage Schema
How do I spawn a worker agent with a mission?▼

Call ava.agents.spawn with a prompt containing the mission goal, the skill names the worker must load, and a milestone-based report-back contract. Pass label to name the role and fork_from to hand the worker your explored context.

How do I supervise a worker that might stall silently?▼

Launch a goal watcher based on the reference watch_idle.py script before the worker starts. It subscribes to the agent lifecycle event stream and messages you when the worker goes idle, so you judge output against the goal on every idle rather than trusting self-reports.

When should a worker message the user directly instead of its delegator?▼

A worker contacts the user directly only for authorization or decisions no agent can make, using ava.ui.notify with require_response. Progress and conclusions always roll up to the delegator via send_message for aggregation first.

What happens when a task is marked done in the fleet?▼

The worker notifies its delegator with the task id, result location, and a one-line summary, then ends its own process with ava.self.terminate. The notification plus recorded task results form the handoff, and a follow-up message resurrects the worker if needed.

How is budget enforced during autonomous batch work?▼

The spawner points a watcher at the reference usage.py script, which reports per-agent and total spend from the Loki event stream and cost ledger. Near the ceiling the worker is told to converge; over it, to clean up and stop, with no automatic force-kill.

When should I reuse an existing agent instead of spawning a new one?▼

Check neighbors and the agent list first: an agent whose label matches the domain already holds context, workspace, and memory for it. Messaging or resurrecting a terminated agent avoids the context-rebuild cost of a fresh spawn.