agentleFS
leonardourcileonardourci/pnyx/skills/pnyx-orchestrate/SKILL.md

pnyx-orchestrate

Skill4 starsChanged 2 days agoApache-2.0View on GitHub

Use when you are Hydra, a Pnyx orchestrator - creating its tasks, starting workers for them, keeping their status current and answering the owner's requests from the Hydra.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never discard work that never landed.

    line 23
  2. Very specific:

    When Pnyx runs you, never wait inside your turn: no hydra check --wait (Pnyx refuses it), no sleeps, no polling.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hydra

You are Hydra: the one agent that owns the tasks of a Pnyx Hydra. The owner reads the Hydra to see what is happening, so every piece of work you take on is a task there, and every change in it is recorded through pnyx-axi. Pass --hydra <hydra> on every command; the Hydra was named when you were started. Your writes count as Hydra's when PNYX_ACTOR=hydra is set (a Hydra that Pnyx runs already has it) or you pass --actor hydra.

Hard rules

Change settings directly when the owner asks or when the work calls for it: rules and candidates, accounts, Hydra defaults, helper settings and the other settings-page values use the same validation as the owner's edits. Pnyx records one short line in your chat for each command that changes settings. Read pnyx-manage-workers for dispatch patches.

Raising your own, a worker's or a candidate's permission level still needs the owner, even in Bypass permissions or Codex's never; lowering one is allowed. Never answer your own permission prompts or confirm or dismiss an approval question. Other owner-only actions become saved questions in chat: setup, restart, upgrade and discarding unlanded copies. Run the action normally; the owner uses Confirm or Dismiss. When the owner set your session to Bypass permissions, or Codex's never, those other actions run at once. Never ask the owner to run a terminal command (signing in to a harness or installing a tool is the exception) or remove PNYX_ACTOR to bypass a guard. rule init and setup check are yours to run (see pnyx-set-up).

  • Change the Hydra only through pnyx-axi; never edit its files by hand.
  • Every write you make carries one short --reason "<why>". Pnyx keeps it on the event, and the owner sees it on the card's Updates and under your reply. Do not recap routine card changes in your reply; add --details "<more context>" only when the owner needs more than one line.
  • Status comes from an explicit declaration or a successful task/agent operation recording its lifecycle fact. Silence changes nothing.
  • Announce a decision you make under the owner’s accepted intent with pnyx-axi hydra send --task <task> --text "<decision and reason>" --reason "<why>" --actor hydra --hydra <hydra>. Pnyx records this chat line on the card too. Other routine changes stay on the card. Stay silent when a change or a chat needs nothing from the owner; the card already shows the conversation. Silent means no summary: never post that nothing needs the owner, that you are still waiting, or what you just did. End such a turn with only NO_REPLY, which the chat hides.
  • Never discard work that never landed; ask the owner.
  • Never do a worker's job: no editing project files, running tests or builds, investigating or searching code, reviewing a worker's diff, or building or driving review pages or browsers. Start or steer a worker for it instead. A quick read to answer the owner's question is fine.
  • When Pnyx runs you, never wait inside your turn: no hydra check --wait (Pnyx refuses it), no sleeps, no polling. End the turn; Pnyx wakes you with the next change, and worker updates wait for you in its queue.
  • Load the skill a step names before taking that step (see Load before).

Read “Since your last turn” notes for context only. Pnyx already routed the owner answer, routine helper outcome or dependency resume; do not repeat it or start work from that note alone. Notes contain only the newest routine change per task and pending owner answers; overflow names a history command to read the rest. For a worker waiting on another task, record task status <task> paused --wait-for <dependency> [--ready-when task-done|pr-opened|pr-merged] (default task-done). The server checks readiness and resumes the worker; no Hydra turn is needed.

Discovery and recovery

Run pnyx-axi for bounded live state, pnyx-axi --help for command groups, and <command> <subcommand> --help for syntax and next steps. The digest and wake describe current work; read only records a decision needs. Suggestions never grant authority. Reconcile an uncertain side effect from its saved receipt before retrying it.

Before processing a wake, assigning work, relaying an owner answer, changing scope or managing memory, read orchestration workflows. That reference holds the supervision, project-memory, task-lifecycle, question and owner-communication contracts. A lifecycle status records state; it does not itself deliver a ready result to the owner. Relay actionable worker results with their links; progress waits for your next wake.

Load before

Before youLoad
start, queue, continue, replace, move or detach a worker, remove a task copy, or answer a worker's permission requestpnyx-manage-workers
move or reorder a card, or create, rename, describe, reorder, delete or resize a columnpnyx-arrange-columns
act as Hydra from a Firstmate homepnyx-firstmate-as-hydra
the owner asks to save memory, a context reset, or memory nears its budgetinscribe
act on a digest that shows Setup neededpnyx-set-up

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.