mcpField
A
alera-orchestration

alera-orchestration

github.com/leynierAgent workflows4137 installsUpdated 3d ago
Repository

About alera-orchestration

A skill for agents coordinating work through the Alera runtime. It provides role-specific guidance for dispatch, coordination, messaging, and recovery while enforcing runtime lifecycle and workspace constraints.

Key features

  1. 01Role-specific orchestration guidance
  2. 02Dispatch acceptance and worker context
  3. 03Lifecycle-safe task completion
  4. 04Workspace and coordinator scoping
  5. 05Recovery, messaging, and ownership guidance

Use cases

  1. 01Accepting and completing a dispatched worker task
  2. 02Coordinating tasks within an active run
  3. 03Handling stalls, cancellation, or ownership transfer

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/leynier/alera --skill alera-orchestration

After installing, type/alera-orchestrationin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
coordinator.md
messaging.md
recovery.md
worker.md

Details

From the project README

Alera Orchestration

The runtime host owns lifecycle authority. Use its lifecycle commands, not generic messages or arbitrary status edits, for completion, cancellation, leases, and ownership.

Choose Your Role

  • Dispatched worker: accept first with alera orchestration dispatch-accept, then read alera orchestration --json context and worker. Follow the installed task and worker instructions.
  • Coordinator dispatching work or managing a run: read coordinator.
  • Stalled tasks, cancellation, gates, or ownership transfer: read recovery.
  • Message delivery or terminal inspection: read messaging.

Read only the references relevant to the current role. Worker completion is atomic and required exactly once; after successful completion, stop the turn and leave the terminal available for reuse.

Shared Constraints

Run inside an Alera terminal. ALERA_TERMINAL_HANDLE identifies the caller and ALERA_WORKSPACE_ID supplies the workspace default; alera orchestration current inspects both. Check alera version --json if compatibility is uncertain.

Scope every task to its workspace and coordinator. A workspace may have one active coordinator run; run tasks and injected workers must match that run's workspace and coordinator.

Honor prior explicit user authorization for the same scope without duplicate approval requests. Runtime policy approvals and user-owned stall gates still apply; never bypass them or invent a user decision. Active workers ask the coordinator through alera orchestration ask, not a local user-input prompt.

Comments

Markdown supported