AgentTeams
Review Skills in agentscope-ai/AgentTeams, with license, maintenance context, and source paths.
- Skills
- 10
- Repository stars
- 5,317
- Identity status
- Source-linked
Provenance
Source and identity
- Profile type
- Repository
- Canonical name
- AgentTeams
- Public sources
- 1
- License context
- Apache-2.0
Source entries
Agent Skills from AgentTeams
Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.
agentscope-ai/AgentTeams
coding-cli
Use it for engineering and operations tasks; the detail page covers purpose, installation, and practical steps.
agentscope-ai/AgentTeams
communication
Use before sending or suppressing any Leader message to Workers, Manager, or Team Admin. Always use this skill for cross-room Matrix messages, @mention decisions, task assignment notifications, structured status reports, completion reports, blocker/revision messages, questions, requester updates, or when deciding whether a same-room reply is enough.
agentscope-ai/AgentTeams
git-delegation
Use it for operations tasks; the detail page covers purpose, installation, and practical steps.
agentscope-ai/AgentTeams
github-operations
Use it for code review and operations tasks; the detail page covers purpose, installation, and practical steps.
agentscope-ai/AgentTeams
project-management
Use before any projectflow call or Team Leader workflow involving Project state, Project lifecycle, DAG planning, Loop planning, ready node checks, pause/resume/complete, project recovery, heartbeat project checks, or project-level result aggregation. Always use team-coordination first when the question is how to organize the work.
agentscope-ai/AgentTeams
task-management
Use before any Leader taskflow call or task-level workflow involving delegating a ready DAG or Loop node, writing task meta/spec, checking a Worker task result, handling result statuses, task directory ownership, or Worker result contracts. Always use this skill when the request mentions delegate_task, check_task, task result.md, task spec.md, BLOCKED, REVISION_NEEDED, INTERRUPTED, SUCCESS, or assigning/delegating a Worker task.
agentscope-ai/AgentTeams
teamharness-communication
Use for TeamHarness message delivery details after a flow has decided a message must be sent: current-session reply, NO_REPLY, cross-room/cross-channel message tool payloads, PROJECT_REQUESTED task-room handoff, and requester replyRoute reports. Do not use to choose work mode, create rooms, delegate, check, or accept tasks.
agentscope-ai/AgentTeams
teamharness-project-management
Use when a Leader maintains durable TeamHarness project state for Quick Task or Project Work: create_quick_project, create_project, plan_dag, plan_loop, ready_nodes, resolve_project, accept_task_result, project completion, and requester report state. Do not use to create Matrix task rooms or send messages.
agentscope-ai/AgentTeams
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
agentscope-ai/AgentTeams
workerflow-internal-workflow
Use when a QwenPaw-backed Worker needs to decide whether to do work directly, use native subagents for internal parallelism, or create a temporary QwenPaw agent with a custom AGENTS.md and skills.
Pinned paths
Every entry links to a specific source path and commit when available.
Repository context
Activity, license, and repository-level popularity are shown as context.
Open the source
Inspect the public repository