CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-management

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.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./manager/agent/skills/team-management/SKILL.md
SKILL.md
Quality
Evals
Security

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

Before creating a Team, read references/create-team.md and confirm its Team Admin. If the requester has not specified one, ask them to choose the current conversation user or another existing Human using the team-admin dropdown described there. Wait for their selection; never silently assign Global Admin.

# 1. Create each Worker CR with worker-management, then reference them
agt create team \
  --name <TEAM_NAME> \
  --leader-name <LEADER_NAME> \
  --admin <HUMAN_RESOURCE_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
  • Choose Team Admin explicitly — use agt create team --admin <HUMAN_RESOURCE_NAME>; the wrapper uses --team-admin. Global Admin is only the legacy API fallback, not your choice on the requester's behalf.
  • 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)
Repository

agentscope-ai/AgentTeams

Path

manager/agent/skills/team-management/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.