Retinue
jklthinking/retinue
Coordinate work through a local Retinue workspace using its MCP tools.
Documents the metabot teams command surface for creating durable teams, spawning teammates, dispatching tasks and inspecting their runs across engine sessions.
Install MetaBot Agent Teams CLI
$ npx skills add xvirobotics/metabot --skill metabot-team -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install xvirobotics/metabot metabot-team --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/xvirobotics/metabot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/skills/metabot-team .claude/skills/metabot-team && rm -rf skills-srcUse ~/.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/
Install the "metabot-team" agent skill from https://github.com/xvirobotics/metabot/tree/main/packages/skills/metabot-team into .claude/skills/metabot-team/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metabot-team", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/xvirobotics/metabot/tree/main/packages/skills/metabot-teamType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add xvirobotics/metabot --skill metabot-team -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install xvirobotics/metabot metabot-team --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xvirobotics/metabot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/skills/metabot-team .agents/skills/metabot-team && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "metabot-team" agent skill from https://github.com/xvirobotics/metabot/tree/main/packages/skills/metabot-team into .agents/skills/metabot-team/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metabot-team", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add xvirobotics/metabot --skill metabot-team -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install xvirobotics/metabot metabot-team --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xvirobotics/metabot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/skills/metabot-team .cursor/skills/metabot-team && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "metabot-team" agent skill from https://github.com/xvirobotics/metabot/tree/main/packages/skills/metabot-team into .cursor/skills/metabot-team/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metabot-team", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/xvirobotics/metabot.git --path packages/skills/metabot-team--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add xvirobotics/metabot --skill metabot-team -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install xvirobotics/metabot metabot-team --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xvirobotics/metabot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/skills/metabot-team .gemini/skills/metabot-team && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "metabot-team" agent skill from https://github.com/xvirobotics/metabot/tree/main/packages/skills/metabot-team into .gemini/skills/metabot-team/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metabot-team", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install xvirobotics/metabot metabot-teamInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add xvirobotics/metabot --skill metabot-team -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/xvirobotics/metabot.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/skills/metabot-team .github/skills/metabot-team && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "metabot-team" agent skill from https://github.com/xvirobotics/metabot/tree/main/packages/skills/metabot-team into .github/skills/metabot-team/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metabot-team", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add xvirobotics/metabot --skill metabot-team -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install xvirobotics/metabot metabot-team --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/xvirobotics/metabot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/skills/metabot-team .opencode/skills/metabot-team && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "metabot-team" agent skill from https://github.com/xvirobotics/metabot/tree/main/packages/skills/metabot-team into .opencode/skills/metabot-team/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "metabot-team", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
metabot-team- GitHub stars
- 994
- Token cost
- ~693 tokens
- SKILL.md length
- 233 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Documents the metabot teams command surface for creating durable teams, spawning teammates, dispatching tasks and inspecting their runs across engine sessions.
- Creating a durable MetaBot team and spawning teammates into it
- SKILL.md covers Core Model, Inspect A Team, Create And Dispatch and Tasks And Runs, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Dispatching a task to a teammate and checking its run status
What it does
A Team is modeled as agents plus messages plus tasks plus runs: agents keep a stable team identity across separate engine sessions, messages are the normal conversational handoff, tasks record durable assignment, dependencies, status and result, and runs record each individual execution with its output, failure, retry or cancellation state; dispatching the same agent twice creates independent tasks and runs rather than reusing one. Inspecting a team uses status, agent-list and task-list commands with a summary or plain flag for concise output, since the default output is JSON.
Creating and dispatching work uses a create command, a spawn command with a role and prompt, and a dispatch command that creates the task, message and run projection the supervisor reads from; a teammate's final response returns through team state and the configured display destination. The default maximum parallel runs per agent is four, configurable with an environment variable. Run statuses are running, completed, failed and stopped, and the skill is explicit that team status and cards are only projections of the local team store, so bus or inbox delivery never gives a remote worker access to the sender's own store.
When your agent uses it
- Creating a durable MetaBot team and spawning teammates into it
- Dispatching a task to a teammate and checking its run status
- Inspecting a team's tasks and runs across sessions
Example prompts
- “Create a metabot team for the billing project and spawn a backend and a QA teammate.”
- “Dispatch this bug investigation to the backend teammate and show me the run status.”
- “List all pending tasks across my metabot teams.”
Requirements
- The metabot CLI
What it can do on your machine
Read from SKILL.md and the folder at commit 916637e. 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 (its code samples are bash).
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
MetaBot Agent Teams CLI loads about 693 tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 233 words of instructions outside code blocks.
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 xvirobotics/metabot at commit 916637e, republished under its MIT licence (© xvirobotics). 233 words, ~693 tokens.
Download SKILL.mdSave it as
.claude/skills/metabot-team/SKILL.md (or your agent's skills folder).- name
- metabot-team
- description
- Use for the MetaBot Agent Teams CLI: create and inspect durable Teams, spawn teammates, exchange messages, and manage Tasks and Runs across Sessions.
MetaBot Agent Teams CLI
This Skill documents the metabot teams command surface and its durable-state
semantics. It does not define Agent execution policy.
Core Model
Team = Agents + Messages + Tasks + Runs.
- Agents retain a stable Team identity across engine Sessions.
- Messages are the normal conversational handoff surface.
- Tasks record durable assignment, dependencies, status, and result.
- Runs record individual executions, output, failure, retry, cancellation, and card state.
- Multiple dispatches to the same Agent create independent Tasks and Runs.
Inspect A Team
metabot teams status <team> --summary
metabot teams agents list <team>
metabot teams tasks list <team> --summary
metabot teams runs list <team> --summary
metabot teams next <team> <member> --summary--summary or --plain selects concise output. The default output is JSON.
Create And Dispatch
metabot teams create <team> --description "..."
metabot teams agents spawn <team> <member> --role <role> --prompt "..."
metabot teams dispatch <team> <member> "<subject>" --description "..." --plain
metabot teams send <team> <member> "<message>" --from <sender>
metabot teams inbox <team> <member> --summarydispatch creates the Task/message/Run projection used by the supervisor. A
teammate's final response returns through Team state and the configured display
destination.
The default maximum parallel Runs per Agent is 4, configurable with
METABOT_AGENT_TEAM_MAX_PARALLEL_PER_AGENT.
Tasks And Runs
metabot teams tasks get <team> <taskId>
metabot teams tasks claim <team> <taskId> <member>
metabot teams tasks done <team> <taskId> "<result>"
metabot teams tasks block <team> <taskId> "<reason>" --blocked-by <id,id>
metabot teams runs list <team>
metabot teams runs output <team> <runId>
metabot teams runs stop <team> <runId>Run statuses are running, completed, failed, and stopped. Stopping a
supervisor-owned Run asks the bridge to stop the execution and prevents late
output from replacing terminal state. Assigned in-progress Tasks may return to
pending for retry.
Delivery Boundary
- Team status and cards are projections of the local Team store.
- Bus or inbox delivery does not give a remote worker access to the sender's local Team store.
- A wait timeout may leave durable Task/Run state pending; returned identifiers remain the recovery handles.
- The injected Team Context is a compact roster and dispatch hint. Tasks, messages, Runs, outputs, and member prompts remain query-only durable state.
© xvirobotics, MIT. 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/skills/metabot-team of xvirobotics/metabot.
Open the folder on GitHubat commit 916637e
Compare with similar skills
MetaBot Agent Teams CLI 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| MetaBot Agent Teams CLI this skillxvirobotics/metabot | 994 | — | ~693 | Automated safety check: Pass | MIT | |
| Retinuejklthinking/retinue | 117 | — | ~279 | Automated safety check: Pass | MIT | |
| Feishu Multi Agenthyperlist/feishu-multi-agent | 273 | — | ~419 | Automated safety check: Pass | None | |
| Team Agent Orchestrationaffaan-m/ECC | 276k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Edict Multi Agent OrchestrationLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.2k | Automated safety check: Pass | MIT | |
| Superset Agent Standupsuperset-sh/superset | 15k | — | ~712 | Automated safety check: Pass | Custom licence |
Similar skills
Feishu Multi Agent
hyperlist/feishu-multi-agent
飞书多 Agent 系统搭建指南。当用户要求创建新的功能 Agent、配置飞书群聊绑定、 搭建多 Agent 协作系统时激活此 skill。
Team Agent Orchestration
affaan-m/ECC
Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.
Edict Multi Agent Orchestration
LeoYeAI/openclaw-master-skills
Install and use the Edict (三省六部) multi-agent orchestration system with 12 specialized AI agents, real-time kanban dashboard, and audit trails
Superset Agent Standup
superset-sh/superset
Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.
Kimi Code Delegation
CherryHQ/cherry-studio
Delegates one bounded repository task to Kimi Code in non-interactive prompt mode and reads back the final result from its JSON event stream.
More from xvirobotics/metabot
Doubao Text-to-Speech Generator
xvirobotics/metabot
Generates Chinese speech audio from text using Volcengine's Doubao TTS API, for narration, voiceovers or multi-voice podcasts.
MetaBot Scheduler
xvirobotics/metabot
Schedules persistent cron and one-shot tasks on the MetaBot server that survive Claude session restarts and can be managed by other bots.
MetaBot CLI
xvirobotics/metabot
Documents the unified `metabot` CLI for personal memory, the skill hub, durable agent messaging, the agent registry, T5T status and scheduling.
Agent Team And Skill Builder
xvirobotics/metabot
Decides whether a request wants a full agent team, one agent, or one skill, then follows the matching flow file to generate it.
Related
Works with
Categories
Questions about MetaBot Agent Teams CLI
What does MetaBot Agent Teams CLI do?
Documents the metabot teams command surface for creating durable teams, spawning teammates, dispatching tasks and inspecting their runs across engine sessions. A Team is modeled as agents plus messages plus tasks plus runs: agents keep a stable team identity across separate engine sessions, messages are the normal conversational handoff, tasks record durable assignment, dependencies, status and result, and runs record each individual execution with its output, failure, retry or cancellation state; dispatching the same agent twice creates independent tasks and runs rather than reusing one. Inspecting a team uses status, agent-list and task-list commands with a summary or plain flag for concise output, since the default output is JSON.
When should I use MetaBot Agent Teams CLI?
MetaBot Agent Teams CLI fits situations like: creating a durable MetaBot team and spawning teammates into it; dispatching a task to a teammate and checking its run status; inspecting a team's tasks and runs across sessions.
How do I install MetaBot Agent Teams CLI in Claude Code?
Run `npx skills add xvirobotics/metabot --skill metabot-team -a claude-code`. Or copy the skill folder (packages/skills/metabot-team in xvirobotics/metabot) into .claude/skills/metabot-team in your project. Claude Code loads it when a task matches its description.
How do I install MetaBot Agent Teams CLI in Codex?
Run `npx skills add xvirobotics/metabot --skill metabot-team -a codex`. Or copy the skill folder (packages/skills/metabot-team in xvirobotics/metabot) into .agents/skills/metabot-team in your project. Codex loads it when a task matches its description.
Can I use MetaBot Agent Teams CLI 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 xvirobotics/metabot --skill metabot-team -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/metabot-team, .gemini/skills/metabot-team, .github/skills/metabot-team and .opencode/skills/metabot-team in your project.
What does MetaBot Agent Teams CLI need to run?
SKILL.md names no scripts, command-line tools or credentials: MetaBot Agent Teams CLI is instructions for the agent only. Our summary lists: The metabot CLI.
Does MetaBot Agent Teams CLI 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 MetaBot Agent Teams CLI 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 MetaBot Agent Teams CLI use?
MetaBot Agent Teams CLI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does MetaBot Agent Teams CLI use?
About 693 tokens (SKILL.md is roughly 2.8k 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 MetaBot Agent Teams CLI?
Skills that share tags, products or a category with MetaBot Agent Teams CLI: Retinue (jklthinking/retinue, 117 stars), Feishu Multi Agent (hyperlist/feishu-multi-agent, 273 stars), Team Agent Orchestration (affaan-m/ECC, 276k stars) and Edict Multi Agent Orchestration (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains MetaBot Agent Teams CLI?
xvirobotics (a GitHub organization) maintains it in xvirobotics/metabot, which has 994 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on September 15, 2026.
Source: xvirobotics/metabot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.