OpenParable
Skip to content
← Back to skills

Team Management

Productivity
team-management

Team Management is an Agent Skill for productivity published in the agentscope-ai/AgentTeams repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/agentscope-ai/AgentTeams/blob/HEAD/manager/agent/skills/team-management/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/team-management, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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 (2 steps)

# 1. Create team via hiclaw CLI
hiclaw create team \
  --name <TEAM_NAME> \
  --leader-name <LEADER_NAME> \
  --leader-model <MODEL> \
  --workers <w1>,<w2>

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

After creation, the Leader is online in the Leader Room (Manager + Global Admin + Leader). @mention the Leader there to delegate the task — the Leader will decompose it and coordinate with team workers in the Team Room.

Full workflow: read references/create-team.md

If admin asks for CPU or memory requests/limits, use a YAML Team manifest with leader.resources and/or workers[].resources, then apply it with hiclaw apply -f. The simple hiclaw create team / hiclaw update team flags do not expose resource tuning. Changing member resources recreates the affected member container, so confirm the team 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
  • Controller forces runtime: copaw for all team members — omit runtime from team creation

Operation Reference

Admin wants to...ReadCommand
Create a new teamreferences/create-team.mdhiclaw create team
Understand team lifecyclereferences/team-lifecycle.md—
Delegate task to teamreferences/team-task-delegation.md—
Add/remove worker from teamreferences/team-lifecycle.mdhiclaw get team
Delete a team's containersreferences/team-lifecycle.mdscripts/lifecycle-worker.sh (per worker)