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.
Orchestrator 层定位、设计决策、与上下层的关系。开发者面向的 opinionated 库，Server 基于它构建。
Apache-2.0Auto-check passed
Install Orchestrator Usage
$ npx skills add stello-agent/stello --skill orchestrator-usage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stello-agent/stello orchestrator-usage --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/stello-agent/stello.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/orchestrator-usage .claude/skills/orchestrator-usage && 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 "orchestrator-usage" agent skill from https://github.com/stello-agent/stello/tree/main/.agents/skills/orchestrator-usage into .claude/skills/orchestrator-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-usage", 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/stello-agent/stello/tree/main/.agents/skills/orchestrator-usageType 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 stello-agent/stello --skill orchestrator-usage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stello-agent/stello orchestrator-usage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stello-agent/stello.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/orchestrator-usage .agents/skills/orchestrator-usage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orchestrator-usage" agent skill from https://github.com/stello-agent/stello/tree/main/.agents/skills/orchestrator-usage into .agents/skills/orchestrator-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-usage", 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 stello-agent/stello --skill orchestrator-usage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stello-agent/stello orchestrator-usage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stello-agent/stello.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/orchestrator-usage .cursor/skills/orchestrator-usage && 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 "orchestrator-usage" agent skill from https://github.com/stello-agent/stello/tree/main/.agents/skills/orchestrator-usage into .cursor/skills/orchestrator-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-usage", 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/stello-agent/stello.git --path .agents/skills/orchestrator-usage--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 stello-agent/stello --skill orchestrator-usage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stello-agent/stello orchestrator-usage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stello-agent/stello.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/orchestrator-usage .gemini/skills/orchestrator-usage && 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 "orchestrator-usage" agent skill from https://github.com/stello-agent/stello/tree/main/.agents/skills/orchestrator-usage into .gemini/skills/orchestrator-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-usage", 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 stello-agent/stello orchestrator-usageInstalls 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 stello-agent/stello --skill orchestrator-usage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stello-agent/stello.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/orchestrator-usage .github/skills/orchestrator-usage && 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 "orchestrator-usage" agent skill from https://github.com/stello-agent/stello/tree/main/.agents/skills/orchestrator-usage into .github/skills/orchestrator-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-usage", 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 stello-agent/stello --skill orchestrator-usage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stello-agent/stello orchestrator-usage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stello-agent/stello.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/orchestrator-usage .opencode/skills/orchestrator-usage && 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 "orchestrator-usage" agent skill from https://github.com/stello-agent/stello/tree/main/.agents/skills/orchestrator-usage into .opencode/skills/orchestrator-usage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-usage", 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
orchestrator-usage- GitHub stars
- 112
- Token cost
- ~406 tokens
- SKILL.md length
- 139 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Orchestrator 层定位、设计决策、与上下层的关系。开发者面向的 opinionated 库，Server 基于它构建。
- Works in 2 steps: 直接提供 runtime.resolver — 开发者自己适配… → 提供 session.sessionResolver +…
- SKILL.md covers 定位, 入口, 硬编码的 opinionated 行为 and Session 接入的两种方式, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Orchestrator Usage is an agent skill from stello-agent/stello. Orchestrator 层定位、设计决策、与上下层的关系。开发者面向的 opinionated 库，Server 基于它构建。
Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Conversations aren't linear — why should AI chats be? The first open-source conversation topology engine. Auto-branching session trees, inherited memory, star-map visualization… The licence is Apache-2.0.
Example prompts
- “/orchestrator-usage”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- 直接提供 runtime.resolver — 开发者自己适配 EngineRuntimeSession
- 提供 session.sessionResolver + consolidateFn — StelloAgent 自动适配 @stello-ai/session
What it can do on your machine
Read from SKILL.md and the folder at commit 3bc9493. 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
Orchestrator Usage loads about 406 tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 139 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 stello-agent/stello at commit 3bc9493, republished under its Apache-2.0 licence (© stello-agent). 139 words, ~406 tokens.
Download SKILL.mdSave it as
.claude/skills/orchestrator-usage/SKILL.md (or your agent's skills folder).- name
- orchestrator-usage
- description
- Orchestrator 层定位、设计决策、与上下层的关系。开发者面向的 opinionated 库，Server 基于它构建。
Orchestrator 层 — 面向开发者的编排库
定位
三层自由度递减：
- Session 层：纯库，完全 DI，零假设
- Orchestrator 层：库，但硬编码部分默认行为
- Server 层：框架，基于 orchestrator，加传输层
Orchestrator 和 Server 的分界线：transport 和 coordination 是正交的。串行队列、fork 路由、engine 生命周期管理跟"用 WS 还是 REST"无关。
入口
唯一推荐入口是 createStelloAgent(config)，返回 StelloAgent 实例。
StelloAgent 隐藏内部组件（orchestrator/factory/runtimeManager），只暴露操作方法。开发者通过 config 声明意图，不需要理解内部装配过程。
硬编码的 opinionated 行为
这些行为由 orchestrator 内部固定，开发者不能替换：
- 同 session 串行，不同 session 并行 — SessionOrchestrator 的 promise 链队列
- Engine hooks 合并 — Factory 将用户 hooks 和 Scheduler 闭包合并，同 key 下都触发
- Runtime ref-counting — acquire/release 引用计数，归零回收（可配 idleTtlMs 延迟）
- 显示拓扑由 SessionTree 直接维护 — fork 默认挂在 source 节点下（engine 用
options.topologyParentId ?? this.session.id兜底）。orchestrator 不做显示拓扑 的路由改写；调用方可通过显式传入topologyParentId覆盖。
可注入的扩展点
| 注入点 | 说明 | 默认值 |
|---|---|---|
| Scheduler | 调度时机 | 手动触发 |
| EngineHookProvider | 开发者自定义 hook | 无 |
| SplitGuard | fork 前置校验 | 无限制 |
| RuntimeRecyclePolicy | 空闲回收策略 | 立即回收 |
Session 接入的两种方式
- 直接提供 runtime.resolver — 开发者自己适配 EngineRuntimeSession
- 提供 session.sessionResolver + consolidateFn — StelloAgent 自动适配 @stello-ai/session
方式 2 是 @stello-ai/session 的推荐接入路径。
核心设计决策
- StelloAgent 是门面，不是组装器 — 隐藏内部组件，只暴露操作方法
- 只有一种 config 形状 — 没有 legacy 兼容路径，减少认知负担
- hooks 是不可变的开发期配置 — 构造时注入，运行期间不可修改
- Server 承接 StelloAgent — 通过 attach/detach 管理连接态，通过 turn/stream 转发请求
© stello-agent, 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 .agents/skills/orchestrator-usage of stello-agent/stello.
Open the folder on GitHubat commit 3bc9493
Compare with similar skills
Orchestrator Usage 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 |
|---|---|---|---|---|---|---|
| Orchestrator Usage this skillstello-agent/stello | 112 | — | ~406 | Automated safety check: Pass | Apache-2.0 | |
| Team Agent Orchestrationaffaan-m/ECC | 275k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Orca Orchestrationstablyai/orca | 87k | — | ~916 | Automated safety check: Pass | MIT | |
| Agent Orchestrator Taskruvnet/ruflo | 74k | 3 repos | ~1k | Automated safety check: Pass | MIT | |
| Plan Orchestrateaffaan-m/ECC | 275k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Orchestratesickn33/agentic-awesome-skills | 47k | 1 repos | ~692 | Automated safety check: Pass | MIT |
Similar skills
Orca Orchestration
stablyai/orca
Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…
Agent Orchestrator Task
ruvnet/ruflo
Agent skill for orchestrator-task - invoke with $agent-orchestrator-task
Plan Orchestrate
affaan-m/ECC
Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts.
Orchestrate
sickn33/agentic-awesome-skills
Coordinate focused subagents on substantial work, keep their ownership non-overlapping, and integrate verified results.
Swarm Orchestration
ruvnet/ruflo
Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.
More from stello-agent/stello
All 12 skills in this repoFork Design
stello-agent/stello
Fork 机制完整说明。覆盖 ForkProfile 与 EngineForkOptions 的字段对齐、四层 fallback 合成链（sessionDefaults → parent → profile → forkOptions）、systemPrompt 合成三种模式、skills 三态语义、持久化边界（SerializableSessionConfig 只固化…
LLM Call Sites
stello-agent/stello
Stello 框架内所有 LLM 调用位置的消息结构速查。覆盖 Session 对话、compress、consolidate；应用层 reflection 调用由 orchestrator 自行决定。
Session Usage
stello-agent/stello
Session 对话单元的设计理念、上下文组装规则、memory / insight 槽位语义、单一 Session 模型与跨 Session 通信模型。
Stello Agent Creation
stello-agent/stello
StelloAgent 创建配置教程。完整说明 createStelloAgent 的每个配置项，包含 sessionDefaults、storage、tools、skills、forkProfiles、session 层接入、orchestration 等。
Stello Agent Usage
stello-agent/stello
StelloAgent 运行时使用教程。覆盖 Session 生命周期、createSession、turn/stream 对话、fork 配置合成链、orchestrator-facing 数据 SDK、runtime 管理、热更新等运行时 API。
Stello Usage
stello-agent/stello
Stello 仓库总览入口。快速理解各包的关系、推荐入口、编排模型、单一 Session 模型. An agent skill from stello-agent/stello.
Questions about Orchestrator Usage
What does Orchestrator Usage do?
Orchestrator 层定位、设计决策、与上下层的关系。开发者面向的 opinionated 库，Server 基于它构建。. Orchestrator Usage is an agent skill from stello-agent/stello.
How do I install Orchestrator Usage in Claude Code?
Run `npx skills add stello-agent/stello --skill orchestrator-usage -a claude-code`. Or copy the skill folder (.agents/skills/orchestrator-usage in stello-agent/stello) into .claude/skills/orchestrator-usage in your project. Claude Code loads it when a task matches its description.
How do I install Orchestrator Usage in Codex?
Run `npx skills add stello-agent/stello --skill orchestrator-usage -a codex`. Or copy the skill folder (.agents/skills/orchestrator-usage in stello-agent/stello) into .agents/skills/orchestrator-usage in your project. Codex loads it when a task matches its description.
Can I use Orchestrator Usage 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 stello-agent/stello --skill orchestrator-usage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestrator-usage, .gemini/skills/orchestrator-usage, .github/skills/orchestrator-usage and .opencode/skills/orchestrator-usage in your project.
What does Orchestrator Usage need to run?
SKILL.md names no scripts, command-line tools or credentials: Orchestrator Usage is instructions for the agent only.
Does Orchestrator Usage 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 Orchestrator Usage 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 Orchestrator Usage use?
Orchestrator Usage 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 Orchestrator Usage use?
About 406 tokens (SKILL.md is roughly 1.6k 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 Orchestrator Usage?
Skills that share tags, products or a category with Orchestrator Usage: Team Agent Orchestration (affaan-m/ECC, 275k stars), Orca Orchestration (stablyai/orca, 87k stars), Agent Orchestrator Task (ruvnet/ruflo, 74k stars) and Plan Orchestrate (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orchestrator Usage?
stello-agent (a GitHub organization) maintains it in stello-agent/stello, which has 112 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 24, 2026.
Source: stello-agent/stello on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.