Skip to content
cccskills
FreePublished on GitHub

team-management

Guides the creation, import, and composition of agent teams with one Team Leader and multiple Workers. It explains member changes, delegation through the Leader, and where to manage each Worker's runtime settings and lifecycle.

OriginalShow the original description

Use when admin requests creating a team, importing a team, managing team composition, adding/removing workers from a team, or delegating tasks to a Team Leader.

See how to install

Good for

  • Creating or importing an agent team
  • Adding or removing team Workers
  • Delegating work through a Team Leader
  • Changing a Worker's CPU or memory settings

Files included (5)

  • SKILL.md2.6 KB
  • references/create-team.md1.7 KB
  • references/team-lifecycle.md1.7 KB
  • references/team-task-delegation.md3.5 KB
  • scripts/create-team.sh1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Team Management

A Team consists of 1 Team Leader + N Workers. The Team Leader is a special Worker with management skills that handles task decomposition and assignment within the team. Manager delegates tasks to Team Leaders, not directly to team workers.

Quick Create

# 1. Create each Worker CR with worker-management, then reference them
agt create team \
  --name <TEAM_NAME> \
  --leader-name <LEADER_NAME> \
  --workers <w1>,<w2>

# 2. @mention the Leader in Leader Room to assign task

The Team command fails if a referenced Worker does not exist. Configure model, runtime, image, resources, identity, skills, MCP, channel policy, and lifecycle on each Worker CR. After Team reconciliation, @mention the Leader in the Leader Room; the Leader will coordinate referenced workers in the Team Room.

Full workflow: read references/create-team.md

If admin asks for CPU or memory requests/limits, update Worker.spec.resources. Changing resources recreates that Worker's container, so confirm it is not mid-task.

Gotchas

  • Team Leader is a Worker container — same runtime, but with team-leader-agent skills instead of worker-agent skills
  • Team workers only talk to their Leader — their groupAllowFrom has [Leader, Team Admin], NOT Manager
  • Manager only talks to Team Leader — never @mention team workers directly
  • Team Room includes Team Admin — it's Leader + Team Admin + all team workers (no Global Admin unless they are Team Admin)
  • Leader Room is standard 3-party — Manager + Global Admin + Leader (same as regular worker room)
  • Leader DM is Team Admin ↔ Leader — for team-level management
  • Team Admin defaults to Global Admin — if --team-admin not specified
  • Delegated tasks use --delegated-to-team — so heartbeat knows to check with Leader, not workers
  • Team never owns Worker runtime configuration or lifecycle — update the referenced Worker CR directly

Operation Reference

Admin wants to...ReadCommand
Create a new teamreferences/create-team.mdagt create team
Understand team lifecyclereferences/team-lifecycle.md—
Delegate task to teamreferences/team-task-delegation.md—
Add/remove worker from teamreferences/team-lifecycle.mdagt get team
Stop/delete a member Workerreferences/team-lifecycle.mdscripts/lifecycle-worker.sh (per worker)

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

  • Find a suitable worker for an unassigned task
  • Compare Nacos worker candidates before importing
  • Import a worker from a specified nacos package URI
agentscope-ai/AgentTeams5.8KUpdated Oct 17, 2026

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.

  • Moving standalone OpenClaw into AgentTeams
  • Reviewing required tool dependencies
  • Adapting role instructions for a Worker
agentscope-ai/AgentTeams5.8KUpdated Oct 17, 2026

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.

  • Identify who sent a message in a room
  • Add or remove trusted contacts
  • Configure the administrator's primary notification channel
agentscope-ai/AgentTeams5.8KUpdated Oct 17, 2026

coding-cli

FreeSummary

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.

  • Delegating code implementation or bug fixes to an AI CLI
  • Writing coding requests with clear acceptance criteria
  • Reviewing and testing changes returned by a CLI
agentscope-ai/AgentTeams5.8KUpdated Oct 17, 2026

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.

  • Running coding tools for worker agents
  • Detecting and selecting available coding CLIs
  • Setting Qwen Code permissions and time budgets
agentscope-ai/AgentTeams5.8KUpdated Oct 17, 2026

communication

FreeSummary

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.

  • Reporting task completion to a coordinator
  • Raising blockers or questions that need action
  • Reducing repetitive acknowledgments
agentscope-ai/AgentTeams5.8KUpdated Oct 17, 2026

See all skills by agentscope-ai

Report a problem with this skill