Retrieve shared reference files and send work in progress using local shared paths. The skill also guides missing-file checks and distinguishes manual file transfers from synchronization already handled by task acceptance and submission.
Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.
Review the instructions the agent will receive before you install.
Use local shared paths only. Do not expose storage internals.
Use:
shared/tasks/{task-id}/shared/projects/{project-id}/ only for read-only project contextDirectory sync paths must end with /. If a directory pull fails, report the filesync result instead of creating local placeholder directories or switching to absolute paths.
Do not use in chat, task outputs, or normal reasoning:
agentteams/agentteams-storage/...teams/{team}/shared/.../root/agentteams-fs/.../root/agentteams-fs/agents/...taskflow(action="ack_task") and taskflow(action="submit_task") handle all task lifecycle file sync internally (pull, push, stat). Do not call filesync separately for these operations.
For shared files outside the task lifecycle (project context, reference materials), call filesync before reading:
{
"action": "pull",
"payload": {
"path": "shared/projects/{project-id}/"
}
}
To push mid-task progress or non-result files that the coordinator needs before submission:
{
"action": "push",
"payload": {
"path": "shared/tasks/{task-id}/progress/",
"exclude": ["spec.md", "base/"]
}
}
Call filesync with action="pull" for shared/tasks/{task-id}/.
Check pwd, then check the local relative path from the task message:
pwd
ls -la
ls -la shared/tasks/{task-id}/
If still missing, @mention your coordinator with the filesync outcome and the exact local path you checked:
@coordinator:domain BLOCKED: I pulled shared/tasks/{task-id}/ but cannot find shared/tasks/{task-id}/spec.md.
Do not search random container absolute paths or create the missing task directory yourself.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.