- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add boshu2/agentops --skill orchestrate -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add boshu2/agentops --skill orchestrate -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add boshu2/agentops --skill orchestrate -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add boshu2/agentops --skill orchestrate -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/boshu2/agentops/tree/HEAD/plugin/skills/orchestrateDel publicador
This skill decides what each worker does next and launches it safely. The core
move: send free capacity to finished work that still owes checks, integration
or a judgment before starting anything new, and launch nothing until every
packet in the batch is valid with canonical write scopes that do not collide.
It worked when no finished-but-unchecked candidate waits while new work starts,
no task runs on a closed but unintegrated prerequisite, no two launched workers
share a canonical path or a contended resource, and each packet has a result
naming observed engagement, terminal status and not_as_briefed.
One agent and one writer is the default. Give work to parallel workers only where the pieces are independent: disjoint canonical write scopes and no contended runtime resource. Dependent or overlapping work stays with one writer or runs in sequence. Within that, concurrency follows the observed bottleneck: reserve capacity for integration, review and repair, and reduce new starts while candidates accumulate.
not_as_briefed (refused, held, worked around or unverified), the task is
not complete. A result marked out of authority is not a candidate. Retry
the step yourself only within your authority and the caller's limits, never
by the route the worker was denied. Otherwise integrate the finished part
only if it stands alone, and report the open step as a blocker.bd ready --exclude-type decision.Record only the concrete constraint and next action in the existing native handoff.
Dispatch a fresh implementer for one coherent accepted task through the runtime's task-only dispatch; a forked session, cleared summary or resumed author context still carries the history (RPI).
not_as_briefed; an authorized safer alternative stays
allowed (change safety).When several workers will apply one set of decisions, such as a batch of
review findings or one rewrite that must read the same in many files, open
decide once, apply in parallel
before splitting the work. When the caller wants file bytes kept out of its own
context, open context-budget delegation
before dispatching a bulk-reader or code-writer. When a packet is a
judgment leg, open model dispatch
before launch.
gaps. New
authorized work after a worker completes uses the runtime's follow-up or
resume operation that starts a turn; a queued message is not a resumed
attempt.out of authority, not a candidate, whatever its checks show.When a worker died, evidence disproves a running assignment's premise, a finished workspace is to be removed, or a caller-selected factory runs the work, open recover and resume.
Name the integration responsibility before launch, and decide then whether the integrated candidate needs a fresh judgment at all. Follow the consumer repository's integration policy and run affected checks on the actual integrated subject. Combine parallel results one at a time in dependency order and run the affected checks after each, so a failure points at one result; a merge without conflicts does not show that two changes work together. A result that conflicts, or whose changed paths or prerequisites changed on the target after it started, goes back to its author through a follow-up or is redone from the current target; it is not merged blind. A write outside a worker's declared scope, or recurring collisions, means the scope split cannot be trusted for this change: finish the rest serially.
For an ordinary candidate the integrated checks and CI are the gate; assign one fresh author-distinct judgment only in the costly cases Validate names. Preserve every explicitly required review leg; advisory Review, Plan challenge and Council advice cannot stand in for a judgment the caller requested (advice or acceptance). Known failures return to the responsible task for direct repair; a genuine causal stall gets RPI's one bounded helper.
packet_id: the caller's packet id
executor: selected runtime; requested model; observed model if reported
observed_session: session/context id the runtime reported, else unknown
engagement: observable evidence the worker started, else unobserved
last_activity: time and kind of the last observed tool call, output or file change, else unobserved
terminal_status: exit or terminal state | running | launch failed | not launched
result: candidate <ref> | evidence <ref> | out of authority <action> | error <verbatim>
not_as_briefed: worker-reported steps refused, held, worked around or unverified | none reported
gaps: recording failures, open choices and unknowns
Ask for not_as_briefed in the packet: a summary of what the worker did leaves
out what it did not do. Where the adapter returns its own denial record
(permission_denials, denied_actions), read that too and list a mismatch
under gaps.
When the caller asks for coordination status, return the status block; answer a quick question in prose.
Dispatch parallel workers without write collisions and decide what idle or finished ones do next. Use when: managing agents, or running or planning agents in parallel, even two.
---name: orchestratedescription: Dispatch parallel workers without write collisions and decide what idle or finished ones do next. Use when…---# plugin/skills/orchestrate/SKILL.mdPreguntas frecuentes
Descarga plugin/skills/orchestrate/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/boshu2/agentops.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.