Skill3.5k repo starsupdated 3d ago

orchestrator-capacity

Historical reference for script-owned loop capacity requests. Do not use from provider sessions.

View source Repository: claude_codex_bridge

Install in Claude Code

Copy

git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge /tmp/orchestrator-capacity && cp -r /tmp/orchestrator-capacity/docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.ccb_orchestrator/adapters/ccb/skills/orchestrator-capacity ~/.claude/skills/orchestrator-capacity

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Orchestrator Capacity Reference

This reference is retained for rolepack history only. It is not projected as an
active provider skill for `agentroles.ccb_orchestrator`.

Loop capacity is now runner-owned. The orchestrator may recommend the semantic
need for capacity, but the supervisor/runner script performs any actual
capacity ensure, status, release, routing, and cleanup.

## Provider Boundary

- Do not run CCB commands.
- Do not inspect runtime capacity from the provider session.
- Do not release agents, mutate task status, import artifacts, or route work.
- Do not invent agent names, windows, panes, provider profiles, or topology.

## Reply Shape

When capacity information is needed, reply with semantic evidence only:

- requested profiles and counts;
- task packet and verification refs;
- blockers or missing evidence;
- release-readiness recommendation based on supplied worker/reviewer evidence.

The runner owns command execution and treats provider replies as evidence only.

More from this repository

ccb-githubSkill

Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state, or GitHub Actions release/test status.

decisionsSkill

ccb-configSkill

Private built-in CCB configuration skill for agentroles.ccb_self. Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs. Use only inside ccb_self; non-self agents should delegate CCB config changes to ccb_self.

ccb-self-chainSkill

Diagnose and repair CCB ask/job/message/reply/artifact/callback lineage. Use for missing replies, incomplete artifacts, pending callbacks, retry/resubmit/ack decisions, reply delivery problems, or work-chain resume advice.

ccb-self-diagnoseSkill

Diagnose CCB runtime, mounted daemon graph, tmux namespace and panes, provider context, queue/inbox/trace, replies/artifacts, config drift, and storage boundaries. Use when the user asks what is broken, which agent is stuck, whether CCB is mounted, why a reply did not arrive, or what to check first.

ccb-self-recoverSkill

Recover CCB agents, panes, mounts, provider contexts, API/provider failures, config reload aftermath, clear operations, and guarded single-agent restarts. Use when the user asks to fix, recover, restart if safe, clear context, reload, remount, or keep work going after provider/API failure.

askSkill

Send a request to a CCB agent with `ask`.

ccb-clearSkill

Clear CCB managed agent conversation context with `ccb clear`. Use when the user writes `$ccb-clear`, `$ccb_clear`, or asks to clear/reset one or more CCB agent contexts without restarting or deleting project state.