azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from GURU-BEAST-ROG at 2026-06-07 19:45:04

Browse Source 
Author: Mike Swanson
Machine: GURU-BEAST-ROG
Timestamp: 2026-06-07 19:45:04
This commit is contained in:
Mike Swanson
2026-06-07 19:45:09 -07:00
parent b928fdb8f3
commit d0254b90ee
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.claude/skills/agy/SKILL.md
View File

@@ -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 - 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 **3** with routing guidance instead of failing obscurely. Claude on such a
machine should NOT attempt local Gemini. machine should NOT attempt local Gemini.
- **Current fleet Gemini host: `GURU-5070`** — the only machine with the Gemini - **Fleet Gemini hosts: `GURU-5070`, `GURU-BEAST-ROG`** — machines with the Gemini
CLI installed and Google-OAuth'd right now. When others get it, install 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 `@google/gemini-cli`, run `gemini` once to log in with Google, then set their
`identity.json` `gemini` block (and update this line). `identity.json` `gemini` block (and update this line).

2
.claude/skills/grok/SKILL.md
View File

@@ -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. - 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. **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.