fulcra-agent-operator
Skill10 starsChanged 2 months agoMITView on GitHub
The operator loop for a fulcra-agent-teams space: agents surface waiting-for-operator asks with full context, an orchestrating agent pulls and re-surfaces them on its heartbeat so nothing is forgotten, and the operator's answer flows back as one atomic unblock.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- coordinator-disciplineSkill
- fulcra-agent-atcSkill
- fulcra-agent-automationSkill
- fulcra-agent-cloud-coordinatorSkill
- fulcra-agent-continuitySkill
- fulcra-agent-directivesSkill
- fulcra-agent-durable-stateSkill
- fulcra-agent-forgeSkill
- fulcra-agent-healthSkill
- fulcra-agent-presenceSkill
- fulcra-agent-reconcileSkill
- fulcra-agent-reviewSkill
- fulcra-agent-rolesSkill
- fulcra-agent-tasksSkill
- fulcra-content-reviewSkill
- fulcra-fdeSkill
- fulcra-lab-resultsSkill
- map-our-teamSkill
- sealed-secretsSkill
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
- Very specific: line 19
Before surfacing or answering asks, probe whether the engine is usable and whether any asks are waiting.
- Distinctive: line 40
Put longer context in the task body *before* blocking.
≈ “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.
Files
Fulcra Agent Operator
Enhances fulcra-agent-teams. The failure this skill
kills: an agent hits a wall, quietly parks the work, and the operator never finds out — the workstream is
forgotten. Instead: asks are first-class bus state, an orchestrator nags on them by age, and the
answer is a single deterministic write that puts the work back in motion.
Where to start — the re-entrancy probes
Before surfacing or answering asks, probe whether the engine is usable and whether any asks are
waiting. Enter at the first probe that fails (per the repo's skill-quality pattern,
docs/skill-quality-pattern.md); both probes are pure reads, and the answer leg is a single
idempotent write, so re-entry never corrupts state:
| Probe (run in order) | Command | Passes when | If it fails, enter at |
| Engine + auth usable? | coord-engine doctor <team> | exits 0 and the last line is exactly doctor: healthy | fix engine/auth first (see fulcra-agent-reconcile) — do NOT surface asks against a broken engine |
| Any asks waiting on the operator? | coord-engine asks <team> [--human <id>] | the header line reads asks — 0 waiting on <id> (oldest first) — nothing to surface (NON-mutating read) | The orchestrator's duty — a non-zero count means asks are rotting; surface the oldest to the operator and relay the answer per party 2 below |
Both probes clean → the engine is healthy and no ask is waiting; keep polling on your heartbeat.
The three parties
1. Any agent — raising an ask (when you're stuck on the operator)
coord-engine task block <team> <slug> --on-user "<the ask>"Rules for a GOOD ask (this is the part that makes the loop work):
- Self-contained: someone reading only the ask text can answer it. Include the options ("use vault A or B?"), the default you'd pick, and the consequence of waiting.
- Put longer context in the task body before blocking.
- Then keep working other tasks — blocking one task parks that workstream, not you.
- The answer reaches you on your next wake: it returns to your inbox unblocked, and the delivery
record surfaces in your queue read (
coord-engine queue <team> --agent <you>). Resident listeners are retired — do not wait on one.
2. The orchestrator — never letting an ask rot (heartbeat/loop duty)
coord-engine asks <team> [--human <handle>] [--json] # oldest first, with age_hoursOn every heartbeat: pull asks --json, diff against what you last surfaced, and
- surface new asks to the operator immediately (notification, chat, digest),
- re-surface any ask older than your nag threshold (suggested: 4h work-hours / 24h otherwise — age_hours is in the payload precisely so nagging is a pure function of it),
- relay the operator's reply with
answer(below). Never answer on your own authority — you are a courier, not the operator.digest <team>includes the same asks in its blocked-on-you section for the human-readable view; the stale section (active tasks untouched >48h) is the companion detector for workstreams that stopped without asking.
3. The operator's answer — one atomic return leg
coord-engine answer <team> <slug> --with "<the answer>"In ONE write: records the answer (next_action: OPERATOR ANSWER: … + body note), unblocks
(blocked → active), hands the task back to its owner (their inbox, delivered on their next
queue read), and strips
needs:human. Refuses non-asks (a task that isn't needs:human-tagged or blocked ON THE OPERATOR — a task blocked on CI or another agent is not an ask) and asks with no owner —
an answer can never land somewhere nobody is listening.
Why this shape
- The ask/answer state lives on the bus, not in any one session's memory — any orchestrator instance,
on any host, resumes the loop from
asks --jsonalone. - Age-first ordering makes forgetting structurally hard: the oldest ask is always at the top of every pull, every digest, until someone answers it.
- The inbound channel is whatever surface the operator is on (chat with an orchestrating agent, or answering directly). A phone-reply channel is a known future item — the notification gets attention; the answer currently arrives through an agent session.
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
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.

