Check current AgentTeams membership, worker status, and messaging identifiers through the agt CLI. Use the returned team metadata to prepare task assignments, contact the appropriate rooms, and manage worker readiness, waking, or sleeping.
Use before any Leader action that depends on current team topology, worker list, worker phase, runtime, room ID, Matrix ID, Team Admin, human identity, or lifecycle state. Always use this skill when assigning tasks, sending cross-room messages, recovering projects, handling heartbeat, waking/sleeping workers, or when any worker/room/identity value might be stale.
Review the instructions the agent will receive before you install.
Use this skill for current AgentTeams topology and runtime state.
Use agt CLI. Do not infer organization state from memory, old chat history, SOUL.md, or AGENTS.md.
Resolve the Team CR name before any team-scoped CLI query. The team name in SOUL.md may be the runtime/storage teamName, not the Kubernetes Team CR name accepted by agentteams --team.
TEAM_CR="$(agt get workers "${AGENTTEAMS_WORKER_CR_NAME:-$AGENTTEAMS_WORKER_NAME}" -o json | jq -r '.team')"
agt get teams "$TEAM_CR" -o json
agt get workers --team "$TEAM_CR" -o json
agt worker status --team "$TEAM_CR"
Use the Team CR name for CLI filters and lifecycle commands. Use the returned teamName only as runtime/storage/display context. If agt get workers --team <name> returns no workers, re-check that you used the Team CR name from your own Worker metadata, not the runtime teamName.
Use the Team Room ID for normal task assignment notifications. Worker room IDs are for exceptional direct follow-up, not routine assignment.
Use lifecycle commands only after checking active project and task files.
agt worker ensure-ready --name <worker-name> --team "$TEAM_CR"
agt worker wake --name <worker-name> --team "$TEAM_CR"
agt worker sleep --name <worker-name> --team "$TEAM_CR"
If CLI output is missing a required room ID or Matrix ID, stop and report a metadata problem. Do not guess.
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.