Bootstrap LiteSuite worker agents with liteharness CLI registration and status reporting.
npx skills add https://github.com/ahostbr/liteharness --skill ls-worker
Please help me install this Agent Skill. Skill: ls-worker Source: https://github.com/ahostbr/liteharness/tree/main/liteharness/catalog/skills/ls-worker Command: npx skills add https://github.com/ahostbr/liteharness --skill ls-worker
It enables a consistent worker bootstrap process for the LiteSuite agent hierarchy by giving a worker a clear way to register with the harness and continuously report status back to a leader.
Start the worker by registering it with the harness using your environment-provided agent and canvas identifiers, then immediately send a “Worker ready” message to the leader.
High-intent search queries and answers about installing and using this skill.
Bootstrapping a worker agent for multi-agent orchestration requires registering it with a harness using environment-driven identity fields via liteharness CLI commands. The worker then sends a ready message to the leader, enabling task routing and continuous lifecycle reporting.
Pane and leaf canvas topology provides spatial self-awareness for agent coordination and parallelization. Workers use this session context to understand their location within the hierarchy and request splits when parallel work is needed during multi-agent execution.
Reporting execution state back to a leader agent involves sending structured messages for ready, progress, DONE, and BLOCKED outcomes. This structured messaging keeps the orchestration transparent and auditable throughout the worker lifecycle.
Yes, worker registration requires environment-driven identity fields, including agent and canvas identifiers. These variables allow the leader to deterministically route tasks to the correct agent session during the liteharness bootstrap process.
You should use a self-splitting worker in a parallel agent workflow when the assigned task requires parallelization. The worker can leverage canvas API calls to understand its pane or leaf location and actively request splits to distribute the workload.
The best way to coordinate multiple worker agents executing assigned tasks is through a hierarchical orchestration model. Workers register deterministically, checkpoint their progress, and report structured status outcomes back to a central leader for transparent management.
ahostbrBootstrap a leader and manage worker sessions via the LiteSuite bridge HTTP API.
djnsty23Summarize sprint progress and task status from prd.json sprint data.
fro-botCoordinate multi-agent swarms with task lists and dependency-based pipelines.
plurigridManage tmux sessions, windows, and panes across terminal workflows.
