From d0254b90eeba81cc82dedbc95102af7c8a997ec2 Mon Sep 17 00:00:00 2001 From: Mike Swanson Date: Sun, 7 Jun 2026 19:45:09 -0700 Subject: [PATCH] sync: auto-sync from GURU-BEAST-ROG at 2026-06-07 19:45:04 Author: Mike Swanson Machine: GURU-BEAST-ROG Timestamp: 2026-06-07 19:45:04 --- .claude/skills/agy/SKILL.md | 4 ++-- .claude/skills/grok/SKILL.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.claude/skills/agy/SKILL.md b/.claude/skills/agy/SKILL.md index ae4eccf..95f2e57 100644 --- a/.claude/skills/agy/SKILL.md +++ b/.claude/skills/agy/SKILL.md @@ -92,8 +92,8 @@ not. Availability is gated by `identity.json` (per-machine, gitignored): - If `gemini.installed` is `false` (or the block is absent), `ask-gemini.sh` exits **3** with routing guidance instead of failing obscurely. Claude on such a machine should NOT attempt local Gemini. -- **Current fleet Gemini host: `GURU-5070`** — the only machine with the Gemini - CLI installed and Google-OAuth'd right now. When others get it, install +- **Fleet Gemini hosts: `GURU-5070`, `GURU-BEAST-ROG`** — machines with the Gemini + CLI installed and Google-OAuth'd. When others get it, install `@google/gemini-cli`, run `gemini` once to log in with Google, then set their `identity.json` `gemini` block (and update this line). diff --git a/.claude/skills/grok/SKILL.md b/.claude/skills/grok/SKILL.md index cc042c8..d208577 100644 --- a/.claude/skills/grok/SKILL.md +++ b/.claude/skills/grok/SKILL.md @@ -69,7 +69,7 @@ Grok is **per-machine** — the skill syncs fleet-wide but the binary does not. ``` - If `grok.installed` is `false` (or the block is absent), `ask-grok.sh` exits **3** with routing guidance instead of failing obscurely. Claude on such a machine should NOT attempt local Grok. -- **Current fleet Grok host: `GURU-5070`** — the only machine with Grok installed right now. When others get it, set their `identity.json` `grok` block (and update this line). +- **Fleet Grok hosts: `GURU-5070`, `GURU-BEAST-ROG`** — machines with Grok installed. When others get it, set their `identity.json` `grok` block (and update this line). **Remote routing (NOT yet wired):** a non-host machine cannot run Grok locally. To fulfill a Grok request from elsewhere, route it to the host (`GURU-5070`). Candidate channels: GuruRMM agent command execution (`/rmm` — GURU-5070 is enrolled; the hard part is shipping image/video artifacts back), `grok agent serve` (WebSocket relay), or a coord-API job queue. Until that's built, Grok requests originate on the host machine.