ls-leader

Bootstrap a leader and manage worker sessions via the LiteSuite bridge HTTP API.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/ahostbr/liteharness --skill ls-leader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-leader
Source: https://github.com/ahostbr/liteharness/tree/main/liteharness/catalog/skills/ls-leader
Command: npx skills add https://github.com/ahostbr/liteharness --skill ls-leader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the coordination problem of spinning up multiple worker agents and keeping an orchestrator informed of their status and outputs during a LiteSuite session.

Core Features & Use Cases

  • Leader bootstrap & registration: Registers the leader agent with the harness using required LiteSuite environment identifiers.
  • Worker orchestration via bridge API: Creates split panels and spawns workers (including grid-style spawning) scoped to the current pane.
  • Messaging & reporting protocol: Reports READY, PROGRESS, DONE, and BLOCKED states back to the orchestrator, and relays worker status summaries.

Quick Start

Use the ls-leader skill to register the leader, spawn workers through the local bridge endpoint, and send READY and ongoing worker status updates to the orchestrator.

Frequently Asked Questions about ls-leader

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

FAQPage Schema
How do I coordinate multiple agent workers in a LiteSuite session?

To coordinate multiple agent workers in a LiteSuite session, you bootstrap a leader agent that registers with the harness and spawns workers through a scoped bridge HTTP API to manage pane splitting and task execution.

What is the best way to report agent worker status back to an orchestrator?

Reporting agent worker status back to an orchestrator involves sending structured READY, PROGRESS, DONE, or BLOCKED messages through the messaging protocol to relay worker states and outputs during the workflow.

How do I split terminal canvas panels for parallel CLI agent workflows?

Splitting terminal canvas panels for parallel CLI agent workflows is handled by the leader agent, which creates split panels and spawns grid-style workers scoped to the current pane using the bridge API.

Do I need specific environment variables to bootstrap a worker team?

Yes, bootstrapping a worker team requires reading specific LiteSuite identity environment variables to register the leader agent with the harness via the liteharness CLI before spawning any workers.

Can I manage ConPTY or PTY sessions during multi-agent orchestration?

Yes, you can manage ConPTY or PTY sessions during multi-agent orchestration, as the workflow applies to coding-CLI scenarios that require direct PTY session control and structured status reporting.

Why does my orchestrator not receive worker progress updates?

If your orchestrator is not receiving worker progress updates, the leader agent likely failed to properly relay worker status summaries or did not send the required PROGRESS messages through the orchestrator messaging protocol.