skills.rest
chenziyang110
chenziyang110COMMUNITY
Explore all skills by this author →
GitHub

worker

I'm sorry, I can't answer that.

7|Updated Apr 7, 2026
Search Tags:#worker protocol#task claiming#agentteams#state root#inbox mailbox#sp-team
One-click install
npx skills add https://github.com/chenziyang110/spec-kit-plus --skill worker-chenziyang110
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/chenziyang110/spec-kit-plus/tree/main/extensions/agent-teams/engine/skills/worker
Command: npx skills add https://github.com/chenziyang110/spec-kit-plus --skill worker-chenziyang110

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps AgentTeams worker panes reliably coordinate task intake, acknowledgement, claiming, and completion using the shared team state and runtime CLI.

Core Features & Use Cases

  • Inbox-driven task intake: Reads the worker inbox and task files from the shared state root for deterministic execution.
  • Claim and lifecycle control: Claims tasks before working and completes or fails using the lifecycle APIs rather than editing task JSON directly.
  • Mailbox communication: Lists and marks mailbox messages as delivered to support leader-to-worker coordination.

Quick Start

Tell your AI to act as the AgentTeams worker by reading its inbox and claiming the next task it finds using sp-team.

Frequently Asked Questions about worker

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

FAQPage Schema
How do I coordinate AgentTeams worker task claiming from a shared state root?▼

AgentTeams worker task claiming reads inbox and task JSON from a shared state root, then uses sp-team CLI JSON APIs to acknowledge, claim, and complete tasks for deterministic execution.

What is the worker protocol for managing task lifecycle in shared team state?▼

The worker protocol manages task lifecycle by reading worker inboxes and task files from a shared state root, invoking sp-team CLI APIs to claim, complete, or fail tasks without directly editing task JSON.

How do I handle mailbox delivery tracking for leader-to-worker coordination?▼

Mailbox delivery tracking for leader-to-worker coordination lists and marks mailbox messages as delivered using sp-team CLI APIs, ensuring deterministic runtime communication between leader and worker panes.

Do I need SP_TEAMS_WORKER identity to process tasks from a shared state root?▼

Yes, SP_TEAMS_WORKER identity is required to satisfy deterministic runtime requirements when reading inbox and task JSON from the state root and invoking sp-team CLI APIs for task lifecycle operations.

Why does my AgentTeams worker fail to claim tasks from the shared state root?▼

AgentTeams worker task claiming fails when the worker does not use SP_TEAMS_WORKER identity or attempts to edit task JSON directly instead of invoking sp-team CLI lifecycle APIs for claim and completion operations.

Can I edit task JSON directly instead of using lifecycle APIs for worker task completion?▼

No, worker task completion requires invoking sp-team CLI lifecycle APIs rather than editing task JSON directly, ensuring deterministic state root coordination and proper mailbox delivery tracking across AgentTeams.

Related Skills

Explore More Software Engineering Skills→
RJJJJRJJJJ

team

Coordinate N agents with tmux-based OMX orchestration runtime.

Community
Advanced
TienchingTienching
3

worker

Operate a tmux-based team worker with startup ACK and task lifecycle.

Community
Intermediate
TienchingTienching
3

team

Coordinate multiple autonomous agents in tmux panes with shared state and mailbox communication.

Community
Intermediate
YeaChan05YeaChan05

team

Coordinate OMX agents in a tmux-based shared task environment.

Community
Advanced