worker

Coordinate worker startup, task claiming, and lifecycle via the forge CLI.

Updated Apr 10, 2026

Search Tags:#cli #worker #team #task #forge #mailbox

Ready to run

npx skills add https://github.com/lpjhelder/kronon-forge --skill worker-lpjhelder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/lpjhelder/kronon-forge/tree/main/skills/worker
Command: npx skills add https://github.com/lpjhelder/kronon-forge --skill worker-lpjhelder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams using Forge need reliable worker processes that can acknowledge their startup, read assigned tasks, claim work safely, and communicate status back to the team leader without manual intervention.

Core Features & Use Cases

Startup ACK: Sends a deterministic acknowledgment to the team leader before any task execution.
Inbox & Task Lifecycle: Reads the worker’s inbox, claims the first unblocked task, and transitions its status using the forge CLI.
Mailbox Interaction: Retrieves messages from the mailbox, acknowledges delivery, and replies with short ACKs when required.
State‑First Discipline: All actions are driven by the team state and CLI interop, avoiding ad‑hoc triggers.

Quick Start

Initialize a worker session and let it automatically process its inbox tasks according to the team protocol.

Frequently Asked Questions about worker

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

FAQPage Schema

How do I coordinate worker initialization and task claiming in a Forge team?▼

To coordinate worker initialization and task claiming, the system sends a deterministic startup acknowledgment to the team leader, reads the worker inbox, and claims the first unblocked task using the forge CLI. It relies on FORGE_TEAM_WORKER and FORGE_TEAM_STATE_ROOT environment variables to enforce deterministic state-first operations.

What is automated worker lifecycle management for tmux-based Forge teams?▼

Automated worker lifecycle management handles startup acknowledgments, inbox reading, task claiming, and status reporting for tmux-based Forge teams without manual intervention. All actions are driven by team state and CLI interop to maintain deterministic execution.

How do I safely claim tasks and report status using the Forge CLI?▼

Safely claim tasks and report status by reading the worker inbox, claiming the first unblocked task, and transitioning its status using the forge CLI. This process ensures safe task claiming and accurate status reporting back to the team leader via deterministic state-first operations.

Do I need environment variables to manage Forge team worker processes?▼

Yes, you need the FORGE_TEAM_WORKER and FORGE_TEAM_STATE_ROOT environment variables to manage Forge team worker processes. These variables are required to enforce deterministic state-first operations and coordinate task claiming and lifecycle management via the forge CLI.

How does mailbox interaction work for Forge team workers?▼

Mailbox interaction for Forge team workers retrieves messages from the mailbox, acknowledges delivery, and replies with short ACKs when required. This ensures reliable communication and status reporting back to the team leader without manual intervention.

What are the limitations of using state-first discipline for Forge worker coordination?▼

The limitation of state-first discipline for Forge worker coordination is that all actions must be driven by team state and CLI interop, avoiding ad-hoc triggers. This requires strict adherence to the forge CLI protocol and proper environment variable configuration, limiting spontaneous or manual task execution.