worker

Name: worker
Availability: InStock
Author: thanhquan3010

Execute beads autonomously within a defined track using Agent Mail.

Updated Mar 14, 2026

Search Tags:#automation #workflow #task management #agent #context persistence #bead execution

Ready to run

npx skills add https://github.com/thanhquan3010/hospital-management-system-v3 --skill worker-thanhquan3010

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worker
Source: https://github.com/thanhquan3010/hospital-management-system-v3/tree/main/.agents/skills/worker
Command: npx skills add https://github.com/thanhquan3010/hospital-management-system-v3 --skill worker-thanhquan3010

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the execution of individual tasks (beads) within a larger workflow (track), ensuring context is maintained between steps and progress is reported.

Core Features & Use Cases

Autonomous Execution: Runs through a sequence of beads, processing each one independently.
Context Persistence: Uses Agent Mail to pass information from one bead to the next.
Tool Integration: Leverages preferred tools defined in AGENTS.md for task completion.
Progress Reporting: Updates an orchestrator on the status of each bead and the overall track.
Use Case: In a software development epic, this worker skill can autonomously pick up coding tasks, implement changes, run tests, and report completion, moving the epic forward without constant human intervention.

Quick Start

Use the worker skill to execute the next bead in track number 5 for the project located at /path/to/project.

Frequently Asked Questions about worker

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

FAQPage Schema

How do I automate task execution within a workflow while maintaining context between steps?▼

Autonomous workflow execution is achieved by processing individual tasks sequentially while passing context between them via Agent Mail, ensuring each step retains the information needed to complete the larger operation.

How does bead-to-bead context persistence work in autonomous task management?▼

Bead-to-bead context persistence works by using Agent Mail to pass information from one executed task to the next, ensuring autonomous agents retain necessary context throughout a defined workflow track.

How do I execute the next bead in a specific track for my software project?▼

To execute the next bead in a track, invoke the worker skill with the specific track number and project path, allowing it to autonomously process the task and report progress to the orchestrator.

Can I use preferred tools defined in AGENTS.md for autonomous coding tasks?▼

Yes, autonomous task execution leverages preferred tools defined in AGENTS.md, allowing the agent to integrate specific development tools required for completing coding and testing tasks within an epic.

What is the best way to report progress on autonomous workflow tasks to an orchestrator?▼

The best way to report progress is through built-in orchestrator updates, where the agent sends status reports on each individual task and the overall workflow track after autonomous execution completes.

When should I use autonomous agent execution for deterministic task sequences?▼

Use autonomous agent execution for deterministic task sequences when you need to automate repetitive coding tasks, implement changes, and run tests within a software development epic without constant human intervention.