New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Qwen Code Team Coordinator

by QwenLM in QwenLM/qwen-code

Leads a small team of Qwen Code teammates: read-only investigators work in parallel, then one writer pinned to a git worktree makes the changes.

Apache-2.0Auto-check passedAgent Workflows

Install Qwen Code Team Coordinator

skills CLI
$ npx skills add QwenLM/qwen-code --skill coordinate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install QwenLM/qwen-code coordinate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/QwenLM/qwen-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/src/skills/bundled/coordinate .claude/skills/coordinate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
coordinate
GitHub stars
28k
Token cost
~994 tokens
SKILL.md length
540 words
Files
1
Skills in repo
41
Repo updated
First seen
Licence
Apache-2.0

At a glance

Leads a small team of Qwen Code teammates: read-only investigators work in parallel, then one writer pinned to a git worktree makes the changes.

  • Works in 4 steps: Create one team and one self-contained… → Spawn named investigation teammates with… → Assign tasks and let teammates… → …
  • Splitting a broad investigation across several parallel read-only agents
  • SKILL.md covers Build one bounded team, Pin the only writer to a… and Keep coordination bounded
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The agent acts as team leader. When team_create is available it makes one team and one self-contained task per investigation workstream, spawns named read-only teammates (three at most is preferred, and never above the configured cap), lets them share findings through send_message and the shared task list, and accepts or rejects each result on its evidence. Read-only workers have a runtime-enforced allowlist with no shell, file writes, memory saves, schedules or agent spawning.

If code must change, the leader finishes the investigation first, shuts down the investigators, calls enter_worktree once, and spawns exactly one general-purpose writer working inside that path. The leader then reviews the result and alone decides how to integrate it. When the checkout is not a Git repository or worktree creation fails, every teammate stays read-only and the leader makes the final change. The team is shut down and deleted after synthesis.

When your agent uses it

  • Splitting a broad investigation across several parallel read-only agents
  • Making a code change with one isolated writer reviewed by the leader
  • Reconciling conflicting evidence from different investigators

Example prompts

  • “/coordinate Find out why the settings dialog loses state, using one investigator per module.”
  • “/coordinate Investigate three possible causes of the slow startup, then fix the confirmed one.”
  • “/coordinate Review the authentication package for gaps and report findings without changing code.”

Requirements

  • Qwen Code with the team_create tool available
  • A Git repository for the worktree-pinned writer

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Create one team and one self-contained task per current investigation workstream. Do not queue an implementation task while read-only…
  2. Spawn named investigation teammates with read_only: true — one per workstream, and prefer three at most. Never exceed the team's…
  3. Assign tasks and let teammates collaborate through send_message and the shared task list. Send targeted follow-ups when evidence…
  4. Accept or reject each result based on its evidence. Reassign rejected work instead of silently using it.

What it can do on your machine

Read from SKILL.md and the folder at commit 55ee50d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Qwen Code Team Coordinator loads about 994 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 540 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~994

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from QwenLM/qwen-code at commit 55ee50d, republished under its Apache-2.0 licence (© QwenLM). 540 words, ~994 tokens.

Download SKILL.mdSave it as .claude/skills/coordinate/SKILL.md (or your agent's skills folder).
name
coordinate
description
Coordinate a small team of Qwen Code teammates with enforced read-only workers, an optional worktree-pinned writer, shared tasks, peer messages, and existing Agent View tabs. Invoke explicitly with /coordinate.
argument-hint
<goal>
disable-model-invocation
true

Coordinate Qwen Code Teammates

Act as the team leader. Decompose the goal, keep task ownership clear, reconcile disagreements, and deliver the final result.

Build one bounded team

When team_create is available:

  1. Create one team and one self-contained task per current investigation workstream. Do not queue an implementation task while read-only teammates are idle because tasks are auto-assigned.
  2. Spawn named investigation teammates with read_only: true — one per workstream, and prefer three at most. Never exceed the team's configured cap, which team_create reports; spawning past it fails outright. Do not pass model; use the session-default model unless the selected agent definition explicitly overrides it.
  3. Assign tasks and let teammates collaborate through send_message and the shared task list. Send targeted follow-ups when evidence conflicts, a task needs clarification, or a result is incomplete.
  4. Accept or reject each result based on its evidence. Reassign rejected work instead of silently using it.

Read-only teammates have a positive execution allowlist. They cannot use shell, edit or write files, save memory, create schedules, invoke arbitrary deferred tools, or spawn agents. This is enforced by the runtime, not only by this prompt.

Pin the only writer to a worktree

When the goal requires code changes:

  1. Finish the parallel investigation first.
  2. Call request_shutdown for each investigation teammate. Once shutdown is pending, they are excluded from automatic task assignment.
  3. Call enter_worktree once and keep the returned path.
  4. Create the implementation task, then spawn exactly one named writer with subagent_type: "general-purpose" and working_dir: <path>. Do not set read_only for this teammate.
  5. Give the writer the accepted investigation evidence and require all changes to stay inside the worktree.
  6. Review and verify the worktree result. The leader alone decides whether and how to integrate it into the current branch.
  7. Do not remove the worktree until accepted changes have been integrated or deliberately discarded.

If the checkout is not a Git repository or worktree creation fails, keep all teammates read-only and let the leader make the final change in the current checkout.

Show full SKILL.md (201 more words)Show less

After synthesis, call request_shutdown for each still-active teammate, then delete the team.

The existing Agent View tabs show teammate conversations, messages, status, and approvals. Do not create another roster, session manager, or terminal UI.

If the Agent Team tools are unavailable, say that experimental.agentTeam must be enabled and Qwen Code restarted. Ordinary subagents are an acceptable fallback for parallel research, but describe them accurately: they report only to the leader and cannot collaborate as a team.

Keep coordination bounded

  • Use one teammate for a narrow task. Past roughly three, the leader spends more of its turn reconciling reports than doing the work, so add a fourth only when the workstreams are genuinely independent — and never past the configured cap.
  • Give every task an objective, scope, completion condition, and required evidence.
  • Default every teammate to read_only: true; add one worktree writer only when implementation is required.
  • Do not use Arena: it is for competing solutions to the same task, not collaboration on different tasks.
  • Do not claim that in-process teammates are independent PTY sessions or heterogeneous CLIs.
  • Finish implementation before running the smallest relevant verification once.

Return the outcome, material evidence or disagreements, changes made by the leader, verification, and remaining risks.

© QwenLM, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/core/src/skills/bundled/coordinate of QwenLM/qwen-code.

Open the folder on GitHubat commit 55ee50d

Compare with similar skills

Qwen Code Team Coordinator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Qwen Code Team Coordinator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qwen Code Team Coordinator this skillQwenLM/qwen-code28k—~994Automated safety check: PassApache-2.0
Agenthubalirezarezvani/claude-skills28k—~2kAutomated safety check: PassMIT
ClawTeam Multi-Agent Swarmwin4r/ClawTeam-OpenClaw1.5k1 repos~2.9kAutomated safety check: PassMIT
Clawteamwin4r/ClawTeam-OpenClaw1.5k—~3.1kAutomated safety check: PassMIT
Puppetmaster Agent Orchestrationprofessorpalmer/Puppetmaster467—~3.2kAutomated safety check: PassMIT
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0

Similar skills

  • Agenthub

    alirezarezvani/claude-skills

    Multi-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation.

    28k GitHub stars~2k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • ClawTeam Multi-Agent Swarm

    win4r/ClawTeam-OpenClaw

    Launches a swarm of specialist Hermes agents in git-worktree-isolated tmux windows with a kanban board and file-based inboxes, using built-in templates like hedge-fund and code-review.

    1.5k GitHub starsUsed in 1 repo~2.9k tokens
    Agent WorkflowsAuto-check passed

  • Clawteam

    win4r/ClawTeam-OpenClaw

    Multi-agent swarm orchestration. An agent skill from win4r/ClawTeam-OpenClaw.

    1.5k GitHub stars~3.1k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed

  • Puppetmaster Agent Orchestration

    professorpalmer/Puppetmaster

    Operates and supervises Puppetmaster, a multi-agent orchestrator, through its MCP tools or CLI, picking the right verb for edits, reviews, audits and long-running jobs.

    467 GitHub stars~3.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Agtx Task Sweep

    fynnfluegge/agtx

    Breaks a conversation's results into feature-level tasks and pushes them to the agtx kanban board, where each task gets its own worktree and agent session.

    1.7k GitHub stars~1.7k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed

More from QwenLM/qwen-code

All 41 skills in this repo

  • Agent Feature Reproduction

    QwenLM/qwen-code

    Reproduces a feature from Codex or Claude Code in Qwen Code by running the reference agent under capture, reading the traces, then implementing matching behavior.

    28k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Qwen Code E2E Testing

    QwenLM/qwen-code

    Guides end-to-end testing of the Qwen Code CLI in headless mode with real model calls, MCP test servers and inspection of raw API traffic.

    28k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Repo Hygiene Scan and Fix

    QwenLM/qwen-code

    Scheduled CI skill that scans a repository for small, certain docs, test and code hygiene issues and fixes them on one branch with a commit per finding.

    28k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Qwen Code Desktop Brand Builder

    QwenLM/qwen-code

    Builds a rebranded Qwen Code desktop package from the Tauri shell using only a brand id and a logo, with sensible derived defaults.

    28k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Qwen Code Memory Leak Debugger

    QwenLM/qwen-code

    Walks through capturing and comparing V8 heap snapshots to find memory leaks in the Qwen Code Node.js CLI, using tmux and the chrome-devtools CLI.

    28k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • tmux Real User Testing

    QwenLM/qwen-code

    Drives Qwen Code in a real tmux session the way a user would and saves a readable step-by-step transcript of each screen for maintainers to review.

    28k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Qwen Code Team Coordinator

What does Qwen Code Team Coordinator do?

Leads a small team of Qwen Code teammates: read-only investigators work in parallel, then one writer pinned to a git worktree makes the changes. The agent acts as team leader. When team_create is available it makes one team and one self-contained task per investigation workstream, spawns named read-only teammates (three at most is preferred, and never above the configured cap), lets them share findings through send_message and the shared task list, and accepts or rejects each result on its evidence.

When should I use Qwen Code Team Coordinator?

Qwen Code Team Coordinator fits situations like: splitting a broad investigation across several parallel read-only agents; making a code change with one isolated writer reviewed by the leader; reconciling conflicting evidence from different investigators.

How do I install Qwen Code Team Coordinator in Claude Code?

Run `npx skills add QwenLM/qwen-code --skill coordinate -a claude-code`. Or copy the skill folder (packages/core/src/skills/bundled/coordinate in QwenLM/qwen-code) into .claude/skills/coordinate in your project. Claude Code loads it when a task matches its description.

How do I install Qwen Code Team Coordinator in Codex?

Run `npx skills add QwenLM/qwen-code --skill coordinate -a codex`. Or copy the skill folder (packages/core/src/skills/bundled/coordinate in QwenLM/qwen-code) into .agents/skills/coordinate in your project. Codex loads it when a task matches its description.

Can I use Qwen Code Team Coordinator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add QwenLM/qwen-code --skill coordinate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/coordinate, .gemini/skills/coordinate, .github/skills/coordinate and .opencode/skills/coordinate in your project.

What does Qwen Code Team Coordinator need to run?

SKILL.md names no scripts, command-line tools or credentials: Qwen Code Team Coordinator is instructions for the agent only. Our summary lists: Qwen Code with the team_create tool available; A Git repository for the worktree-pinned writer.

Does Qwen Code Team Coordinator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Qwen Code Team Coordinator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Qwen Code Team Coordinator use?

Qwen Code Team Coordinator is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qwen Code Team Coordinator use?

About 994 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Qwen Code Team Coordinator?

Skills that share tags, products or a category with Qwen Code Team Coordinator: Agenthub (alirezarezvani/claude-skills, 28k stars), ClawTeam Multi-Agent Swarm (win4r/ClawTeam-OpenClaw, 1.5k stars), Clawteam (win4r/ClawTeam-OpenClaw, 1.5k stars) and Puppetmaster Agent Orchestration (professorpalmer/Puppetmaster, 467 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qwen Code Team Coordinator?

QwenLM (a GitHub organization) maintains it in QwenLM/qwen-code, which has 28,370 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 9, 2026.

Source: QwenLM/qwen-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.