Coordinate changes to shared task folders with .processing marker files that indicate ongoing work. Managers and Workers check these markers before editing, synchronize files through MinIO, and remove markers after completing their changes.
中文简介正在准备中。当前显示英语简介。
Coordinate access to shared task directories using .processing marker files. Use before accessing a Worker's workspace to prevent conflicts when both Manager and Worker might modify files simultaneously.
安装前可以查看交给 AI 代理的指令内容。
This skill provides a general coordination mechanism for shared task directories. It prevents conflicts when both Manager and Workers need to access/modify the same task workspace.
When a Worker delegates work to Manager (e.g., git operations), the Manager modifies the Worker's workspace. During this time, the Worker might also be modifying files, causing potential conflicts.
Use .processing marker files to signal "work in progress". Any party (Worker or Manager) must check for this marker before modifying a task directory.
tasks/{task-id}/
├── workspace/ # Code workspace (shared between Worker and Manager)
├── notes/ # Worker's notes, plan.md, memory (not synced by Manager)
├── meta.json # Task metadata
└── .processing # Processing marker file (created when work in progress)
.processing MarkerLocation: tasks/{task-id}/.processing
{
"processor": "manager",
"started_at": "2026-02-25T10:30:00Z",
"expires_at": "2026-02-25T10:45:00Z",
"operation": "git-delegation"
}
| Field | Description |
|---|---|
processor | Who is processing: manager or worker name |
started_at | ISO 8601 timestamp when processing started |
expires_at | ISO 8601 timestamp when marker expires (15 min default) |
operation | What operation is in progress (optional) |
run_id | Optional unique identifier for your current operation; coding CLI execution requires it to match before passing through an active marker |
The marker auto-expires after 15 minutes (configurable). This prevents deadlocks if a process crashes without removing the marker.
Always follow this sequence:
Sync from MinIO first:
mc mirror "${AGENTTEAMS_STORAGE_PREFIX}/shared/tasks/${task_id}/" "/root/agentteams-fs/shared/tasks/${task_id}/"
Check for .processing:
bash /opt/agentteams/agent/skills/task-coordination/scripts/check-processing-marker.sh "$task_id"
If safe, create marker:
bash /opt/agentteams/agent/skills/task-coordination/scripts/create-processing-marker.sh "$task_id" "manager"
Perform modifications
Remove marker:
bash /opt/agentteams/agent/skills/task-coordination/scripts/remove-processing-marker.sh "$task_id"
Sync to MinIO:
mc mirror "/root/agentteams-fs/shared/tasks/${task_id}/" "${AGENTTEAMS_STORAGE_PREFIX}/shared/tasks/${task_id}/" --overwrite
Check if a task directory is being processed.
bash /opt/agentteams/agent/skills/task-coordination/scripts/check-processing-marker.sh <task-id>
Exit codes:
Create a processing marker for a task.
bash /opt/agentteams/agent/skills/task-coordination/scripts/create-processing-marker.sh <task-id> <processor-name> [timeout-mins] [run-id]
Parameters:
task-id: Task identifier (e.g., task-20260225-103000)processor-name: Who is processing (manager or worker name)timeout-mins: (Optional) Expiration timeout in minutes (default: 15)run-id: (Optional) Fresh identifier for your operation. Generate it once and pass it unchanged to your coding CLI wrapper and marker removal call. Existing calls without it retain the legacy marker format.Remove the processing marker after work is done.
bash /opt/agentteams/agent/skills/task-coordination/scripts/remove-processing-marker.sh <task-id> [run-id]
When you supply run-id, removal refuses to delete a marker belonging to a different run. Existing calls without it retain their original behavior.
This coordination mechanism is used by:
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Find worker agents in Nacos that match a task, recommend candidates, and import the administrator's chosen worker. It also supports importing a specified nacos package URI, with worker name confirmation and direct reporting of installation failures.
中文简介正在准备中。当前显示英语简介。
Prepare an existing OpenClaw setup for import as an AgentTeams managed Worker. Analyze tool dependencies, adapt role instructions and scheduled jobs, and build a ZIP package containing the configuration and custom image requirements.
中文简介正在准备中。当前显示英语简介。
Manage communication channels by identifying senders, maintaining trusted contacts, and setting the administrator's primary notification destination. It also covers first contact on a new channel and contacting the administrator across channels, with rules for handling unknown senders.
中文简介正在准备中。当前显示英语简介。
Prepare coding tasks for delegation to an authorized agent’s AI command-line tool. Set up and synchronize the workspace, write precise change requests, then review returned changes and run relevant checks before reporting completion.
中文简介正在准备中。当前显示英语简介。
Run AI coding command-line tools on behalf of worker agents using their prepared prompts and workspaces. Detect available tools, configure delegation, return results, and apply supported execution controls such as time budgets and permission settings.
中文简介正在准备中。当前显示英语简介。
Guide agent replies in Matrix chat rooms, including when to mention a coordinator, report completion, raise blockers, or answer questions. The rules limit repetitive acknowledgments and stop exchanges that add no new task, question, or decision.
中文简介正在准备中。当前显示英语简介。