Skills

Skills are specialized instruction sets that teach agents how to perform specific tasks. Fleet ships with the fleet-orchestration skill — a set of instructions that enables agents to spawn, coordinate, and monitor child sessions for parallel work.

Skills are not installed by default. You install them through the Settings UI and assign them to the agents that need them.

Installing a Skill

From the Settings UI

1. Open the Fleet dashboard and click Settings in the sidebar
2. Switch to the Skills tab
3. Click Install Skill
4. Enter the URL to a SKILL.md file — for the built-in fleet-orchestration skill, use the raw GitHub URL from the Fleet repository
5. Click Install

The skill appears in the skills list after installation.

Via CLI

weave-fleet skill install <source>

The source can be:

Format	Example
Raw URL	https://raw.githubusercontent.com/.../SKILL.md
GitHub shorthand	github:user/repo/path/to/SKILL.md
Local file path	/home/dev/skills/my-skill/SKILL.md

To install and assign to agents in one step:

weave-fleet skill install <source> --agents loom tapestry

Managing Skills

Command	Description
weave-fleet skill list	List installed skills and their agent assignments
weave-fleet skill install <source>	Install a skill from a URL, GitHub shorthand, or local path
weave-fleet skill remove <name>	Remove a skill and unassign it from all agents

Assigning Skills to Agents

After installation, a skill must be assigned to the agents that should use it. Unassigned skills are installed but inactive.

From the Settings UI

1. Go to Settings > Skills
2. Find the skill card for the skill you want to assign
3. Click the agent badges (e.g., loom, tapestry) to toggle assignment on or off — highlighted badges indicate the skill is assigned to that agent

Via CLI

Pass --agents during installation:

weave-fleet skill install <source> --agents loom tapestry

TIP

Agent assignments are stored in ~/.config/opencode/weave-opencode.jsonc under agents.<name>.skills[]. You can also edit this file directly.

Fleet-Orchestration Skill

The fleet-orchestration skill ships with Fleet and teaches agents how to orchestrate multi-session workflows. When installed and assigned, agents can automatically spawn child sessions, delegate work in parallel, and collect results — all through the Fleet API.

What It Enables

Capability	Description
Parallel task execution	Agents spawn multiple child sessions to work on independent tasks simultaneously
Automatic parallelizability analysis	Agents assess file overlap between tasks before deciding to parallelize or serialize
Workspace isolation	Each child session gets its own worktree or clone, preventing conflicts
Callback-driven coordination	Parent agents wait for child completion callbacks instead of polling
Conflict detection	After children complete, the parent agent reviews diffs to detect overlapping changes
Error handling	Failed child sessions are inspected and retried or escalated automatically

Which Agents Need It

Assign the fleet-orchestration skill to Loom and Tapestry:

• Loom — the orchestrator agent. Uses the skill to analyze tasks, spawn child sessions, and coordinate parallel work
• Tapestry — the execution agent. Uses the skill when executing plan steps that involve multi-session delegation

Other agents (shuttle, thread, weft, etc.) do not need this skill — they operate within a single session and are spawned by the orchestrator, not the other way around.

Install and Assign

weave-fleet skill install <fleet-orchestration-skill-url> --agents loom tapestry

Or install via the Settings UI and toggle the loom and tapestry badges on the skill card.

How It Works

Once installed, the orchestrating agent follows a structured workflow when the user requests parallel work:

1. Analyze — assess whether tasks can safely run in parallel based on file overlap
2. Spawn — create child sessions with worktree isolation and onComplete callbacks
3. Prompt — send each child a scoped, self-contained task description
4. Wait — the agent waits for Fleet callbacks (no polling)
5. Inspect — review diffs from each child session and check for conflicts
6. Report — summarize results to the user, flagging any issues

For details on how sessions, isolation strategies, and callbacks work, see Session Management.

Removing a Skill

From the Settings UI

Click the remove button on the skill card in Settings > Skills. This deletes the skill and removes it from all agent assignments.

Via CLI

weave-fleet skill remove fleet-orchestration

This deletes ~/.config/opencode/skills/fleet-orchestration/ and removes the skill from all agents in weave-opencode.jsonc.