Clarify responsibilities in a TeamHarness team, including planning, task execution, result acceptance, and runtime administration. Use the role boundaries to identify who owns each action and how participants should handle sensitive information.
Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work.
Review the instructions the agent will receive before you install.
Use this skill to reason about team roles and responsibility boundaries.
Leader owns planning, delegation, acceptance, and requester reporting. Workers own assigned task execution. Remote members participate as invited local agents or humans. Manager owns control-plane operations.
Do not let a Worker silently become project owner. Do not let a remote member act like a controller-managed Worker unless the team explicitly models that role.
Leader owns:
Worker owns:
shared/tasks/{task-id}/spec.mdshared/tasks/{task-id}/result.mdRemote member owns only the work explicitly assigned to that member. Treat remote members as participants, not controller-managed runtime resources.
Manager owns control-plane operations such as creating workers, changing model configuration, deploying teams, and managing runtime state. TeamHarness skills must not instruct agents to call control-plane APIs.
Never write secrets, credentials, tokens, authorization headers, or live runtime
state into TEAMS.md, project files, task specs, task results, or Matrix
messages. If a task needs credentialed access, refer only to the approved
credential name or environment variable name, not its value.
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.
Guides communication in Matrix agent teams by choosing recipients, rooms, and when to mention someone. It covers task notifications and progress reports, helping agents avoid duplicate assignments and send concrete updates to the appropriate requester.