Pi Flow · OVERLORD — the CONTROL-PLANE agent contract: the seat between the human and the pi fleet that OBSERVES the canonical telemetry stream, DECIDES, and ACTS through piflowctl (run / optimize / fix), making the high-order calls a deterministic controller can't — continue · abort · rerun-with-a-steer · nudge · escalate · land. LOAD THIS when you are SUPERVISING a live run, an optimize pass, or a fix loop and must judge a node's behaviour and decide its fate; when you are "spawning + testing" a fixer/agent and deciding whether to shut it down, re-run, or escalate; or when "act as the control plane", "be the overlord / the governor", "supervise / babysit this run", "should I kill / rerun / escalate this", "insert a control plane", or "k8s-style control of the flow" come up. The overlord has TWO MODES — a programmatic controller and an agent (you) — fed by the SAME stream; this is the AGENT-mode contract. It DELEGATES deterministic termination (timeouts, retries, the run-count ceiling, token/edit budgets) to the shipped workflow-management plane and adds JUDGMENT on top; it intervenes AT SEAMS for live producer runs and may abort mid-run ONLY off the critical path (a candidate / control node). It is an event-WOKEN SENTINEL with NO event loop — a declarative wake-policy over the one stream decides when a fold event is owed human-grade judgment, then it wakes, adjudicates a one-shot digest, acts at a seam, and sleeps. piflow-start is its actuator for running & monitoring; piflow-inspect is its telemetry/instrument source (status · telemetry · trace · logs); piflow-triage + piflow-fixer are the two agents it spawns and supervises over an optimize round (name the defect, then solve it) — this skill is the decider ABOVE all four. THIS IS THE DEFAULT SEAT WHILE ANY RUN, OPTIMIZE PASS, OR ROUND IS LIVE: load it whenever you are monitoring, supervising, or babysitting a pi-flow run or fix loop — not only on an explicit "act as control plane" ask. LOAD THIS ALSO when you are running triage/fix and must decide continue/abort/rerun/escalate/land; when "doing a round" or "monitoring an optimize pass" comes up; or when "supervise / babysit this run", "monitor this optimize round", "should I kill / rerun / escalate this", or "insert a control plane" come up.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryEngineeringStars0
About this skill
Pi Flow · OVERLORD — the CONTROL-PLANE agent contract: the seat between the human and the pi fleet that OBSERVES the canonical telemetry stream, DECIDES, and ACTS through piflowctl (run / optimize / fix), making the high-order calls a deterministic controller can't — continue · abort · rerun-with-a-steer · nudge · escalate · land. LOAD THIS when you are SUPERVISING a live run, an optimize pass, or a fix loop and must judge a node's behaviour and decide its fate; when you are "spawning + testing" a fixer/agent and deciding whether to shut it down, re-run, or escalate; or when "act as the control plane", "be the overlord / the governor", "supervise / babysit this run", "should I kill / rerun / escalate this", "insert a control plane", or "k8s-style control of the flow" come up. The overlord has TWO MODES — a programmatic controller and an agent (you) — fed by the SAME stream; this is the AGENT-mode contract. It DELEGATES deterministic termination (timeouts, retries, the run-count ceiling, token/edit budgets) to the shipped workflow-management plane and adds JUDGMENT on top; it intervenes AT SEAMS for live producer runs and may abort mid-run ONLY off the critical path (a candidate / control node). It is an event-WOKEN SENTINEL with NO event loop — a declarative wake-policy over the one stream decides when a fold event is owed human-grade judgment, then it wakes, adjudicates a one-shot digest, acts at a seam, and sleeps. piflow-start is its actuator for running & monitoring; piflow-inspect is its telemetry/instrument source (status · telemetry · trace · logs); piflow-triage + piflow-fixer are the two agents it spawns and supervises over an optimize round (name the defect, then solve it) — this skill is the decider ABOVE all four. THIS IS THE DEFAULT SEAT WHILE ANY RUN, OPTIMIZE PASS, OR ROUND IS LIVE: load it whenever you are monitoring, supervising, or babysitting a pi-flow run or fix loop — not only on an explicit "act as control plane" ask. LOAD THIS ALSO when you are running triage/fix and must decide continue/abort/rerun/escalate/land; when "doing a round" or "monitoring an optimize pass" comes up; or when "supervise / babysit this run", "monitor this optimize round", "should I kill / rerun / escalate this", or "insert a control plane" come up.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Pi Flow · OVERLORD — the CONTROL-PLANE agent contract: the seat between the human and the pi fleet that OBSERVES the canonical telemetry stream, DECIDES, and ACTS through piflowctl (run / optimize / fix), making the high-order calls a deterministic controller can't — continue · abort · rerun-with-a-steer · nudge · escalate · land. LOAD THIS when you are SUPERVISING a live run, an optimize pass, or a fix loop and must judge a node's behaviour and decide its fate; when you are "spawning + testing" a fixer/agent and deciding whether to shut it down, re-run, or escalate; or when "act as the control plane", "be the overlord / the governor", "supervise / babysit this run", "should I kill / rerun / escalate this", "insert a control plane", or "k8s-style control of the flow" come up. The overlord has TWO MODES — a programmatic controller and an agent (you) — fed by the SAME stream; this is the AGENT-mode contract. It DELEGATES deterministic termination (timeouts, retries, the run-count ceiling, token/edit budgets) to the shipped workflow-management plane and adds JUDGMENT on top; it intervenes AT SEAMS for live producer runs and may abort mid-run ONLY off the critical path (a candidate / control node). It is an event-WOKEN SENTINEL with NO event loop — a declarative wake-policy over the one stream decides when a fold event is owed human-grade judgment, then it wakes, adjudicates a one-shot digest, acts at a seam, and sleeps. piflow-start is its actuator for running & monitoring; piflow-inspect is its telemetry/instrument source (status · telemetry · trace · logs); piflow-triage + piflow-fixer are the two agents it spawns and supervises over an optimize round (name the defect, then solve it) — this skill is the decider ABOVE all four. THIS IS THE DEFAULT SEAT WHILE ANY RUN, OPTIMIZE PASS, OR ROUND IS LIVE: load it whenever you are monitoring, supervising, or babysitting a pi-flow run or fix loop — not only on an explicit "act as control plane" ask. LOAD THIS ALSO when you are running triage/fix and must decide continue/abort/rerun/escalate/land; when "doing a round" or "monitoring an optimize pass" comes up; or when "supervise / babysit this run", "monitor this optimize round", "should I kill / rerun / escalate this", or "insert a control plane" come up.
About this listing
Category
Engineering
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI