Historical reference for script-owned loop capacity requests. Do not use from provider sessions.
Scanned 9/2/2026
Install to Claude Code
Skills Directorynpx -y skills add SeemSeam/claude_codex_bridge --skill orchestrator-capacity --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Orchestrator Capacity?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/seemseam-orchestrator-capacity)More formats (shields.io, HTML) on the badges page.
---
name: orchestrator-capacity
description: Historical reference for script-owned loop capacity requests. Do not use from provider sessions.
---
# 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.
