CtrlK
BlogDocsLog inGet started
Tessl Logo

orchestrator-capacity

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

44

Quality

46%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.ccb_orchestrator/adapters/ccb/skills/orchestrator-capacity/SKILL.md
SKILL.md
Quality
Evals
Security

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.

Repository
SeemSeam/claude_codex_bridge
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.