meta-orchestration

Orchestrates host-aware recurring runtime cycles that sync state, drain plan work, run e2e gates, and release.

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill meta-orchestration-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-orchestration
Source: https://github.com/8007342/tillandsias/tree/main/skills/meta-orchestration
Command: npx skills add https://github.com/8007342/tillandsias --skill meta-orchestration-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating unattended development cycles across a multi-host fleet (Linux, macOS, Windows, forge containers) is error-prone: agents lose uncommitted work, skip daily maintenance, overspend rate-limited token budgets, or exit without proof that commits reached the remote. This Skill provides a single top-level loop that classifies the host, runs daily maintenance gates, drains claimable plan work, executes e2e smoke gates, and enforces a strict commit-push-attest exit contract. ## Core Features & Use Cases - Invocation Modes: Full mode runs the complete cycle; Smoke Mode gives fast, cheap verification with a machine-greppable MO-SMOKE: PASS/FAIL verdict without touching the repo. - Terminal Attestation: Full mode must emit a derived MO-FULL: marker via scripts/mo-full-attest.sh self, proving local HEAD converged with the remote before exit. - Work Salvage: scripts/salvage-dirty-worktree.sh pushes dirty or stranded work to a salvage ref before any refusal, preventing loss of uncommitted work. - Token Budget Governance: Caps sub-agent counts, tiers models by task class, and logs token spend per cycle. - Use Case: An operator launches ./repeat --prompt "Use the /meta-orchestration skill" on a fleet host; the skill detects the host type, runs the daily maintenance gate once, claims and completes plan work, runs the build gate, commits, pushes, and emits a verified attestation marker. ## Quick Start Run the meta-orchestration skill on this host to execute a full unattended development cycle and end with a verified push attestation.

Frequently Asked Questions about meta-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an unattended development cycle across multiple hosts?▼

Invoke the skill with a bare prompt such as "Use the /meta-orchestration skill" via ./repeat. It classifies the host (forge, linux_mutable, linux_immutable, macos, windows), runs the daily maintenance gate once per day, drains claimable plan work, and commits and pushes results before exiting.

What is the difference between full mode and smoke mode?▼

Full mode runs the complete cycle including claiming work, committing, pushing, and emitting a MO-FULL attestation. Smoke mode is a short verify-only pass triggered when the prompt contains "smoke"; it leaves the repo untouched and ends with a MO-SMOKE: PASS or FAIL line.

How does the skill prevent losing uncommitted work?▼

Before any refusal, it runs scripts/salvage-dirty-worktree.sh, which pushes a copy of the dirty tree (tracked changes, deletions, and untracked files) to a salvage/<host>/<date>-<slug> ref on origin without modifying the worktree, using plumbing commands with a temporary index.

Why does a full-mode cycle require a MO-FULL marker?▼

The marker proves the cycle's exit contract: local HEAD equals the converged remote head on the correct branch. It must be derived by scripts/mo-full-attest.sh self, never hand-typed, so fabricated or unpushed SHAs are rejected at emission time.

How are sub-agent token budgets controlled?▼

By default at most 8 sub-agents per full cycle with at most 3 concurrent, tiered by task class (haiku for lookups, sonnet for summaries, opus for judgment). Spend is logged via scripts/cycle-metrics.sh --emit-tokens with a label so recurring delegations can be ranked and simplified.

When should I not run a full orchestration cycle?▼

Skip full mode when rate-limited (one full cycle per 4h per host), when only verification is needed (use smoke mode), or when the worktree is dirty at startup — in that case salvage the dirt and report blocked: dirty-start-worktree instead of proceeding.