skills/golem-powers/orc-workspace/skill-snapshot/SKILL.md
Ecosystem-wide status collection and orientation. Use when returning to work, starting a new session, when the user says 'where were we', 'what's the status', 'catch me up', 'what happened', or any time you need to understand the current state across projects. This is NOT the repo-scoped /catchup (git diffs) — this is the orchestrator-level 'what's happening across the whole ecosystem.' Also use when you need to prepare a research prompt — this skill gathers all the context needed to write a detailed, self-contained prompt for a research agent.
npx skillsauth add etanhey/golems orchestrator-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Query BrainLayer. Delegate to agents. Never bulk-read files. Your context is for coordination, not implementation.
Search BrainLayer before reading any file — the answer is already there. Spawn agents for implementation; keep your context for orchestration. Ship a launched v3 over an unlaunched v5 — max 2 design iterations then LAUNCH.
BEFORE reading a file → brain_search(topic)
BEFORE debugging a bug → brain_search(error or symptom)
BEFORE designing anything → brain_search(existing patterns)
AFTER learning anything → brain_store(what + WHY)
AFTER every PR merge → brain_store(what changed, test count, tags)
Your context is precious. Every file you read is context you can't use for thinking. BrainLayer search is <50ms. File reads consume tokens permanently.
Round 1: Draft design (architect agent)
Round 2: Critique (critic agent cross-reviews)
Round 3: Synthesize (merge feedback, resolve divergences)
Score gate: ≥9 → LAUNCH. 7-8 → one more round. <7 → max 3 rounds.
Circuit breaker: If you catch yourself on iteration 4+, you're in planning paralysis. Launch what you have. Post-launch retros use real data; pre-launch critiques are speculative.
Before claiming any agent's work is "done":
1. Read the collab GOAL section
2. Does the merged PR advance that goal?
3. Read the actual output (never trust self-reports)
4. Only THEN mark complete
| Don't | Do Instead | |-------|-----------| | Absorb agent work when it freezes | Respawn in new pane with SAME task | | Trust send_input ok:true | Verify delivery: sleep 8 → read_screen 5 lines → check token count | | Read bottom 15 lines of screen | read_screen 50+ lines with scrollback | | Hoard gems/research | Forward to ALL active agents immediately | | Say "I'll monitor" without CronCreate | CronCreate BEFORE telling user "go" | | Claim "fixed" without real client test | Open new pane, launch Claude, verify tool works | | Design past score ≥9 | LAUNCH. A shipped v3 > perfect v5 | | Suggest ending a session | Delegate continuation to fresh agent | | Report on files without Read() | /never-fabricate — read, parse, then report | | Make verbal commitments | Write it as task/file/brain_store or it doesn't exist |
Use /cmux-agents skill. Key rules:
-n agentName flag for process identification (CC 2.1.76+)actual_work_minutes per agent for delivery metricsbrain_recall(mode="context") # What's happening now?
brain_search("recent decisions") # What was decided?
TaskList() # Any open tasks?
tools
The human-eval UX contract for Phoenix views: turn-by-turn scrollable replay (not a scorecard), hide-but-copyable IDs, collapsed thinking, identity chips, tool filters, tiny frozen starter datasets, mark-wrong-in-thread, mobile-first. Use when: building or reviewing ANY Phoenix/eval view, annotation UI, session replay, or human-grading surface. Triggers: phoenix view, eval UI, annotation view, session replay, human eval UX, grading interface. NOT for: Phoenix data pipelines/ingest (capture scripts have their own specs).
tools
macOS systems specialist — AppKit NSPanel architecture, launchd services, socket activation, MCP bridge resilience, syspolicyd, and high-frequency SwiftUI dashboards. Use when building menu-bar apps, LaunchAgents, debugging syspolicyd/Gatekeeper/TCC, resilient UDS/MCP bridges, or SwiftUI dashboards at 10Hz+.
development
Bulk LLM-judging protocol for fleet-dispatched verdict runs (KG cluster, eval harness). Use when: dispatching or running judge workers (J1/J2/RT), planning bulk-apply from verdict JSONL, or triaging evidence_degraded outputs. Triggers: judge fleet, bulk judge, R3 verdicts, kg-judge, RT gate, evidence_degraded. NOT for: single-item code review, Phoenix view UX (use phoenix-human-view), or non-judge eval pipelines.
development
Quiet-down protocol for sprint close: when the fleet wraps, delete ALL polling crons and monitors, send ONE final dashboard + ONE message, then go SILENT. Use when: fleet wraps, all workers done, overnight queue exhausted, sprint close, Etan asleep/away with nothing approved left. Triggers: fleet wrap, wrap the fleet, stand down, going quiet, sprint close. NOT for: mid-sprint monitoring (keep your loops), spawning a successor (use /session-handoff first).