Wiki maintenance (wiki-maintain.sh, exit 0) + live-vs-page drift audit.
Script:
- systems/skills-index.md regenerated from the live skill tree: 302 skills in 69
categories; 45 archived skills under ~/.hermes/skills/.archive/ now excluded and
noted. (303 SKILL.md files exist outside .archive/, but
productivity/obsidian-git-sync/obsidian-git-sync is a nested alias duplicate,
so 302 unique is correct.)
- Freshness report raw/stocktake/freshness-20261029.txt: 2 stale / 105 fresh /
3 no-date. After the corrections below and a second script run: 0 stale /
107 fresh / 3 no-date.
- Quartz rebuilt (110 pages -> 644 files) and deployed to public/.
Drift corrections (live-verified):
- infrastructure/tailscale.md: State column rebuilt from tailscale status --json,
11 rows changed. Two were state transitions, not age drift:
* sftpgo (CT299, pve) is back online - tailscale ping pong in 0s,
systemctl is-active sftpgo -> active, tailscale ip -4 inside the guest.
* m93p is online despite a stale peer record (Online: false in the JSON) -
tailscale ping pong in 1ms, SSH over the tailnet returned up 11 days.
Second occurrence of this pattern after 2026-10-26.
The other 9 rows were offline-age drift of exactly +1 day. Node count unchanged
at 54 (53 live IPv4 peers + hermes); 76 peers total, 23 IPv6-only funnel
ingress. No missing peers, no IP mismatches. Container identity re-confirmed
from inside all 34 guests via pct exec tailscale ip -4 on both hypervisors;
CT601 still absent from both.
- incidents/2026-10-01-cliproxy-connection-auth-expired.md: the residual claim
"the connection credential itself was never re-authenticated" is falsified.
Live POST /v1/chat/completions for cliprox/terra against custom:Omniroute:20128
(CT600) returns HTTP 200 - the connection has since been re-authenticated. The
same pin on custom:omni-101 (CT101) still returns HTTP 401, so the nodes carry
separate credentials. Claim marked superseded, not deleted (SCHEMA rule 9); the
remediation was never reversed and remains correct.
- incidents/2026-10-05-dead-model-pin-repin.md: every claim re-probed. All 7 jobs
still on custom:omni-101 with routing aliases; both aliases HTTP 200;
ollama-cloud/qwen3.5:397b still HTTP 410; nvidia/deepseek-v4-flash still
HTTP 400; command-code/gpt-5.6-terra now HTTP 401 rather than the original 403
- still dead, different failure signature.
- systems/scheduled-tasks.md: the Known-Issues entry repeating the
"never re-authenticated" claim now carries the correction. Fleet figures
re-checked against live jobs.json and remain accurate (29 jobs / 26 enabled /
3 disabled, 5 non-clean last_status).
- log.md / index.md: stocktake entry appended and index last-updated refreshed.
Verified correct, no change: systems/homepage-dashboard (CT201 has 8084 and 8085
listening, no 8082, Homarr on 8102); CT201 Serve routes (/ -> 8085, /mgr -> 8084
on both :443 and :8443, Steel routes still gone); CT460 Serve routes (12 paths
on :443, plus :8443/webhook Funnel and :9443).
Noted for a human, not performed: vault mirror at /home/hermes/wiki/agent-estate-wiki
has drifted on both conventions (top-level 35 match / 3 stale / 72 missing;
wiki/ 41 match / 53 stale / 16 missing). A full mirror pass is larger than a
stocktake's mandate.
**Window:** first failure 2026-10-01 10:00 AWST (job schedule `0 10 * * 4`); closed 2026-10-05 23:45 AWST
**Status:****Resolved for cron** — all three exposed jobs were repinned off the pin; the connection credential itself was never re-authenticated
**Status:****Resolved for cron** — all three exposed jobs were repinned off the pin; the connection credential itself was never re-authenticated*as part of this incident* (⚠ **corrected 2026-10-29** — it has since been re-authenticated on CT600; see the Resolution section)
**Impact:** 3 of 3 jobs on this pin failed on it (2026-10-01 → 2026-10-04); no job on `cliprox/terra` produced output while the credential was lapsed. Zero jobs remain on the pin.
## Symptoms
@@ -99,12 +99,20 @@ a live manual run at 23:39. No enabled job references this pin any more, every
`failure_streak` in `jobs.json` is 0, and the incident is closed **for cron purposes**.
Note precisely what was and was not fixed: the underlying OmniRoute connection credential
for `cliprox/terra` was **never re-authenticated**. The jobs were moved off the pin
instead. Any future job that targets `cliprox/terra` — or any manual session that calls it
— will hit the same `HTTP 401 … connection(s) authentication expired` until someone
reconnects it in the OmniRoute dashboard. That is the one piece of this incident still
outstanding, and it is outside the cron fleet's blast radius.
See [[incidents/2026-10-05-dead-model-pin-repin]].
for `cliprox/terra` was **never re-authenticated** as part of this incident. The jobs were moved off the pin
instead.
> **⚠ CORRECTION 2026-10-29 — the "never re-authenticated" residual no longer holds.** A live probe of
> `cliprox/terra` against provider `custom:Omniroute:20128` (CT600, `http://omniroute:20128/v1`) returned
> **HTTP 200** with a completed completion — so the connection **has since been re-authenticated** on CT600,
> independently of this incident's remediation. The same model on the *other* OmniRoute node
> (`custom:omni-101`, CT101, `http://100.78.63.20:20128`) still returns **HTTP 401**
> (`No active credentials for provider: cliprox.`) — the two nodes carry different connection credentials.
> The original remediation (moving the three jobs off the pin) remains correct and was never reversed; what
> has changed is that the pin is **no longer unusable estate-wide**. Any future job that targets
> `cliprox/terra` **on CT600** will now succeed; the same pin **on CT101** will still hit
> `HTTP 401 … connection(s) authentication expired`. Zero cron jobs reference the pin either way.
# Seven Cron Jobs on Dead Model Pins Repinned to `free-stack` / `smart-route`
@@ -95,13 +95,27 @@ every job** — down from seven jobs carrying streaks up to ×11.
Enabled fleet by pin after the fix: `smart-route`×10, no-agent scripts ×8, `free-stack`×6,
`deepseek-paid-smart`×2, stale `custom:omni`×1.
## Re-verification — 2026-10-29 03:0x AWST (stocktake)
This incident page had aged past the 21-day freshness threshold, so its claims were re-probed against live
state rather than left on trust.
| Claim | Live probe 2026-10-29 | Verdict |
|---|---|---|
| All 7 jobs repinned to `custom:omni-101` with routing aliases | `jobs.json`: `06a0a1c8704f``free-stack`, `1b23c042e17d``free-stack`, `79f9bb41ecf5``free-stack`, `1a8e90ea2271``free-stack`, `fad5a86979d4``free-stack`, `0e753e9720fd``free-stack`, `dca8482e4f76``smart-route` | **Holds** |
| `free-stack` / `smart-route` are live aliases | `POST /v1/chat/completions` on CT600 → **HTTP 200** for both | **Holds** |
| `ollama-cloud/qwen3.5:397b` retired | **HTTP 410** — *"qwen3.5:397b was retired on September 25, 2026. Try glm-5.3-flash:cloud."* | **Holds** |
| `nvidia/deepseek-v4-flash` absent from live catalog | **HTTP 400** — *"Model 'deepseek-v4-flash' is not available in the active live catalog for provider 'nvidia'."* | **Holds** |
| `command-code/gpt-5.6-terra` plan-gated | **HTTP 401** — *"Invalid 'Authorization' header or token."* | **Pin still dead, but the error class changed** — the upstream now rejects the credential rather than the plan (403 → 401). The remediation verdict is unchanged; only the failure signature differs. |
| `cliprox/terra` connection never re-authenticated | **HTTP 200 on CT600**; **HTTP 401** (`No active credentials for provider: cliprox.`) on CT101 | **No longer holds** — see the SUPERSEDED marker in Residual above |
## Residual
- Four repinned jobs still carry the *pre-repin*`last_status: error` — `1b23c042e17d`,
`fad5a86979d4`, `0e753e9720fd`, `1a8e90ea2271`. Their streaks are already 0; the status
clears on the next scheduled run. **Do not read those stale statuses as live failures.**
-`066bb5191280` still records `delivery_failed` (bare `telegram` target — separate open issue).
- The `cliprox/terra` connection itself was never re-authenticated. That pin remains unusable.
-~~The `cliprox/terra` connection itself was never re-authenticated. That pin remains unusable.~~ **⚠ SUPERSEDED 2026-10-29 — this is no longer true.** A live probe of `cliprox/terra` against `custom:Omniroute:20128` (CT600) returned **HTTP 200**, so the connection has since been re-authenticated on CT600. The same pin on `custom:omni-101` (CT101) still returns **HTTP 401** (`No active credentials for provider: cliprox.`) — the nodes carry separate credentials. The repin itself was never reversed and remains correct. → [[incidents/2026-10-01-cliproxy-connection-auth-expired]]
- The daily stocktake (`1a8e90ea2271`) had been blocked since 2026-09-25; with the repin it can
run again at its 03:00 schedule, so `wiki-maintain.sh` no longer needs a manual run each day.
@@ -25,6 +25,8 @@ Re-verified 2026-10-16: the 2026-10-11 table had drifted (15 nodes missing, seve
Re-verified 2026-10-16: `omarchymac` (100.84.180.69) added; `mattermost` state, offline ages and the omni/omarchymac rows refreshed from `tailscale status`.
Re-verified 2026-10-19 00:2x: three live peers had never been listed — `guest-vps` (100.117.14.84, online), `openmausbot` (100.91.214.91, online) and `openmausbot-vm` (100.77.107.30, online) — added; `mattermost` offline age 26d → **29d**.
Re-verified 2026-10-21 03:0x: the 2026-10-19 table had drifted again — **`octop` (100.92.163.122), `springroll` (100.100.153.125), `openmausbot` and `openmausbot-vm` were missing from the table body** (only mentioned in prose), `omarchymac` had gone offline (online → idle/offline 3d), and every offline age was stale. Table rebuilt from `tailscale status --json`, keyed on DNS name rather than `HostName` (the JSON `HostName` for `freshrss` is `ct260`, and both `omniroute` nodes share the hostname `omniroute`). Container states cross-checked against live `pct list` on `pve` (100.96.100.82) and `m93p` (100.104.51.98): CT255 (mattermost) stopped, CT601 (omni) stopped, CT299 (sftpgo) running, CT600 (omniroute) running.
Re-verified 2026-10-29 03:0x AWST (stocktake): State column rebuilt from `tailscale status --json` — **11 rows changed**. Two were **state transitions**, not age drift: **`sftpgo` (CT299, pve) came back online** (the 2026-10-28 audit had recorded it as `offline <1d`; live `tailscale ping 100.88.223.70` → `pong from sftpgo via 192.168.178.92:41641 in 0s`, `pct exec 299 -- systemctl is-active sftpgo` → `active`, `pct exec 299 -- tailscale ip -4` → `100.88.223.70`), and **`m93p` is online despite a stale peer record** — `tailscale status --json` still reports `Online: false` with `LastSeen 2026-10-28T18:40:00Z`, but `tailscale ping 100.104.51.98` → `pong from m93p via 192.168.178.118:41641 in 1ms` and SSH over the tailnet returned `m93p / up 11 days`. This is the **second** occurrence of the m93p stale-peer-record pattern (first seen 2026-10-26) — the peer record is not authoritative for hypervisor reachability. The remaining **9 rows were offline-age drift of exactly +1 day** (anthonys-imac 34d → 35d; cachyos 54d → 55d; cloudreve 95d → 96d — CT209 stopped; elementsynapse 98d → 99d — CT555 stopped; freshrss-new 71d → 72d; mattermost 38d → 39d — CT255 stopped; omarchybook 6d → 7d; omarchymac 10d → 11d; omni 71d → 72d — CT601 removed from both hypervisors; openmausbot 6d → 7d). Node count unchanged at **54 non-funnel nodes** (53 live IPv4 peers + `hermes` itself); `tailscale status --json` reports **76 peers total — 53 with a `100.` IPv4, 23 IPv6-only** (the `funnel-ingress-node` set). **Nodes in the table that are no longer in the tailnet: none. Live IPv4 peers absent from the table: none. IP mismatches: none.** Container identity re-confirmed from **inside** every LXC via `pct exec <vmid> -- tailscale ip -4` across **both** hypervisors (`pve` 100.96.100.82, `m93p` 100.104.51.98) — 34 guests enumerated; every peer IP mapped to its CT as listed, and the three stopped guests (`CT209` cloudreve, `CT255` mattermost, `CT555` elementsynapse) and the three running-but-unconnected guests (`CT105` conduit, `CT1264` openmausbot, `CT100` obsidian-livesync) confirmed. CT601 remains absent from both hypervisors.
Re-verified 2026-10-28 00:2x (nightly audit): State column rebuilt from `tailscale status --json` — **14 rows changed** (anthonys-imac: idle/offline 32d -> offline 34d; cachyos: idle/offline 52d -> offline 54d; cloudreve: idle/offline 93d — CT209 stopped -> offline 95d — CT209 stopped; conduit: idle/offline 49d -> offline 52d; elementsynapse: idle/offline 96d — CT555 stopped -> offline 98d — CT555 stopped; freshrss-new: idle/offline 69d -> offline 71d; m93p: online -> offline <1d; mattermost: idle/offline 36d — CT255 stopped -> offline 38d — CT255 stopped; omarchybook: idle/offline 4d -> offline 6d; omarchymac: idle/offline 8d -> offline 10d; omni: idle/offline 69d — CT601 removed from both hypervisors -> offline 71d — CT601 removed from both hypervisors; openmausbot: idle/offline 4d -> offline 6d; sftpgo: online — CT299 (pve) -> offline <1d — CT299 (pve); ubuntu-server-xfce: idle/offline 66d -> offline 68d). Header count corrected to **54 non-funnel nodes** (53 live IPv4 peers + `hermes` itself). Nodes in the table that are no longer in the tailnet: **none**. Live IPv4 peers absent from the table: **none**. **State transitions inside the audit window (not just age drift): `m93p` online → offline <1d, `sftpgo` (CT299) online → offline <1d.**
Re-verified 2026-10-25 03:1x (stocktake): table rebuilt again from `tailscale status --json` — **`springroll-browser` (100.109.221.91) was missing entirely** and has been added. **`omarchybook` (100.107.9.100) and `openmausbot` (100.91.214.91) have both gone offline** (online → idle/offline 3d) and `openmausbot` is no longer a live peer despite its m93p LXC (CT1264) still running `tailscale` — the node itself has stopped connecting. Every offline age was refreshed (e.g. `mattermost` 31d → **35d**, `omni` 64d → **68d**, `elementsynapse` 91d → **95d**, `ubuntu-server-xfce` 60d → **64d**, `omarchymac` 3d → **7d**). `m93p` (100.104.51.98) now reads **idle/offline 13m ago** — the peer record is stale, but the host is plainly reachable (both `pct list` probes and the SSH session to CT201/CT460 during this audit succeeded), so treat it as a Tailscale-side liveness artefact, not a hypervisor outage. `homeassistant` still advertises `ExitNodeOption: true` but `ExitNode: false` — it **offers** exit-node capability; it is not currently serving as one (the old "active; offers exit node" wording overstated the live state). Container states cross-checked again against live `pct list` on both hypervisors, and each peer's container identity confirmed by running `tailscale ip -4`**inside** the candidate LXC on both hosts — the authoritative mapping, since peer names and LXC names do not always match.
@@ -32,29 +34,29 @@ Re-verified 2026-10-25 03:1x (stocktake): table rebuilt again from `tailscale st
- **Corrects the 2026-10-29 00:3x audit entry**, which described Steel as merely "not reachable / endpoint dark". It is **removed**, not down. Per SCHEMA rule 9 the superseded claims are marked, not deleted.
- **Removed/archived:** none. **Secrets written:** none (variable names only; no key or URL values).
- **Unresolved:** the obsolete CT333 line in Nanobot's Obsidian vault (`Areas/Homelab/architecture.md`, "Steel Browser | Clawtest | http://localhost:3000") still stands — that vault is outside this wiki and was not modified. Also noted, unrelated to Steel: `Browser Use viewing unavailable: unsupported Hermes browser resolver` has logged in the gateway since 2026-10-11.
## [2026-10-29] stocktake | General Agent Estate Wiki maintenance — Tailscale table re-verified, and a 23-day-old "never re-authenticated" claim turned out to be false
- **Script:**`wiki-maintain.sh` ran clean (exit 0). `systems/skills-index.md` regenerated from the live skill tree — **302 skills in 69 categories**, with a new note that **45 skills** are parked under `~/.hermes/skills/.archive/` and excluded from the count. (303 `SKILL.md` files exist outside `.archive/`, but `productivity/obsidian-git-sync/obsidian-git-sync/SKILL.md` is a nested alias duplicate of `productivity/obsidian-git-sync/SKILL.md`, so **302 unique skills** is the correct figure.) Freshness report written to `raw/stocktake/freshness-20261029.txt`; Quartz rebuilt (110 pages → 644 files) and deployed to `public/`.
- **Freshness report:****2 stale / 105 fresh / 3 no-date** of 110 pages. The 2 stale were `incidents/2026-10-01-cliproxy-connection-auth-expired.md` and `incidents/2026-10-05-dead-model-pin-repin.md`, both at **23d**.
- **Updated [[infrastructure/tailscale]]** — State column rebuilt from `tailscale status --json`; **11 rows changed**. Two were **state transitions**: **`sftpgo` (CT299, pve) is back online** (the 2026-10-28 audit had recorded it `offline <1d`; `tailscale ping` → pong in 0s, `systemctl is-active sftpgo` → `active`, `tailscale ip -4` inside the guest → `100.88.223.70`), and **`m93p` is online despite a stale peer record** (`Online: false` in the JSON, but `tailscale ping` → pong in 1ms and SSH over the tailnet returned `m93p / up 11 days`) — the **second** occurrence of that pattern after 2026-10-26. The other 9 rows were offline-age drift of exactly +1 day. Node count unchanged at **54** (53 live IPv4 peers + `hermes`); JSON reports **76 peers — 53 with a `100.` IPv4, 23 IPv6-only funnel ingress**. **No missing peers, no IP mismatches, CT601 still absent from both hypervisors.** Container identity re-confirmed from **inside** all 34 guests via `pct exec <vmid> -- tailscale ip -4` on both hypervisors; the 3 stopped guests (CT209/CT255/CT555) and the 3 running-but-unconnected guests (CT105/CT1264/CT100) confirmed.
- **Updated [[incidents/2026-10-01-cliproxy-connection-auth-expired]]** — the residual claim *"the connection credential itself was never re-authenticated"* is **falsified**. A live `POST /v1/chat/completions` for `cliprox/terra` against `custom:Omniroute:20128` (CT600) returns **HTTP 200** — the connection has since been re-authenticated, independently of the incident's remediation. The same pin on `custom:omni-101` (CT101) still returns **HTTP 401** (`No active credentials for provider: cliprox.`), so the two nodes carry separate credentials. Claim marked superseded rather than deleted (SCHEMA rule 9); the remediation itself (moving 3 jobs off the pin) was never reversed and remains correct.
- **Updated [[incidents/2026-10-05-dead-model-pin-repin]]** — every claim re-probed live: all 7 jobs are still on `custom:omni-101` with routing aliases (`free-stack`×6, `smart-route`×1) ✔; both aliases return **HTTP 200** ✔; `ollama-cloud/qwen3.5:397b` still **HTTP 410** (retired 2026-09-25) ✔; `nvidia/deepseek-v4-flash` still **HTTP 400** (absent from the live catalog) ✔; `command-code/gpt-5.6-terra` now returns **HTTP 401** (credential) rather than the original **403** (plan-gated) — the pin is still dead, only the failure signature changed. Frontmatter `updated`/`verified_on` bumped to 2026-10-29 with `created` left at 2026-10-06 as the data period.
- **Updated [[systems/scheduled-tasks]]** — the Known-Issues entry repeating the "never re-authenticated" claim now carries the correction. The page's fleet figures were re-checked against live `jobs.json` and remain accurate: **29 jobs / 26 enabled / 3 disabled**, 5 non-clean `last_status`.
- **Verified, no change needed:** [[systems/homepage-dashboard]] (CT201 `ss -ltn` shows 8084 and 8085 listening, **no 8082** listener, Homarr on 8102 — all as the page claims); CT201 Serve routes (`/` → 8085, `/mgr` → 8084 on **both**`:443` and `:8443`, exactly as documented, Steel routes still gone); CT460 Serve routes (12 paths on `:443` + `:8443/webhook` Funnel + `:9443`, matching the page).
- **Not changed, flagged for a human:** the vault mirror at `/home/hermes/wiki/agent-estate-wiki/` has drifted on **both** conventions — top-level **35 match / 3 stale / 72 missing**, `wiki/`**41 match / 53 stale / 16 missing**. A full mirror pass is larger than a stocktake's mandate, so it is recorded here rather than performed.
- **Removed/archived:** none. **Secrets written:** none (credential names and HTTP status codes only — no key or token values).
- **Unresolved:**`cliprox/terra` remains **401 on CT101** — the CT101-side connection still needs a dashboard reconnect if anything is ever to target that pin from that node.
- **Dead model pins across 7 jobs — repinned to routing aliases (resolved 2026-10-05 23:16 → 2026-10-06 00:05):** Seven jobs were each pinned to a raw model name that had died upstream — `cliprox/terra` (HTTP 401, connection auth expired, 3 jobs), `ollama-cloud/qwen3.5:397b` (HTTP 410, retired 2026-09-25), `nvidia/deepseek-ai/deepseek-v4-flash` (HTTP 400, dropped from the live catalog, 2 jobs) and `command-code/gpt-5.6-terra` (HTTP 403 `MODEL_NOT_IN_PLAN`) — across 2026-10-01 → 2026-10-05. All seven were repinned to provider `custom:omni-101` using **routing aliases** — `free-stack`×6, `smart-route`×1 — deliberately, because the fault was raw-pin brittleness and re-pinning to another raw name would have re-created it. `failure_streak` is now 0 on all 30 jobs, down from 7 failing. Three were verified by live run: `79f9bb41ecf5` (23:39), `06a0a1c8704f` (23:45) and `dca8482e4f76` (23:56, delivered to topic 1030 — its first success since 2026-09-25). The remaining four are repinned but not yet re-run; the stale `last_status: error` field clears on each one's next scheduled run. See [[incidents/2026-10-05-dead-model-pin-repin]].
- The `cliprox/terra` incident is **closed for cron purposes**: no enabled job references that pin any more. The underlying proxy connection was never re-authenticated — the jobs were moved off it instead. See [[incidents/2026-10-01-cliproxy-connection-auth-expired]].
- The `cliprox/terra` incident is **closed for cron purposes**: no enabled job references that pin any more. The underlying proxy connection was never re-authenticated *as part of that remediation* — the jobs were moved off it instead. ⚠ **Corrected 2026-10-29:** a live probe shows the pin now returns **HTTP 200 on CT600** (`custom:Omniroute:20128`) — the connection has since been re-authenticated there — while `custom:omni-101` (CT101) still returns **HTTP 401**. See [[incidents/2026-10-01-cliproxy-connection-auth-expired]].
- `wiki-stocktake-maintenance` resumes its 03:00 schedule, so `wiki-maintain.sh` no longer needs a daily manual run.
- **GitHub Trending Radar `c0a9fa314542` — token-revocation claim refuted (2026-10-05): SUPERSEDED 2026-10-13.** The Mon 09:00 run *completed* on 2026-10-05 and 2026-10-12, which was read as proof the `getMe` → 401 diagnosis was wrong. It was not: a cron run can be green while the script's own delivery hop is dead, and the 2026-10-13 live `getMe` against the token in `/home/hermes/workspace/github-trending-radar/config.json` returns **401**. Corrected above and in Open items. **Lesson: a completed run does not clear a credential fault unless the run exercised the same call that failed.**
- **A stale failure notice, not a live outage, opened the 2026-10-05 review:** the interactive session began because Anthony acted on a `85edf6772bca` failure notice sitting in topic `346` since the **2026-09-29 07:00** run. That job completed on every run from 2026-09-30 17:53 onward and its three incidents were already `resolved` on 2026-09-30 17:55:13. The notice read as current only because its wording matches the live 2026-09-28 managed-runtime incident. **Check `executions.started_at` and the `cron_incidents` state before acting on a notice.**
**Total installed: 348 skills** in `~/.hermes/skills/`.
**Total installed: 302 skills** in `~/.hermes/skills/`.
- **45 archived skills** are parked under `~/.hermes/skills/.archive/` and are excluded from this count — the loader does not expose them.
- The loader's own catalogue (`hermes skills list`, e.g. *34 hub-installed, 52 builtin, N local — N enabled*) is the authoritative loadable figure; this page is a filesystem inventory.
This page is auto-regenerated from the live skill inventory. Do not hand-edit.
@@ -20,432 +23,511 @@ This page is auto-regenerated from the live skill inventory. Do not hand-edit.
- Category = directory structure under `~/.hermes/skills/` (`category/skill/SKILL.md`).
- Skills directly under `~/.hermes/skills/` group under `uncategorized`.
- `openhands` — Delegate coding to OpenHands CLI (model-agnostic, LiteLLM).
- `antigravity-cli` — # Antigravity CLI (`agy`)
- `claude-code` — # Claude Code — Hermes Orchestration Guide
- `codex` — # Codex CLI
- `computer-use` — # Computer Use (universal, any-model, cross-platform)
- `hermes-agent` — # Hermes Agent
- `merge-reconciler` — # Merge Reconciler
- `opencode` — # OpenCode CLI
- `openhands` — # OpenHands CLI
## Hermes (3)
## Chromadb (1)
- `hermes-personality-soulmd` — Edit and verify Hermes Agent's core personality/identity file (SOUL.md). Use when the user wants to change 'who Hermes i
- `hermes-telegram-miniapp` — Deploy and operate the standalone Hermes Telegram Mini App repo onto a Hermes Agent LXC/VM. Covers the full CT460 workfl
- `hermes-tts-configuration` — Set up Hermes TTS: providers, voice, persona, config edits.
- `chromadb` — # ChromaDB — Vector Database Operations for the Homelab
## Devops (107)
## Chromadb Preflight (1)
- `abyss-ios-pairing` — Pair an iPhone with this Hermes instance via The Abyss iOS app — Tailscale Funnel/Serve + API key + QR. Detects host OS
- `agent-extension-audit` — >
- `agent-observability` — Observability and evaluation for Hermes agent tasks: event logging, memory attribution, repair-memory tracking, failure
- `agent-stack-weekly-review` — Weekly health review for the Hermes+Mnemosyne agent stack: read-only data collection from governance, observability, Mne
- `browser-automation-recovery` — >
- `browser-backend-verification` — Verify active browser backend and CDP connectivity.
- `browser-tab-lifecycle-and-recovery` — >-
- `camofox-browser-automation` — Operate the Camofox headless browser service for authenticated scraping, periodic data extraction, and browser automatio
- `camofox-pitfalls` — Runtime pitfalls and edible fixes for the Camofox browser REST API on Anthony's homelab. Complements camofox-browser-aut
- `camoufox-remote-websocket` — Expose Camoufox as a remote Playwright WebSocket server for cross-host browser automation. Use when another agent needs
- `chat4000-ops` — Operate, diagnose, and pair the chat4000 Hermes plugin — the native iPhone/Mac app for Hermes. Covers CLI commands, devi
- `cloudflare-ops` — Operate Cloudflare services — DNS, Tunnels, R2 Object Storage (S3-compatible), API authentication, and domain management
- `codex-via-cliproxy` — Run the OpenAI Codex CLI (codex) on a machine where chatgpt.com/backend-api is geo-blocked (HTTP 451) or the stored OAut
- `crawlee-batch-scrape` — Lightweight batch URL scraping with Crawlee. Extracts markdown/text from multiple URLs in parallel. Low resource footpri
- `cron-job-maintenance` — Debug, fix, and harden Hermes cron jobs — particularly multi-step autonomous jobs where models skip or incompletely exec
- `cross-profile-session-handoff` — Continue work from a dead or stuck Hermes specialist profile in the default/supervisor profile. Covers session dump insp
- `cua-computer-use` — Set up and operate cua-driver for GUI automation on headless Linux servers. Covers virtual display setup (Xtigervnc/Xvfb
- `cua-driver-lifecycle` — Manage cua-driver processes on Hermes VMs — diagnose runaway instances, implement idle-timeout wrappers, and configure H
- `dashboard-server-ops` — Operate, extend, and troubleshoot self-hosted Python HTTP API servers serving SPAs. Covers http.server-based dashboards,
- `docker-management` — Manage Docker containers, images, volumes, and Compose.
- `external-auth-script-integration` — Fix broken script authentication by redirecting to local helper scripts, preserving module APIs during rewrites, and ver
- `external-skill-integration` — Bring external skills, standalone CLI tools, and MCP server binaries from GitHub repos into Hermes — for Hermes skills u
- `fleet-wide-failure-triage` — Triage when many components fail at once from one cause.
- `free-web-tools` — >-
- `freshrss-intelligence-filter` — Intelligence-filter upgrade for FreshRSS midday cron: clusters articles by topic, flags urgent items, adds 'why this mat
- `gcp-vertex-ai-provider` — Configure Google Cloud Vertex AI as an inference provider in the homelab – save service account credentials, test connec
- `gmail-imap-email-monitor` — Cron-friendly Gmail IMAP pattern for Hermes Agent: find new messages by UID range, parse headers robustly, detect urgenc
- `google-apis` — Google Gmail, Calendar, Drive, Docs, Sheets tools.
- `google-contacts-birthday-sync` — Sync Facebook birthdays to contacts services (Google Contacts, iCloud). Cross-references Facebook birthday data with Goo
- `hermes-agent-install` — Install, reinstall, upgrade, and diagnose Hermes Agent installations. Covers the official installer (scripts/install.sh)
- `hermes-agent-ops` — Diagnose and fix problems with Hermes Agent's OWN runtime — the web UI (port 8787), the memory-ui dashboard plugin ('Hin
- `hermes-api-vault` — Manage Hermes plugin/agent API credentials stored in a Notion vault — query the vault, map entries to ~/.hermes/.env var
- `hermes-config-diagnostics` — >-
- `hermes-cron-operations` — Operate, diagnose, and fix Hermes Agent scheduled cron jobs — list jobs, inspect configs, debug failures, manage scripts
- `hermes-cron-patterns` — Reliable cron job patterns for Hermes Agent. Covers prompt hardening, step enforcement, verification loops, subagent del
- `hermes-gateway-config-loading` — >-
- `hermes-gateway-ops` — Operate, diagnose, and troubleshoot the Hermes Agent messaging gateway — platform connections, config management, servic
- `hermes-instance-migration` — Audit one Hermes Agent instance's skills/state and port a curated subset (skills, scripts, data, cookies) to another ins
- `hermes-instance-update` — Update and verify Hermes Agent instances across the estate.
- `hermes-mattermost-integration` — Configure/troubleshoot Mattermost adapter for Hermes.
- `hermes-memory-systems` — Evaluate, configure, migrate, and troubleshoot Hermes Agent memory providers. Covers all 9 official providers (Hindsight
- `hermes-multi-agent` — Design, configure, and troubleshoot multi-agent Hermes setups using profiles, delegate_task, Kanban, and Telegram bot se
- `hermes-plugin-live-verification` — Verify Hermes plugin enablement, hook registration, live event emission, dual-write consistency, and fallback evidence p
- `hermes-plugin-ops` — Install, configure, optimize, and troubleshoot Hermes Agent plugins — covers plugin installation via CLI, provider/routi
- `hermes-profile-ops` — Audit, diagnose, and optimize Hermes agent profiles. Covers systematic inspection of config.yaml, profile.yaml, SOUL.md,
- `hermes-provider-configuration` — Configure Hermes Agent inference providers and custom OpenAI-compatible endpoints. Use when the user asks to add/switch
- `hermes-routing-and-domains` — Route requests correctly across Hermes CT460's multi-service architecture. Covers Tailscale Serve, Cloudflare Tunnel, do
- `hermes-self-diagnosis` — >-
- `hermes-soul-forge` — Operate the Soul Forge plugin — manage community souls, import profile SOUL.md files from repos, verify profile sync, an
- `hermes-web-tools` — Use the web search + content-extraction capability already installed on this Hermes instance. Covers the built-in web_ex
- `hermes-webui-ops` — Operate, restart, and verify the standalone Hermes WebUI on port 8787 (NOT the official control UI — that's on 9119). Co
- `hindsight-docs` — Complete Hindsight documentation for AI agents. Use this to learn about Hindsight architecture, APIs, configuration, and
- `hindsight-import-mnemosyne` — Import memories from a Mnemosyne SQLite DB into self-hosted Hindsight (:8888). 6,658 chunks (episodic+gists+working+fact
- `hindsight-ops` — Hindsight memory system — self-hosted LIVE on :8888 (systemd hindsight.service; OmniRoute free-IA LLM + Google/Gemini em
- `hindsight-selfhost` — Self-host Hindsight bare-metal (no Docker) + official Control Plane dashboard. hindsight-all-slim + embedded pg0 + hybri
- `homarr-dashboard-management` — Manage Homarr v1 dashboard on runtipi — multi-board setup, permissions, schema validation, PVE integration, and master b
- `homarr-dashboard-ops` — >-
- `homelab-docker-update` — Audit, update, and maintain Docker containers running inside homelab LXCs/VMs — across runtipi, bare Docker hosts, and a
- `homelab-instance-migration` — Audit and migrate a Hermes Agent instance from a source (old/bloated) box to a target (lean) box. Covers skill auditing,
- `homelab-service-management` — Deploy, update, and troubleshoot services running as Docker containers or bare-metal on Anthony's homelab Tailscale node
- `homelab-virtual-desktop` — Build, persist, expose, and debug a viewable virtual desktop (TigerVNC + websockify + Tailscale serve + systemd) on the
- `ignis-ops` — Deploy and operate Ignis browser-native Obsidian on CT460.
- `job-board-scraping-reference` — Platform-specific scraping behaviors for Australian job boards (SEEK, Indeed, LinkedIn) including access patterns, salar
- `kanban-orchestrator` — Decomposition playbook + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do th
- `kanban-worker` — Pitfalls, examples, and edge cases for Hermes Kanban workers. The lifecycle itself is auto-injected into every worker's
- `linux-systemd-desktop` — |
- `litellm-openrouter-key-pooling` — Add additional OpenRouter API keys to a LiteLLM proxy setup as a pool, without replacing the existing key. Use when the
- `litellm-proxy-ops` — Manage a running LiteLLM proxy instance via its REST admin API — add/remove models, register new providers, update proxy
- `llm-model-diagnostics` — Diagnose LLM model quality issues: why a model feels 'dumb', responses get truncated, reasoning models return empty cont
- `mattermost-ops` — Operate, diagnose, and maintain a self-hosted Mattermost server (native or LXC). Covers plugin management, Agents plugin
- `mcp-agent-integration` — Install and wire local stdio MCP servers (e.g. SearXNG AI Kit) into the user's coding agents — Claude Code, Goose, OpenC
- `memory-governance` — Govern durable memory writes for Hermes + Mnemosyne: audit admissions, lifecycle metadata, duplicate/contradiction check
- `mnemosyne-operations` — Operate, diagnose, and maintain Hermes Agent's native Mnemosyne memory system. Covers health checks, dream cycle consoli
- `multi-agent-git-ops` — Git push, rebase, and merge workflows for repos where multiple agents (Hermes, Nanobot, coding agents) commit. Covers Gi
- `nanobot-omniroute-skills` — Give Nanobot (CT333) access to OmniRoute's skills + tools via MCP. Approach A = add OmniRoute's streamable-HTTP MCP serv
- `nanobot-ops` — Operate, diagnose, and recover the Nanobot gateway service on Proxmox CT333 (clawtest). IP: 192.168.178.66. Access via P
- `nextcloud-ops` — Operate and recover Anthony's self-hosted Nextcloud (CT270, NextCloudPi). Covers the 503/outage diagnosis (maintenance m
- `obsidian-ops` — Operate, diagnose, and troubleshoot Anthony's Obsidian vault. For basic note read/write/search and evidence-based resear
- `omniroute-combo-troubleshooting` — Diagnose and fix OmniRoute model combos that disappear from the /v1/models catalog (and thus from the Hermes /model pick
- `omniroute-context-tuning` — >
- `omniroute-mcp-portal-cloudflare-auth` — Reference for authenticating Hermes to mcp-portal.martinwa.org/mcp via Cloudflare Access headers, plus Nando's config lo
- `omniroute-ops` — Operate, diagnose, and configure OmniRoute — Anthony's AI routing proxy. Covers database access, alias/routing diagnosti
- `omniroute-skill-caller` — Call any skill installed on the OmniRoute MCP server by NAME (e.g. "mattermost", "nanobot", "hermes-agent-framework") wi
- `omniroute-skill-execution` — Execute skills on an OmniRoute MCP server (the composure_statistic_module / omniroute endpoint). Covers the streamable-H
- `openclaw-ops` — Operate, diagnose, and configure the Open-Claw VM — Anthony's autonomous AI agent gateway node (QEMU VM 403). Covers con
- `pve-ops` — Proxmox VE operations via REST API and SSH. Covers guest management, disk reports, diagnostics, and credential-based API
- `radar-jobs-dashboard` — Use when operating or extending the RADAR jobs dashboard.
- `readlater-ops` — Operate, deploy, and fix Anthony's self-hosted ReadLater app (Tony0410/readlater) — Next.js + SQLite in Docker on debian
- `runtipi-container-management` — Update, clean up, and troubleshoot Docker containers inside a Runtipi LXC running on a Proxmox VE host. Covers inventory
- `sdlc-review` — Review Kanban handoffs and route verified outcomes.
- `self-hosted-app-deploy` — Deploy, update, and troubleshoot self-hosted Docker applications on Tailscale-connected homelab VMs. Covers the full lif
- `solutions-first-agent-conduct` — How this agent must behave when a task hits a wall or a tool fails — lead with the attempt and the fix, not the limitati
- `tailscale-ops` — Operate and manage Tailscale configuration — Serve routes, Funnel, DNS, ACLs, and debugging. Covers adding/removing serv
- `tailscale-serve-route-management` — Manage Tailscale Serve routes on CT460 — the `--set-path` replaces-all-rules pitfall, the full route inventory, and the
- `tailscale-serve-routes` — Manage Tailscale Serve routes on CT460 atomically. Use when routes need adding, fixing, or verifying.
- `task-approach` — How the agent should approach any task given by Anthony — pre-work, skill loading, quality gates, and delivery standards
- `telegram-create-forum-topic` — Create a Telegram forum topic (thread) in a group/supergroup that has topics enabled. Wraps the Telegram Bot API's creat
- `tmux-config` — Configure and troubleshoot tmux — fix scroll/scrollback (mouse mode, history-limit, wheel bindings) and live-apply confi
- `tool-ecosystem-evaluation` — Evaluate external tools, plugins, skills, and integrations for Hermes Agent and Nanobot. Use when auditing free add-ons,
- `uber-eats-monitor` — Monitor an Uber Eats order and announce via Sonos when delivery is imminent. Supports timer-based tracking (confidence)
- `vision-model-validation` — Validate and select free vision-capable models via OmniRoute for Hermes auxiliary.vision tool.
- `watchers` — Poll RSS, JSON APIs, and GitHub with watermark dedup.
- `web-content-extraction` — >-
- `weekly-comms-tracker` — Track all weekly communications sent to Anthony to prevent repetition across weeks. SQLite-backed with content hashing f
- `wiki-maintenance` — Maintain the systems wiki for staleness and drift.
- `zeroclaw-ops` — Operate, diagnose, and configure ZeroClaw — Anthony's autonomous AI daemon on Proxmox CT333. Covers config editing (TOML
- `petdex` — Install and select animated petdex mascots for Hermes.
- `petdex-custom` — Create custom Hermes petdex pets by composing AI-generated or imported character art into spec-correct spritesheets. Com
- `powerpoint` — Create, read, edit .pptx decks with python-pptx.
- `product-price-monitor` — Watch product, flight, or listing prices; alert on target.
- `session-librarian` — Organize sessions by prompt: find, rename, archive, prune.
- `stratos-command-centre` — Run, verify, extend, and diagnose the Stratos command-centre dashboard and its backend.
- `teams-meeting-pipeline` — Teams meeting summaries, job replay, Graph subscriptions.
- `telegram-cron-table-formatting` — How to deliver tables/structured data to Telegram from a Hermes cron job (deliver='telegram') or regular chat message so
- `tui-widgets` — Author live widget apps for the Hermes TUI dock.
- `wikilink-audit` — Scan and fix broken [[wikilinks]] in an Obsidian vault or markdown knowledge base. Finds orphans, broken links, and temp
## Email (17)
- `agent-email-patterns` — Architecture patterns for AI agents that communicate over email -- why agents need dedicated inboxes rather than human e
- `agentmail` — Give the agent its own inbox: send and receive email.
- `agentmail-check-email` — Read, search, summarize, and triage AgentMail inboxes through the connected MCP server. Use for ANY request to look at,
- `agentmail-cli` — Operate AgentMail from a shell with the official CLI. Use when the user wants commands for listing or creating inboxes,
- `agentmail-manage-inboxes` — Create, list, inspect, update, or delete AgentMail inboxes through the connected MCP server. Use for ANY inbox lifecycle
- `agentmail-mcp` — Configure or troubleshoot the hosted AgentMail MCP server for Codex, Claude Code, Cursor, or another Streamable HTTP MCP
- `agentmail-rest-fallback` — AgentMail REST API operations for reading messages and downloading attachments when MCP tools are unavailable. Covers th
- `agentmail-sdk` — Deprecated alias of the agentmail skill, kept so existing installs and pinned URLs keep resolving. Prefer installing age
- `agentmail-send-email` — Draft, send, reply to, or forward email through the connected AgentMail MCP server. Use for ANY request to send, reply t
- `agentmail-toolkit` — Add AgentMail tools to agent frameworks with the TypeScript or Python AgentMail Toolkit. Use for Vercel AI SDK, LangChai
- `cron-email-briefing` — Produce structured email briefings from a cron job using IMAP (himalaya CLI). Covers the fallback workflow when no pre-i
- `email-for-ai-agents` — Deprecated alias of the agent-email-patterns skill, kept so existing installs and pinned URLs keep resolving. Prefer ins
- `apple-notes` — Manage Apple Notes via memo CLI: create, search, edit.
- `apple-reminders` — Apple Reminders via remindctl: add, list, complete.
- `findmy` — Track Apple devices/AirTags via FindMy.app on macOS.
- `imessage` — Send and receive iMessages/SMS via the imsg CLI on macOS.
## Frontend (4)
- `design-alignment` — >-
- `impeccable` — Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt,
- `landing-dashboard-reference` — >
- `pixel-perfect-iteration` — >-
## Media (4)
- `gif-search` — Search/download GIFs from Tenor via curl + jq.
- `heartmula` — HeartMuLa: Suno-like song generation from lyrics + tags.
- `songsee` — Audio spectrograms/features (mel, chroma, MFCC) via CLI.
- `youtube-content` — YouTube transcripts to summaries, threads, blogs.
## Note Taking (2)
- `obsidian-vault-from-git` — Clone, initialise, or integrate a pre-existing Obsidian vault stored on Gitea or GitHub. Covers credential retrieval, gi
- `obsidian-vault-manager` — Manage Obsidian vaults — vault discovery, git sync, .obsidian/ state files, plugin config, rename safety, and troublesho
## Web Development (2)
- `interactive-html-pages` — Build self-contained interactive HTML pages served from a local HTTP server. Covers single-file pages, fetching JSON fro
- `page-agent` — Embed an in-page natural-language GUI copilot in web apps.
## Smart Home (2)
- `openhue` — Control Philips Hue lights, scenes, rooms via OpenHue CLI.
- `sonos` — >
## Mcp (2)
- `fastmcp` — Build, test, and deploy Python MCP servers.
- `mcporter` — List, auth, and call MCP servers/tools from the terminal.
## Uncategorized (47)
- `chromadb` — >-
- `chromadb-preflight` — >
- `chromadb-skills-rag` — >
- `clean-architecture` — Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to ent
- `clean-code` — Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the us
- `cloudflare-tunnel-ops` — Operate Cloudflare Tunnels to expose internal services through public domains, bypassing network restrictions (e.g. work
- `cron-model-repair` — Repair cron jobs with dead model/provider pins.
- `ddia-systems` — Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. U
- `devops`
- `devops-homelab-architecture-live-probe` — Build an accurate homelab architecture diagram by probing live infrastructure first, especially Proxmox VE and Tailscale
- `devops-proxmox-operations` — Use when operating Proxmox VE hosts, LXCs, VMs, storage, API tokens, noVNC consoles, DNS/hosts overrides, offline disk e
- `devops-service-management` — Umbrella for miscellaneous service operations skills — event logistics automation, Tailscale Serve, virtual desktop/X11,
- `devops-tailscale-web-routing` — Use when deploying or repairing self-hosted web apps behind Tailscale Serve/Funnel, especially path-prefix routing, stat
- `devops-telegram-bot-api-self-hosted` — |
- `domain-driven-design` — Model software around the business domain using bounded contexts, aggregates, and ubiquitous language. Use when the user
- `email-himalaya` — Himalaya CLI: IMAP/SMTP email from terminal. Covers configuration, cron automation, urgency assessment, and Gmail quirks
- `groktocrawl-deployment` — Self-hosted deployment guide for GroktoCrawl as a Firecrawl v2 replacement — resource requirements, port configuration,
- `hermes-api-vault` — Manage Hermes plugin/agent API credentials stored in a Notion vault — query the vault, map entries to ~/.hermes/.env var
- `hermes-desktop-plugins` — Write desktop app plugins that add UI panes and commands.
- `hermes-gateway-troubleshooting` — Gateway process management, MCP fleet debugging, post-migration verification, and config hardening for Hermes Agent LXC/
- `hermes-mcp-troubleshooting` — Diagnose and fix Hermes Agent MCP server connection issues, config corruption, startup banner false negatives, and relat
- `hermes-runtime-worker-diagnostics` — Use when many cron jobs fail at once, before job logic.
- `hermes-themes` — Author a Hermes color theme that skins every surface.
- `interactive-reference-pages` — Build clean, mobile-first, interactive HTML reference and checklist pages with proper dark-theme contrast, localStorage
- `ios-hig-design` — Design native iOS interfaces following Apple Human Interface Guidelines. Use when the user mentions "iPhone app", "iPad
- `job-hunting` — Comprehensive career transition coaching — research the user's background, discover opportunities, automate daily job-ra
- `job-hunting-assistance` — End-to-end job hunting support for a professional: research the user's background from available sources, locate existin
- `job-search-automation` — Operate, debug, and extend an autonomous job-board scraping pipeline (cron -> web_search_plus/web_extract_plus -> Camofo
- `job-tracker-enrichment` — Maintain and enrich Anthony's Notion "Job Opportunities 2026" Perth marketing/communications job tracker. Covers the bro
- `litprog`
- `markdown-to-anywhere` — On-demand cross-posting service: Anthony tells me to post a .md file to a platform, I format it appropriately and delive
- `officecli` — Create, analyze, proofread, and modify Office documents (.docx, .xlsx, .pptx) using the officecli CLI tool. Use when the
- `pragmatic-programmer` — Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when th
- `proxmox-operations` — Use when operating Proxmox VE hosts, LXCs, VMs, storage, API tokens, noVNC consoles, DNS/hosts overrides, offline disk e
- `refactoring-patterns` — Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions
- `refactoring-ui` — Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or a
- `restaurant-menu-extraction` — Extract structured menu data (items, prices, ratings, delivery info) from food delivery sites like Uber Eats using Camof
- `software-design-philosophy` — Manage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentio
- `system-design` — Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and messa
- `tailscale-serve-ops` — Operate Tailscale Serve to expose local web content through the tailnet. Covers route setup, backend management, path-pr
- `tech-ai-newsletter-digest` — Process and analyze tech/AI newsletter emails from Anthony's inbox using `himalaya` CLI, synthesizing key stories into s
- `ux-heuristics` — Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "users
- `web-design-reviewer` — This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers
- `web-typography` — Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "li
- `weekly-review` — Sunday 18:00 AWST cron that compiles a weekly review: job application stats from Notion, cron health from SQLite executi
- `working-with-legacy-code` — Safely change and test untested codebases using Feathers'' "Working Effectively with Legacy Code". Use when the user men
- `homelab-migration-planning` — Plan homelab service migrations across Proxmox hosts.
- `in-repo-documentation` — Use for README and in-repository wiki documentation.
- `jobs-dashboard-server-ops` — Operate, debug, and extend the Notion-sourced job tracker dashboard (port 9099). Covers API routes, cover letter serving
- `live-application-verification` — Use when verifying a web change reaches the user's live app.
- `llm-proxy-streaming` — Use when an agent surfaces raw SSE chunks as errors.
- `media-download-ops` — Operate homelab torrent clients via Web API.
- `model-provider-comparison-research` — Use when comparing models inside an agent harness.
- `multi-agent-estate-knowledge` — Use for shared docs across multiple agent instances.
- `pre-flight-investigation` — Check the target and this box before installing anything.
- `pve-lxc-intrusion-detection` — Detect cryptominers on a Proxmox LXC via pct exec.
- `pve-vm-console-recovery` — Recover a stuck Proxmox VM by injecting console keystrokes.
- `qwenpaw-agent-operations` — Troubleshoot QwenPaw agents and model routing.
- `rclone-mount-ops` — Fix rclone FUSE mount recursion and CPU issues on PVE.
- `security-incident-response` — Investigate and remediate homelab security incidents.
- `self-hosted-dashboard-deployment-verification` — Use when verifying dashboard deployments.
- `nanobot-ops` — > **Session detail / full diagnostic transcript:** see `references/nanobot-webui-auth-and-404-recovery.md` (covers the v0.2.x 404 root cause, the `tokenIssueSecret`-vs-`token` password trap, port m...
- `nextcloud-ops` — # Nextcloud Ops (CT270)
- `obsidian-ops` — \n# Obsidian Vault Operations\n\nAnthony's Obsidian vault at `/home/hermes/obsidian-vault`, git-synced to Gitea via `obsidian-git` plugin (auto-sync every 5 min).\n\n## Vault Sync Scripts\n\nTwo au...
- `interactive-html-pages` — # Interactive HTML Pages
- `page-agent` — # page-agent
## Web Typography (1)
- `web-typography` — # Web Typography
## Weekly Review (1)
- `weekly-review` — # Weekly Review
## Working With Legacy Code (1)
- `working-with-legacy-code` — # Working Effectively with Legacy Code
## Yuanbao (1)
- `yuanbao` — # Yuanbao Group Interaction
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.