wiki: nightly audit 2026-11-05 window — network-map re-verified by live probe (9377=Camofox not Stratos, 8790/5174 gone, +9120/9222/7777/6767/8085/9900, full Tailscale Serve table, two dead routes 8769/9123); commit pending 11-04 stocktake re-verifications; log + skills-index
This commit is contained in:
+9
-7
@@ -3,8 +3,8 @@ title: QwenPaw
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-08-15
|
||||
updated: 2026-10-11
|
||||
verified_on: 2026-10-11
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: high
|
||||
tags: [qwenpaw, ct465, agent, paseo]
|
||||
sources: [live-probe, config-reference]
|
||||
@@ -24,11 +24,13 @@ Multi-agent gateway platform. Runs on CT465 with its own workspace, agent profil
|
||||
|
||||
## Current State
|
||||
|
||||
- **Status:** Active — `paseo.service` active on CT465, verified 2026-10-11
|
||||
- **Status:** Active — `paseo.service` active on CT465, **re-verified 2026-11-04**
|
||||
- **Default chat model:** OmniRoute Smart Route (`auto/smart`)
|
||||
- **Config format:** JSON (`agent.json` per workspace)
|
||||
- **Daemon:** `paseo.service`
|
||||
- **Also listening on CT465:** PVE exporter (`100.96.150.69:9221`), a Python service on `:9876`, and local SMTP `:25`
|
||||
- **Daemon:** `paseo.service` — **system** unit on CT465 (distinct from the **user** unit `paseo-daemon.service` that runs on CT460; see [[systems/paseo]])
|
||||
- **CT465 listening ports (live 2026-11-04):** `0.0.0.0:6767` (Paseo), `*:13500`, `127.0.0.1:25463`, `127.0.0.1:11434` (Ollama), `127.0.0.1:38585`, `100.110.72.126:42510`, `:22`
|
||||
- ⚠ **Corrected 2026-11-04.** The old claim that "PVE exporter (`100.96.150.69:9221`), a Python service on `:9876`, and local SMTP `:25`" were listening **on CT465** was **wrong on all three counts**. Live `ss -ltn` inside CT465 shows **none** of them. `:9221` and `:9876` listen on the **`pve` hypervisor host itself** (`100.96.100.82`), not in the guest, and `100.96.150.69` is **CT200** (the Docker host), not the PVE exporter. `:25` is the hypervisor's own loopback SMTP, also not in CT465.
|
||||
- **Port 6767 has two live implementations — do not conflate them:** CT465's own `paseo.service` listens on `0.0.0.0:6767` and answers **HTTP 404** on `/` (the daemon is alive; `/` is not a route). The tailnet node `paseo` (`100.72.188.93`) is a **different guest** — CT1261 on `m93p` — also running `paseo.service` on `:6767`, and it answers **HTTP 200** on `/`. CT460's own user-unit daemon is a third instance (also `:6767`, **HTTP 404** on `/`; `/api/health` → 200).
|
||||
- **CT400/CT465 identity:** confirmed CT465 = `qwenpaw`, running
|
||||
|
||||
## Operating Layers
|
||||
@@ -60,8 +62,8 @@ qwenpaw daemon status
|
||||
|
||||
When adding an OpenAI-compatible provider from Proxmox:
|
||||
- Verify target by VMID and hostname before writing config
|
||||
- CT600/`omniroute` is the **live** OmniRoute service at `100.88.81.19:20128` — verified serving 2026-10-11
|
||||
- CT601/`omni` is a separate guest at `100.93.204.4` — **stopped**, do not use
|
||||
- CT600/`omniroute` is the **live** OmniRoute service at `100.88.81.19:20128` — verified serving 2026-10-11, still live 2026-11-04
|
||||
- ⚠ **Corrected 2026-11-04:** CT601/`omni` is **no longer present on either hypervisor** — `pct list` on both `pve` and `m93p` shows **no CT601 at all**, and the `omni` tailnet peer (`100.93.204.4`) has dropped out of the tailnet entirely. The guest was **removed**, not merely stopped. Use CT600.
|
||||
- A third instance `omniroute-1` at `100.78.63.20:20128` is also live; Hermes registers it as provider `omni-101`
|
||||
- Query `/v1/models` using the exact API key stored for QwenPaw, not a management key
|
||||
- See [[systems/omniroute]] for the full live node table
|
||||
|
||||
@@ -3,8 +3,8 @@ title: "Mnemosyne Capture Pipeline Broken (Aug 18)"
|
||||
type: incident
|
||||
status: superseded
|
||||
created: 2026-08-18
|
||||
updated: 2026-10-12
|
||||
verified_on: 2026-10-12
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: high
|
||||
tags: [memory, mnemosyne, hermes, incident, capture]
|
||||
sources: [mnemosyne-db, health-monitor, run_agent.py]
|
||||
@@ -68,6 +68,29 @@ embedding coverage **98.3 % working / 99.6 % episodic**, FTS aligned (`fts_worki
|
||||
The three guard conditions diagnosed below were never individually confirmed as the fix — the path resumed
|
||||
capturing and has captured through every window since.
|
||||
|
||||
### Re-verified 2026-11-04 — capture still healthy, and the counts have moved on
|
||||
|
||||
Live state of `~/.hermes/mnemosyne/data/mnemosyne.db` (the path in the Verification snippet above is still
|
||||
correct; note the DB is under `data/`, not the `~/.hermes/mnemosyne/*.db` glob path):
|
||||
|
||||
| Metric | 2026-10-12 (page) | 2026-11-04 (live) |
|
||||
|---|---|---|
|
||||
| `working_memory` | 786 | **970** |
|
||||
| `episodic_memory` | 1,056 | **1,146** |
|
||||
| `memoria_facts` | — | **446** |
|
||||
| `memory_embeddings` | — | **943** |
|
||||
| Working-memory vector coverage | 98.3 % | **98.6 %** (`vec_working` 956 / `working_memory` 970) |
|
||||
| Episodic vector coverage | 99.6 % | **100 %** (`vec_episodes` 1,146 / `episodic_memory` 1,146) |
|
||||
| `fts_working` | 786 | **970** — aligned with `working_memory` |
|
||||
| `fts_facts` | 876 | **927** (vs `memoria_facts` 446 — FTS indexes a superset) |
|
||||
| Last `working_memory` entry | 2026-10-11 | **2026-11-03 17:12:40** |
|
||||
|
||||
`mnemosyne stats` independently reports **Total 2,562 / Working 970 / Episodic 1,146**, and the `vec0` extension
|
||||
loads cleanly (`sqlite-vec` from the agent venv), confirming vector search is live rather than silently FTS-only.
|
||||
**Working-memory coverage is above the 95 % reindex threshold**, so no `mnemosyne reindex` was triggered by this
|
||||
audit. **Capture has continued to work without incident for a full month** — the original failure has not
|
||||
recurred.
|
||||
|
||||
**Caution for the next alarm:** the health monitor raised a false EXCEPTION on 2026-10-11 00:08 by comparing
|
||||
naive-UTC `created_at` against AWST `now` ("stalled 10.7 h" — real gap 2.7 h). Do not triage that as a repeat
|
||||
of this incident; see [[systems/mnemosyne]].
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Hermes Managed-Runtime Dependency Failure
|
||||
type: incident
|
||||
status: resolved
|
||||
created: 2026-09-30
|
||||
updated: 2026-10-11
|
||||
verified_on: 2026-10-11
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: high
|
||||
tags: [hermes, cron, runtime, python, worker, incident]
|
||||
sources: [live-jobs-json, live-guard-script, live-cron-list]
|
||||
@@ -36,6 +36,7 @@ Hermes migrated to **uv-managed runtimes**. Each runtime gets its own interprete
|
||||
|
||||
```
|
||||
~/.hermes/installs/019d0d114d22b7e6/environments/<hash>/venv # 10 venvs at time of incident
|
||||
# (now **3** — see 2026-11-04 re-verification below)
|
||||
```
|
||||
|
||||
The migration did not carry every dependency into every managed venv. Workers launched against a venv missing `dotenv` and `mnemosyne` died during import — *before* acknowledging ownership of the job. The failure therefore surfaced as a scheduler/dispatch bug while the real cause was:
|
||||
@@ -71,6 +72,33 @@ Wiring: the **Mnemosyne Watchdog** job (`96eb95ce12f2`, `*/15 * * * *`) runs the
|
||||
- Stale `*.dist-info` directories make `uv` skip a package as "already installed" even when the module is not importable.
|
||||
- `write_file` silently no-ops on `.hermes/scripts/` paths (Hermes library bug). Stage the script in `/tmp` and `install` it into place.
|
||||
|
||||
## Re-verification (2026-11-04)
|
||||
|
||||
**The incident remains resolved, but the estate's runtime topology has changed since 2026-09-30 and the page's
|
||||
"10 venvs" figures are now stale.** Live state on CT460:
|
||||
|
||||
| Item | 2026-09-30 (page) | 2026-11-04 (live) |
|
||||
|---|---|---|
|
||||
| Managed venvs under `~/.hermes/installs/*/environments/*/venv` | **10** | **3** — `19da945341ad4794ac2bc8ff9fdd3643`, `d41b16c8b6674454a4a819bd4acced1f`, `f51d6e4902414114974145d8041c79cb` |
|
||||
| Total runtimes the guard checks | 10 | **4** (3 managed venvs + the tools installer python) |
|
||||
| Guard result | 10/10 OK | **`hermes-runtime-deps-guard: 4/4 runtimes OK`** (exit 0) |
|
||||
| Bootstrap-selected runtime | n/a | **`f51d6e4902414114974145d8041c79cb`** — confirmed by running `hermes_bootstrap` under the tools python: `sys.path` → `…/f51d6e4902414114974145d8041c79cb/venv/lib/python3.14/site-packages` |
|
||||
| `fastembed` in the bootstrap-selected venv | repaired | **OK** — guard log: `fastembed OK in f51d6e4902414114974145d8041c79cb` |
|
||||
| Fastembed model cache | n/a | **present** — `~/.hermes/cache/fastembed/models--qdrant--bge-small-en-v1.5-onnx-q` |
|
||||
| Old gateway committed env `795020dbf24343cd9c52df24723dca83` | the one that broke on 2026-10-10 | **no longer exists** — the `environments/` directory now holds only the three venvs above |
|
||||
|
||||
The guard script itself is unchanged and still wired in: `~/.hermes/scripts/hermes-runtime-deps-guard.sh` exists
|
||||
(executable, 6479 bytes) and is invoked by `~/.hermes/scripts/mnemosyne-watchdog.py` at line 62.
|
||||
|
||||
**Two notes for the next time this class recurs.** First, the "10 venvs" figure is not a stable invariant —
|
||||
Hermes prunes and re-creates uv environments, so **count the live venvs rather than trusting a recorded number**;
|
||||
the guard's own `4/4 runtimes OK` line is the authoritative reading. Second, the **gateway's committed env is no
|
||||
longer a separate directory** — the `795020dbf…` env from the 2026-10-10 recurrence has been garbage-collected,
|
||||
and `hermes_bootstrap` now selects `f51d6e49…` (one of the three surviving managed venvs). The 2026-10-10
|
||||
failure mode ("the gateway loads an env the guard does not check") may therefore no longer reproduce in that exact
|
||||
shape, but the underlying trap — *a `sys.path` that points somewhere the guard never inspects* — is unchanged, so
|
||||
the preventive rule below still stands.
|
||||
|
||||
## Verification (2026-09-30)
|
||||
|
||||
| Check | Result |
|
||||
@@ -83,7 +111,7 @@ Wiring: the **Mnemosyne Watchdog** job (`96eb95ce12f2`, `*/15 * * * *`) runs the
|
||||
## Preventive rules
|
||||
|
||||
- Treat "worker exited before ownership acknowledgement" as a **dependency/import** failure first. Read worker stderr before touching provider or model pins.
|
||||
- After any Hermes runtime or Python upgrade, re-run the guard and confirm 10/10 managed venvs import `dotenv` and `mnemosyne`.
|
||||
- After any Hermes runtime or Python upgrade, re-run the guard and confirm **every runtime it reports** imports `dotenv` and `mnemosyne` — read the guard's own `N/N runtimes OK` line rather than a recorded venv count, because the number of managed venvs changes as Hermes prunes and re-creates uv environments (10 on 2026-09-30, 3 on 2026-11-04).
|
||||
- Mass-cron-failure triage order: live interpreter imports → worker stderr → runtime layout → job logic. See [[runbooks/restart-hermes]] and [[systems/scheduled-tasks]].
|
||||
|
||||
## Related
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Backups
|
||||
type: infrastructure
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-22
|
||||
verified_on: 2026-10-22
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: medium
|
||||
tags: [infrastructure, backups]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -59,7 +59,7 @@ How Hermes's own configuration/state gets backed up, and what's missing.
|
||||
`e27da6c34bbb` (**Hermes Config Backup to Gitea**, daily `0 11 * * *`, `hermes-config-backup.sh`) **commits
|
||||
locally every night and fails to push every night — while its cron row still reads `last_status: ok` and its
|
||||
execution row reads `completed`.** Last commit that reached Gitea: **2026-08-07 11:00:47**; the local repo is
|
||||
**76 commits ahead of `origin/main`**. Root cause is a credential: `origin` is
|
||||
**89 commits ahead of `origin/main`** (was 76 on 2026-10-22 — **13 more nights of local-only commits** since). Root cause is a credential: `origin` is
|
||||
`https://gitea.kangaroo-eel.ts.net/Anthony/hermes-config-backup.git` — HTTPS, no userinfo, no credential
|
||||
helper — so the non-interactive push dies on
|
||||
`fatal: could not read Username … No such device or address` → `✗ Push to Gitea FAILED` →
|
||||
@@ -71,6 +71,27 @@ since 2026-08-07.** The 2026-07-22 full zip and the wiki/authoring repos remain
|
||||
Telegram failure notices *have* been firing daily (last: 2026-10-21 11:00:14, `message_id 8449`); the AgentMail
|
||||
notification step failed.
|
||||
|
||||
**Re-verified 2026-11-04 — still dead, and the drift is now 89 commits.** Live `git -C ~/.hermes/config-backup`:
|
||||
`origin` = `https://gitea.kangaroo-eel.ts.net/Anthony/hermes-config-backup.git` (**unchanged** — still HTTPS with
|
||||
no userinfo and no credential helper, so the credential root cause has not been addressed); `rev-list --count
|
||||
origin/main..HEAD` = **89**; `log origin/main -1` = **2026-08-07 11:00:47 +0800 1e1eb208** (`🦝 nightly backup:
|
||||
2026-08-07 11:00:29 AWST`) — i.e. **nothing has reached Gitea in 89 days**. `backup.log` confirms the nightly
|
||||
failure is current, not historical: the last two runs read
|
||||
`[2026-11-02 11:00:32 AWST] ✗ Push to Gitea FAILED` / `--- Backup complete: FAIL ---` and
|
||||
`[2026-11-03 11:00:31 AWST] ✗ Push to Gitea FAILED` / `--- Backup complete: FAIL ---`.
|
||||
**A second, separate push failure is now also present:** the script attempts a `github` remote that **does not
|
||||
exist** — `fatal: 'github' does not appear to be a git repository` → `✗ Push to GitHub FAILED`. So both off-box
|
||||
targets are broken; the GitHub leg is a missing-remote error rather than a credential error, and would need
|
||||
`git remote add github …` with credentials before it can work at all.
|
||||
**The cron row still lies:** `e27da6c34bbb` reads `enabled: true, last_status: ok` in `jobs.json` while every
|
||||
nightly execution has failed the push — the classic green-row/dead-artifact pattern.
|
||||
|
||||
**Full-backup gap unchanged:** the one full `hermes backup` zip on disk is still
|
||||
`/home/hermes/hermes-backup-2026-07-22-180830.zip` (246 MB, 22 Jul) — **now 105 days old**. No new full zip has
|
||||
been taken. `crontab -l -u hermes` is still empty and there are still **0 user systemd timers**, so nothing
|
||||
schedules the full zip; only `e5ed215fc91c` (**Mnemosyne DB Backup**, weekly `0 3 * * 0`) and `e27da6c34bbb`
|
||||
(config backup, daily) exist in the cron fleet, and neither takes a full `hermes backup`.
|
||||
|
||||
## Relevant runbooks
|
||||
- [[runbooks/backup-wiki]]
|
||||
- [[runbooks/update-hermes-safely]]
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Docker Services
|
||||
type: infrastructure
|
||||
status: mixed
|
||||
created: 2026-07-22
|
||||
updated: 2026-11-01
|
||||
verified_on: 2026-11-01
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: high
|
||||
tags: [docker, homelab, infrastructure]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt, live-probe]
|
||||
@@ -20,14 +20,41 @@ Docker runs on **four hosts**, and CT460's socket is not readable by the agent u
|
||||
|
||||
| Host | Access | Containers running |
|
||||
|---|---|---|
|
||||
| CT200 `docker` (`100.96.150.69`) | `pct exec 200 -- docker ps` via PVE | **61** — main Docker host (**verified 2026-10-31**) |
|
||||
| CT200 `docker` (`100.96.150.69`) | `pct exec 200 -- docker ps` via PVE | **62** — main Docker host (**re-verified 2026-11-04**) |
|
||||
| CT201 `runtipi` (`100.96.244.39`) | `pct exec 201 -- docker ps` via PVE | **20** — Runtipi stack: `audiobookshelf`, `calibre-web`, `code-server`, `cyberchef`, `duplicati`, `filebrowser`, `flaresolverr`, `gotify`, `homarr`, `homebox`, `homepage-manager`, `it-tools`, `linkwarden`, `linkwarden-db`, `mealie-1`, `ntfy`, `runtipi`, `runtipi-db`, `syncthing`, `transmission` (**verified 2026-10-31**) |
|
||||
| CT333 `clawtest` (`100.122.189.81`) | `pct exec 333 -- docker ps` via PVE | **8** — `thirsty_payne`, `community-spark`, `readlater-extraction-worker`, `readlater`, `kokoro-tts`, `edge-tts`, `gotify`, `onecli-postgres-1`. The `steel-browser` container and its image were **removed 2026-10-29** |
|
||||
| CT333 `clawtest` (`100.122.189.81`) | `pct exec 333 -- docker ps` via PVE | **8** — `nostalgic_leavitt`, `community-spark`, `readlater-extraction-worker`, `readlater`, `kokoro-tts`, `edge-tts`, `gotify`, `onecli-postgres-1`. The `steel-browser` container and its image were **removed 2026-10-29**; `thirsty_payne` was **replaced 2026-11-02** by `nostalgic_leavitt` (`ghcr.io/github/github-mcp-server`, created 2026-11-02) |
|
||||
| CT1001 `docker-01` (`100.121.12.31`, **on `m93p`**) | `pct exec 1001 -- docker ps` via `m93p` | **1** — `sshwifty`. **Added 2026-10-31** — a fourth Docker host, previously undocumented |
|
||||
| CT460 `hermes` | `sudo docker` — socket is `root:docker srw-rw----`, `hermes` user not in group `docker`; **no passwordless sudo in cron** | `ignis` — **running** (`Up 35 hours`), verified via `pct exec 460 -- docker ps` from the PVE host |
|
||||
| CT460 `hermes` | `pct exec 460 -- docker ps` **as root** from the PVE host — socket is `root:docker srw-rw----`, the `hermes` user is not in group `docker` (its own `docker ps` → `permission denied while trying to connect to the docker API`) | `ignis` — **running** (`Up 4 days`, `ignis-subpath:0.8.9`, `0.0.0.0:8080->8080/tcp`), re-verified 2026-11-04 |
|
||||
|
||||
## CT200 live inventory (re-verified 2026-11-01, 61 containers)
|
||||
`8mblocal`, `apprise-api`, `audiobookshelf`, `chromadb`, `edge-tts`, `emulatorjs`, `excalidraw-backend`, `excalidraw-frontend`, `filebrowser`, `filebrowser1`, `flaresolverr`, `guacamole-guacamole-1`, `guacamole-guacd-1`, `guacamole-postgres-1`, `homarr`, **`ignis-ignis-1`**, `jellyfin`, `khoj-database-1`, `khoj-sandbox-1`, `khoj-search-1`, `khoj-server-1`, `kokoro-tts`, `libre-closet`, `lobe-chat`, `mycompose-db-1`, `mycompose-saas-1`, `nc_app_context_agent`, `nc_app_talk_bot_ai`, `nextstep-app`, `nextstep-db`, `nextstep-scheduler-1`, `onlyoffice-docserver`, `open-webui`, `overtchat-app`, `overtchat-redis`, `overtchat-searxng`, `portainer`, `portkey-gateway-web-1`, `postgres-newsku`, `prowlarr`, `qbittorrent`, `quickdrop`, `react-resume-client-1`, `readlater`, `readlater-extraction-worker`, `redis-cache`, `save-restricted-bot`, `searxng`, `secret-santa-app`, `sshwifty`, `telegram-bot-api`, `tgvideo-bot`, `tt-rss-app-1`, `tt-rss-db-1`, `tt-rss-updater-1`, `tt-rss-web-nginx-1`, `watchtower`, `worldmonitor`, `worldmonitor-redis`, `worldmonitor-redis-rest`, `ytdlp-web-player`.
|
||||
## CT200 live inventory (re-verified 2026-11-04, 62 containers)
|
||||
`8mblocal`, `apprise-api`, `audiobookshelf`, `chromadb`, `edge-tts`, `emulatorjs`, `excalidraw-backend`, `excalidraw-frontend`, `filebrowser`, `filebrowser1`, `flaresolverr`, `guacamole-guacamole-1`, `guacamole-guacd-1`, `guacamole-postgres-1`, `homarr`, **`ignis-ignis-1`**, `jellyfin`, `khoj-database-1`, `khoj-sandbox-1`, `khoj-search-1`, `khoj-server-1`, `kokoro-tts`, `libre-closet`, `lobe-chat`, `mycompose-db-1`, `mycompose-saas-1`, `nc_app_context_agent`, `nc_app_talk_bot_ai`, `nextstep-app`, `nextstep-db`, `nextstep-scheduler-1`, `onlyoffice-docserver`, `open-webui`, `overtchat-app`, `overtchat-redis`, `overtchat-searxng`, `portainer`, `portkey-gateway-web-1`, `postgres-newsku`, `prowlarr`, `qbittorrent`, `quickdrop`, `react-resume-client-1`, `readlater`, `readlater-extraction-worker`, `redis-cache`, `save-restricted-bot`, `searxng`, `secret-santa-app`, `sshwifty`, `telegram-bot-api`, `tgvideo-bot`, `tt-rss-app-1`, `tt-rss-db-1`, `tt-rss-updater-1`, `tt-rss-web-nginx-1`, `watchtower`, `worldmonitor`, **`worldmonitor-seeder-scheduled`**, `worldmonitor-redis`, `worldmonitor-redis-rest`, `ytdlp-web-player`.
|
||||
|
||||
**Re-verified 2026-11-04 — 61 → 62 containers, one addition.** A set-wise diff against live
|
||||
`docker ps --format '{{.Names}}'` on CT200 shows **exactly one container live but absent from the previous list:
|
||||
`worldmonitor-seeder-scheduled`** (image `worldmonitor:latest`, `Up 29 minutes`, **status `unhealthy`**). Every
|
||||
other name in the list above is confirmed live, and **no listed container has disappeared**. Note the seeder's
|
||||
**new** name — the 2026-11-01 correction removed a `worldmonitor-seeder-fast` entry as "not running", and live
|
||||
`docker ps -a --filter name=worldmonitor` now shows four worldmonitor containers: `worldmonitor` (`Up 4 days`,
|
||||
healthy), **`worldmonitor-seeder-scheduled`** (`Up 29 minutes`, **unhealthy**), `worldmonitor-redis` and
|
||||
`worldmonitor-redis-rest` (`Up 4 days`). The `worldmonitor-seeder-fast` container **does not exist at all** —
|
||||
not even stopped (`docker ps -a` lists only the four above), so the old entry was correctly removed and the seeder
|
||||
has since been redeployed under a new name. **Watch item:** `worldmonitor-seeder-scheduled` is reporting
|
||||
**unhealthy** — worth a look if it does not clear.
|
||||
|
||||
**CT333 container set — `thirsty_payne` → `nostalgic_leavitt` (2026-11-04).** Live CT333 `docker ps` returns 8
|
||||
running containers, and the name that had replaced `adoring_jemison` on 2026-11-01 has itself been replaced:
|
||||
`nostalgic_leavitt` (image `ghcr.io/github/github-mcp-server`, **created 2026-11-02T17:01:17Z**, `Up 29 hours`).
|
||||
The count is unchanged at 8 and the other seven names are identical. A ninth container, `qdrant`
|
||||
(`qdrant/qdrant`), exists but is **stopped** (`Exited (143) 4 months ago`) — it is not in the running count and
|
||||
is not listed above. **Docker generates these random names for compose-less containers, so repeated renames are
|
||||
normal — the reliable check is always the live set, never the recorded name.**
|
||||
|
||||
**CT460 `ignis` access path corrected (2026-11-04).** The old row said "no passwordless sudo in cron", which
|
||||
implied the container list could not be read at all. It can: **`pct exec 460 -- docker ps` from the PVE host
|
||||
runs as root and works** (`ignis|ignis-subpath:0.8.9|Up 4 days|0.0.0.0:8080->8080/tcp`). What does *not* work is
|
||||
the `hermes` user's own `docker ps` inside CT460 — `permission denied while trying to connect to the docker API
|
||||
at unix:///var/run/docker.sock` — because the socket is `root:docker srw-rw----` and `hermes` is not in group
|
||||
`docker`. Use the root-via-PVE path.
|
||||
|
||||
**Re-verified 2026-11-01:** the 2026-10-11 inventory listed **49** containers; the live count is now **61**.
|
||||
**Corrected 2026-11-01:** the inventory list had three **misspelled** `overtchat-*` entries (written
|
||||
|
||||
@@ -3,11 +3,11 @@ title: Network Map
|
||||
type: infrastructure
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-14
|
||||
verified_on: 2026-10-14
|
||||
updated: 2026-11-05
|
||||
verified_on: 2026-11-05
|
||||
confidence: high
|
||||
tags: [infrastructure, network]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt, live-probe:ct460-ss+tailscale-serve-status-2026-11-05]
|
||||
---
|
||||
|
||||
# Network Map
|
||||
@@ -22,11 +22,13 @@ Where Hermes and its dependencies run, and how traffic reaches them.
|
||||
- **This container (hermes, ct460):** `192.168.178.129` (DHCP, eth0)
|
||||
|
||||
### Tailscale (`kangaroo-eel.ts.net`)
|
||||
_Peer IPs below re-checked 2026-11-05 against `tailscale status` on ct460; `webserver`, `clawtest`, `hermesagent`, `docker`, `omniroute` all matched the values listed._
|
||||
- **pve:** `100.96.100.82`
|
||||
- **m93p:** `100.104.51.98` — **second, unclustered Proxmox hypervisor (PVE 9.2.0), discovered 2026-10-14.** See [[infrastructure/proxmox]]. Guest IDs collide with `pve`'s, so always qualify a guest with its host.
|
||||
- **hermes (ct460):** `100.118.5.51`
|
||||
- **hermesagent (ct450, the original/legacy Hermes agent dashboard):** `100.98.205.112`
|
||||
- **omniroute (ct600):** resolves via `omniroute.kangaroo-eel.ts.net` → `100.88.81.19`
|
||||
- **omniroute-1 (third OmniRoute node):** `100.78.63.20` (`omniroute-1.kangaroo-eel.ts.net`) — added 2026-11-05.
|
||||
- **nanobot (ct333, "clawtest"):** `100.122.189.81`
|
||||
- **webserver (ct207, runs the Cloudflare Tunnel):** `100.82.40.23`
|
||||
- **debianvm (VM 101):** `100.98.95.65`
|
||||
@@ -42,19 +44,51 @@ Where Hermes and its dependencies run, and how traffic reaches them.
|
||||
| Port | Bind | Process | Purpose |
|
||||
|---|---|---|---|
|
||||
| 22 | `*` | sshd | SSH |
|
||||
| 80 / [::]:80 | `*` | nginx | reverse proxy, default vhost |
|
||||
| 19119 | `*` | nginx → 127.0.0.1:9119 | public Hermes webui path (tunneled) |
|
||||
| 9119 | `0.0.0.0` | hermes (webui) | Hermes Web UI backend |
|
||||
| 8644 / 8642 | `*` | hermes | additional Hermes agent ports |
|
||||
| 5174 | `*` | node | Hermes desktop companion (tunneled as hermes-desktop.martinwa.org) |
|
||||
| 9377 | `*` | node | Stratos — AI Command Centre |
|
||||
| 8787 | `127.0.0.1`* | python | Hermes gateway health endpoint (see [[runbooks/update-hermes-safely]]) |
|
||||
| 9099 / 8790 | `*` | python3 | auxiliary Hermes processes (unverified purpose) |
|
||||
| 5901 / [::]:5901 | `*` | x11vnc | VNC on Xvfb `:99`, see [[systems/headless-server]] |
|
||||
| 6080 / 6081 | `127.0.0.1` | websockify | noVNC web bridges for two VNC displays |
|
||||
| 80 | `*` | nginx | reverse proxy, default vhost |
|
||||
| 443 / 8443 / 9443 | `100.118.5.51` (tailscale) | tailscaled | Tailscale Serve/Funnel listeners — route table below |
|
||||
| 19119 | `*` | nginx → 127.0.0.1:9119 | public Hermes webui path (Cloudflare-tunneled) |
|
||||
| 9119 | `0.0.0.0` | `hermes-webui/server.py` | Hermes Web UI backend (Serve `/`) |
|
||||
| 8644 / 8642 | `*` | hermes (gateway) | additional Hermes agent ports |
|
||||
| 9900 | `0.0.0.0` | hermes (gateway) | gateway aux port (up 2026-11-05) |
|
||||
| 5174 | — | *(no listener)* | desktop companion port listed up to 2026-10-14; **not listening 2026-11-05** |
|
||||
| 5173 | `0.0.0.0` | node (vite) | content-spark-hub dev server (Serve `:9443` `/`) |
|
||||
| 5175 | `127.0.0.1` | `python3 -m http.server` (`hermes-ui/app/dist`) | hermes-ui static build (Serve `/ui`) |
|
||||
| 9377 | `*` | node — `/home/hermes/services/camofox-browser` | **Camofox browser REST** (`{"ok":true,"engine":"camoufox"}`). Corrected 2026-11-05 — this port had been recorded as "Stratos — AI Command Centre". |
|
||||
| 9222 | `0.0.0.0` | node `camoufox-ws-server.mjs` | Camofox Playwright/CDP WebSocket endpoint |
|
||||
| 7777 | `0.0.0.0` | node `@openchamber/web serve` | OpenChamber web |
|
||||
| 6767 | `0.0.0.0` | Paseo Daemon | Paseo daemon HTTP (loopback helper also on 42013) |
|
||||
| 8080 | `*` | Ignis | Ignis browser-native Obsidian, see [[systems/ignis]] (Serve `/ignis`) |
|
||||
| 8085 | `0.0.0.0` | `agentmail-webhook.py` | AgentMail webhook receiver; funnel-exposed (`/webhook`) |
|
||||
| 8787 | `*` | `hermes-webui/server.py` | hermes-webui backend (Serve `/webui`); used as the health-probe target in [[runbooks/update-hermes-safely]] |
|
||||
| 9099 | `0.0.0.0` | `job_dashboard_server.py` | jobs dashboard + static routes (Serve `/jobs`) |
|
||||
| 9120 | `0.0.0.0` | `serve.py` (repo `public/`) | **Agent Estate Wiki site** (Serve `/wiki`) — added 2026-11-05 |
|
||||
| 5901 | `*` | x11vnc | VNC on Xvfb `:99`, see [[systems/headless-server]] |
|
||||
| 6080 / 6081 | `127.0.0.1` | websockify → 5900 / 5901 | noVNC bridges for the Camofox and desktop displays |
|
||||
| 25 | `127.0.0.1` / `[::1]` | postfix | local mail transport |
|
||||
|
||||
\* `curl` target used in [[runbooks/update-hermes-safely]] health check; binding not independently re-verified in this pass.
|
||||
Loopback-only helpers (not routable): `49347` hermes gateway, `42013` Paseo, `42647` + `38187` opencode.
|
||||
|
||||
## Tailscale Serve / Funnel (verified 2026-11-05)
|
||||
|
||||
`tailscale serve status` on ct460 reports 14 proxies: 12 under `https://hermes.kangaroo-eel.ts.net` (tailnet only), one tailnet route on `:9443`, and one Funnel route on `:8443` (public).
|
||||
|
||||
| Route | Target | Note |
|
||||
|---|---|---|
|
||||
| `/` | `127.0.0.1:9119` | Hermes Web UI |
|
||||
| `/ui` | `127.0.0.1:5175` | hermes-ui static build |
|
||||
| `/jobs` | `127.0.0.1:9099` | jobs dashboard |
|
||||
| `/wiki` | `100.118.5.51:9120` | Agent Estate Wiki |
|
||||
| `/webui` | `127.0.0.1:8787` | hermes-webui |
|
||||
| `/ignis` | `127.0.0.1:8080` | Ignis |
|
||||
| `/gitea` | `100.82.100.128:3000` | Gitea (ct207 tailnet IP) |
|
||||
| `/desktop` | `127.0.0.1:6081` | desktop VNC (noVNC) |
|
||||
| `/vnc-camofox` | `127.0.0.1:6080` | Camofox VNC |
|
||||
| `/evening-grid.html` | `127.0.0.1:9099/evening-grid.html` | jobs dashboard page |
|
||||
| `/agent-estate` | `127.0.0.1:8769` | **DEAD — nothing listening on 8769 (2026-11-05)** |
|
||||
| `/synergy-prep` | `127.0.0.1:9123` | **DEAD — nothing listening on 9123 (2026-11-05)** |
|
||||
|
||||
- `:9443` (tailnet only) — `/` → `127.0.0.1:5173`.
|
||||
- Funnel `:8443` (public) — `/webhook` → `127.0.0.1:8085/webhook` (AgentMail webhook receiver).
|
||||
|
||||
## Relevant runbooks
|
||||
- [[runbooks/diagnose-docker]]
|
||||
|
||||
@@ -1996,4 +1996,5 @@ embedded credential was seen during verification and is not reproduced here ([RE
|
||||
CT460 on `100.88.223.70:8080`; `jobs.json`, `executions.db`, `cron_incidents`, `deliveries.db` read live.
|
||||
- **Not done / unchanged:** no page removed or archived; no job added, removed, disabled or re-pinned; no
|
||||
decision reversed. **No secrets, passwords, tokens or keys written or quoted.**
|
||||
- *network-map.md re-verified (live probe 2026-11-05):* corrected the ct460 port table — **9377 is Camofox browser REST** (`/home/hermes/services/camofox-browser`), not Stratos; `8790` and `5174` are no longer listening; added `9120` (wiki serve), `9222` (Camofox CDP/WS), `7777` (OpenChamber), `6767` (Paseo), `8085` (AgentMail webhook), `9900` (gateway). Added the full Tailscale Serve table (12 routes on `:443`, `/` on `:9443` → 5173, Funnel `:8443` `/webhook` → 8085). Two routes are dead: `/agent-estate` → 8769 and `/synergy-prep` → 9123 have no listener.
|
||||
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Retained Research Answers
|
||||
type: query
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-12
|
||||
verified_on: 2026-10-12
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
review_after: 2027-01-12
|
||||
confidence: medium
|
||||
tags: [query, research, vnc, remote-desktop]
|
||||
@@ -18,11 +18,32 @@ Research answers worth keeping: what was asked, the answer, the evidence it rest
|
||||
|
||||
> The 2026-07-22 stub was filled on 2026-10-12 with the first retained answer (asked in the 2026-10-11
|
||||
> interactive session `talaria-ios`, 41 messages).
|
||||
>
|
||||
> **2026-11-04 re-verification:** the answer's *framing* was wrong — it was written for "TigerVNC + Xtigervnc
|
||||
> servers" that the estate does not run. The client-side advice remains valid for the one VNC server that does
|
||||
> exist (x11vnc on CT460). See the correction note under the answer.
|
||||
|
||||
## Fastest VNC client (asked 2026-10-11)
|
||||
|
||||
**Answer for the CT460/CT200 TigerVNC + Xtigervnc servers:** use the **TigerVNC native viewer** with
|
||||
AutoSelect and the defaults — free, and the fastest standard-RFB client. Lowest bandwidth is **KasmVNC**
|
||||
**Answer for the CT460 VNC server:** use the **TigerVNC native viewer** with AutoSelect and the defaults —
|
||||
free, and the fastest standard-RFB client.
|
||||
|
||||
> ⚠ **Corrected 2026-11-04 — the original question was framed against servers the estate does not run.**
|
||||
> This answer was written on 2026-10-12 for "the CT460/CT200 TigerVNC + Xtigervnc servers". **Neither exists.**
|
||||
> Live state, re-verified 2026-11-04:
|
||||
> - **CT460** runs **x11vnc**, not TigerVNC and not Xtigervnc: `x11vnc -display :99 -forever -shared -rfbport 5901
|
||||
> -rfbportv6 5901 -noxdamage -quiet -nopw` (PID 1290295), fronted by **websockify** → noVNC on
|
||||
> `127.0.0.1:6080 → 5900` (a **dead** target — no listener on 5900) and `127.0.0.1:6081 → 5901` (**live**).
|
||||
> The display itself is `Xvfb :99 -screen 0 1600x1200x24 -ac -nolisten tcp`.
|
||||
> - **CT200** runs **no VNC server at all**. Its only X server is `Xvfb :495478600 -screen 0 800x680x24`, started
|
||||
> 2026-10-30 — that is the Camofox browser's own headless Xvfb, and the Camofox VNC plugin tree lives on
|
||||
> **CT460** (`/home/hermes/services/camofox-browser/plugins/vnc/`), not on CT200. No `x11vnc`, no `Xtigervnc`,
|
||||
> no `vncserver`, and nothing listening on 5900/5901/6080/6081.
|
||||
>
|
||||
> **The advice itself still stands**, because x11vnc speaks standard RFB and TigerVNC's viewer is the right
|
||||
> client for it — but it now applies to **one** host, and the page's "the estate's own VNC/Xtigervnc setup" pointer
|
||||
> is wrong. The real setup is documented at [[systems/headless-server]], which already described x11vnc correctly
|
||||
> back on 2026-10-20; this query page was the outlier. Lowest bandwidth is **KasmVNC**
|
||||
(WebP, ~30 % less) but that is a *server* swap, not a client. **RealVNC Connect** is not a faster decoder, it is
|
||||
a forked protocol (RFB 6, audio, no port-forwarding) and needs a RealVNC server. **TurboVNC** remains the
|
||||
reference for lossless 3D/CAD. Genuinely low latency means leaving RFB entirely: **Parsec** or
|
||||
@@ -66,8 +87,14 @@ software (a thin client with no SIMD headroom decodes slowly regardless of viewe
|
||||
|
||||
**Does NOT establish:** exact throughput multipliers on current hardware (the benchmark is 2012); no
|
||||
end-to-end benchmark was run against Anthony's own hosts. If speed becomes a real complaint, measure the
|
||||
existing server before changing clients.
|
||||
existing server before changing clients. **It also does not establish anything about TigerVNC or Xtigervnc
|
||||
*server*-side behaviour on this estate, because the estate runs neither** — x11vnc's own encoder settings
|
||||
(`-compress`, `-quality`, `-encodings`) are the live lever on CT460, not the TigerVNC/TurboVNC encoder options
|
||||
the report discusses. The compression-level and local-cursor levers above map onto x11vnc as
|
||||
`-compress <level>` and the `x11vnc` cursor-shape options, but the specific numbers were tuned for a different
|
||||
server and should be re-measured before being trusted on this one.
|
||||
|
||||
## Related
|
||||
- [[systems/hermes-agent]] — the estate's own VNC/Xtigervnc setup lives under [[systems/headless-server]]
|
||||
- [[systems/headless-server]] — **the estate's actual VNC setup** (x11vnc on `Xvfb :99`, noVNC via websockify) — re-verified 2026-11-04
|
||||
- [[systems/hermes-agent]] — the agent host this answer was researched for
|
||||
- [[log]] — audit entries
|
||||
|
||||
@@ -0,0 +1,136 @@
|
||||
# Wiki freshness audit — 2026-11-04
|
||||
Threshold: >21 days since `updated`
|
||||
|
||||
## STALE (8)
|
||||
|
||||
- [ 24d] agents/qwenpaw.md (updated 2026-10-11)
|
||||
- [ 24d] incidents/2026-09-28-hermes-managed-runtime-deps.md (updated 2026-10-11)
|
||||
- [ 24d] systems/ignis.md (updated 2026-10-11)
|
||||
- [ 24d] systems/paseo.md (updated 2026-10-11)
|
||||
- [ 23d] incidents/2026-08-18-mnemosyne-capture-pipeline.md (updated 2026-10-12)
|
||||
- [ 23d] queries/retained-research-answers.md (updated 2026-10-12)
|
||||
- [ 23d] systems/home-assistant.md (updated 2026-10-12)
|
||||
- [ 23d] systems/nanobot.md (updated 2026-10-12)
|
||||
|
||||
## FRESH (112)
|
||||
|
||||
- [ 15d] CONTRIBUTING.md
|
||||
- [ 9d] agents/hermes-chaos.md
|
||||
- [ 9d] agents/hermes-production.md
|
||||
- [ 15d] agents/index.md
|
||||
- [ 6d] agents/nanobot.md
|
||||
- [ 15d] agents/open-claw.md
|
||||
- [ 15d] agents/zeroclaw.md
|
||||
- [ 6d] comparisons/camoufox-vs-chrome.md
|
||||
- [ 15d] comparisons/hermes-vs-nanobot.md
|
||||
- [ 15d] comparisons/memory-backends.md
|
||||
- [ 15d] comparisons/model-routers.md
|
||||
- [ 6d] comparisons/steel-vs-camoufox.md
|
||||
- [ 15d] concepts/agent-memory.md
|
||||
- [ 6d] concepts/browser-automation.md
|
||||
- [ 15d] concepts/model-routing.md
|
||||
- [ 15d] concepts/persistent-shells.md
|
||||
- [ 15d] concepts/tool-calling.md
|
||||
- [ 4d] current-state.md
|
||||
- [ 6d] decisions/index.md
|
||||
- [ 15d] decisions/keep-openrouter-as-fallback.md
|
||||
- [ 15d] decisions/persistent-shell-enabled.md
|
||||
- [ 6d] decisions/rollback-steel-to-camofox.md
|
||||
- [ 15d] experiments/index.md
|
||||
- [ 11d] incidents/2026-07-29-mnemosyne-relay.md
|
||||
- [ 15d] incidents/2026-08-01-mnemosyne-capture-failure.md
|
||||
- [ 11d] incidents/2026-08-04-omniroute-free-deepseek-silent-stops.md
|
||||
- [ 13d] incidents/2026-08-08-gitea-config-backup-push-dead.md
|
||||
- [ 12d] incidents/2026-08-15-skills-index-drift.md
|
||||
- [ 10d] incidents/2026-08-26-work-outlook-basic-auth-disabled.md
|
||||
- [ 15d] incidents/2026-08-29-gmail-read-state.md
|
||||
- [ 14d] incidents/2026-09-02-sftpgo-outage.md
|
||||
- [ 6d] incidents/2026-10-01-cliproxy-connection-auth-expired.md
|
||||
- [ 9d] incidents/2026-10-03-ct450-hermes-update.md
|
||||
- [ 9d] incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md
|
||||
- [ 6d] incidents/2026-10-05-dead-model-pin-repin.md
|
||||
- [ 11d] incidents/2026-10-09-cron-provider-timeout-storm.md
|
||||
- [ 3d] incidents/2026-10-09-memory-recall-relevance.md
|
||||
- [ 19d] incidents/2026-10-14-omniroute-node-connection-refused-storm.md
|
||||
- [ 8d] incidents/2026-10-16-omniroute-503-resource-pressure.md
|
||||
- [ 16d] incidents/2026-10-18-degenerate-stream-canned-substitute.md
|
||||
- [ 8d] incidents/2026-10-20-gateway-unclean-exit-orphaned-run.md
|
||||
- [ 13d] incidents/2026-10-21-omniroute-pre-dispatch-filter-skip.md
|
||||
- [ 10d] incidents/2026-10-22-conduit-memory-start-timeout.md
|
||||
- [ 9d] incidents/2026-10-22-nous-portal-refresh-token-invalid.md
|
||||
- [ 9d] incidents/2026-10-24-conduit-call-request-refused.md
|
||||
- [ 9d] incidents/2026-10-25-gmail-digest-runaway-and-refire.md
|
||||
- [ 7d] incidents/2026-10-26-planned-restart-orphaned-cron-run.md
|
||||
- [ 5d] incidents/2026-10-27-job-radar-budget-exhausted.md
|
||||
- [ 5d] incidents/2026-10-28-job-radar-stage1-iteration-cap.md
|
||||
- [ 5d] incidents/2026-10-29-conduit-voice-silence.md
|
||||
- [ 4d] incidents/2026-10-30-ct460-host-outage-scheduler-gap.md
|
||||
- [ 5d] incidents/2026-10-30-m93p-nfs-mount-loss-lxc-boot-failure.md
|
||||
- [ 4d] incidents/2026-10-30-mnemosyne-health-monitor-paused.md
|
||||
- [ 3d] incidents/2026-10-31-asana-access-failures.md
|
||||
- [ 3d] incidents/2026-10-31-conduit-voice-local-mode-not-applying.md
|
||||
- [ 3d] incidents/2026-10-31-gateway-reload-force-drain-orphaned-run.md
|
||||
- [ 2d] incidents/2026-11-01-cron-worker-sigterm-orphaned-claims.md
|
||||
- [ 1d] incidents/2026-11-01-weekly-review-lost-to-gateway-handoff-failure.md
|
||||
- [ 0d] incidents/2026-11-02-job-radar-stage1-iteration-cap-recurrence.md
|
||||
- [ 0d] incidents/2026-11-03-job-radar-stream-active-timeout.md
|
||||
- [ 0d] index.md
|
||||
- [ 13d] infrastructure/backups.md
|
||||
- [ 15d] infrastructure/credentials-map.md
|
||||
- [ 3d] infrastructure/docker-services.md
|
||||
- [ 15d] infrastructure/domains-and-tunnels.md
|
||||
- [ 4d] infrastructure/hosts.md
|
||||
- [ 21d] infrastructure/network-map.md
|
||||
- [ 3d] infrastructure/proxmox.md
|
||||
- [ 3d] infrastructure/tailscale.md
|
||||
- [ 10d] reports/communities-wa-social-media-audit-2026.md
|
||||
- [ 3d] reports/uber-eats/2026-07.md
|
||||
- [ 3d] reports/uber-eats/2026-08.md
|
||||
- [ 3d] reports/uber-eats/2026-09.md
|
||||
- [ 3d] reports/uber-eats/2026-10.md
|
||||
- [ 3d] reports/uber-eats/index.md
|
||||
- [ 15d] runbooks/backup-wiki.md
|
||||
- [ 15d] runbooks/diagnose-docker.md
|
||||
- [ 15d] runbooks/gateway-resource-resilience.md
|
||||
- [ 5d] runbooks/job-radar.md
|
||||
- [ 15d] runbooks/multiplexer-setup.md
|
||||
- [ 9d] runbooks/provider-health.md
|
||||
- [ 6d] runbooks/recover-docker-service.md
|
||||
- [ 15d] runbooks/restart-browser.md
|
||||
- [ 15d] runbooks/restart-hermes.md
|
||||
- [ 15d] runbooks/restore-openrouter.md
|
||||
- [ 15d] runbooks/test-openrouter.md
|
||||
- [ 15d] runbooks/troubleshoot-tool-loop.md
|
||||
- [ 9d] runbooks/update-hermes-safely.md
|
||||
- [ 1d] systems/browser-backend.md
|
||||
- [ 15d] systems/cloudflare-tunnel.md
|
||||
- [ 3d] systems/conduit.md
|
||||
- [ 9d] systems/current-profile.md
|
||||
- [ 15d] systems/guanaco.md
|
||||
- [ 15d] systems/headless-server.md
|
||||
- [ 5d] systems/hermes-agent.md
|
||||
- [ 0d] systems/hermes-hq-push.md
|
||||
- [ 15d] systems/hermes-ui.md
|
||||
- [ 5d] systems/homepage-dashboard.md
|
||||
- [ 9d] systems/memory-backend.md
|
||||
- [ 2d] systems/messaging-integrations.md
|
||||
- [ 3d] systems/mnemosyne.md
|
||||
- [ 9d] systems/model-providers.md
|
||||
- [ 15d] systems/nextcloud.md
|
||||
- [ 15d] systems/obsidian.md
|
||||
- [ 3d] systems/omniroute.md
|
||||
- [ 15d] systems/opencode-go.md
|
||||
- [ 15d] systems/openrouter.md
|
||||
- [ 16d] systems/push-notifications.md
|
||||
- [ 0d] systems/scheduled-tasks.md
|
||||
- [ 0d] systems/skills-index.md
|
||||
- [ 15d] systems/terminal-backend.md
|
||||
- [ 15d] systems/tool-search.md
|
||||
|
||||
## NO updated DATE (3)
|
||||
|
||||
- SCHEMA.md
|
||||
- experiments/active/example.md
|
||||
- log.md
|
||||
|
||||
TOTAL: 8 stale, 112 fresh, 3 no-date of 123 pages
|
||||
@@ -0,0 +1,138 @@
|
||||
# Wiki freshness audit — 2026-11-05
|
||||
Threshold: >21 days since `updated`
|
||||
|
||||
## STALE (0)
|
||||
|
||||
|
||||
## FRESH (122)
|
||||
|
||||
- [ 16d] CONTRIBUTING.md
|
||||
- [ 10d] agents/hermes-chaos.md
|
||||
- [ 10d] agents/hermes-production.md
|
||||
- [ 16d] agents/index.md
|
||||
- [ 7d] agents/nanobot.md
|
||||
- [ 16d] agents/open-claw.md
|
||||
- [ 1d] agents/qwenpaw.md
|
||||
- [ 16d] agents/zeroclaw.md
|
||||
- [ 7d] comparisons/camoufox-vs-chrome.md
|
||||
- [ 16d] comparisons/hermes-vs-nanobot.md
|
||||
- [ 16d] comparisons/memory-backends.md
|
||||
- [ 16d] comparisons/model-routers.md
|
||||
- [ 7d] comparisons/steel-vs-camoufox.md
|
||||
- [ 16d] concepts/agent-memory.md
|
||||
- [ 7d] concepts/browser-automation.md
|
||||
- [ 16d] concepts/model-routing.md
|
||||
- [ 16d] concepts/persistent-shells.md
|
||||
- [ 16d] concepts/tool-calling.md
|
||||
- [ 0d] current-state.md
|
||||
- [ 7d] decisions/index.md
|
||||
- [ 16d] decisions/keep-openrouter-as-fallback.md
|
||||
- [ 16d] decisions/persistent-shell-enabled.md
|
||||
- [ 7d] decisions/rollback-steel-to-camofox.md
|
||||
- [ 16d] experiments/index.md
|
||||
- [ 12d] incidents/2026-07-29-mnemosyne-relay.md
|
||||
- [ 16d] incidents/2026-08-01-mnemosyne-capture-failure.md
|
||||
- [ 12d] incidents/2026-08-04-omniroute-free-deepseek-silent-stops.md
|
||||
- [ 14d] incidents/2026-08-08-gitea-config-backup-push-dead.md
|
||||
- [ 13d] incidents/2026-08-15-skills-index-drift.md
|
||||
- [ 1d] incidents/2026-08-18-mnemosyne-capture-pipeline.md
|
||||
- [ 11d] incidents/2026-08-26-work-outlook-basic-auth-disabled.md
|
||||
- [ 16d] incidents/2026-08-29-gmail-read-state.md
|
||||
- [ 15d] incidents/2026-09-02-sftpgo-outage.md
|
||||
- [ 1d] incidents/2026-09-28-hermes-managed-runtime-deps.md
|
||||
- [ 7d] incidents/2026-10-01-cliproxy-connection-auth-expired.md
|
||||
- [ 10d] incidents/2026-10-03-ct450-hermes-update.md
|
||||
- [ 10d] incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md
|
||||
- [ 7d] incidents/2026-10-05-dead-model-pin-repin.md
|
||||
- [ 12d] incidents/2026-10-09-cron-provider-timeout-storm.md
|
||||
- [ 4d] incidents/2026-10-09-memory-recall-relevance.md
|
||||
- [ 20d] incidents/2026-10-14-omniroute-node-connection-refused-storm.md
|
||||
- [ 9d] incidents/2026-10-16-omniroute-503-resource-pressure.md
|
||||
- [ 17d] incidents/2026-10-18-degenerate-stream-canned-substitute.md
|
||||
- [ 9d] incidents/2026-10-20-gateway-unclean-exit-orphaned-run.md
|
||||
- [ 14d] incidents/2026-10-21-omniroute-pre-dispatch-filter-skip.md
|
||||
- [ 11d] incidents/2026-10-22-conduit-memory-start-timeout.md
|
||||
- [ 10d] incidents/2026-10-22-nous-portal-refresh-token-invalid.md
|
||||
- [ 10d] incidents/2026-10-24-conduit-call-request-refused.md
|
||||
- [ 10d] incidents/2026-10-25-gmail-digest-runaway-and-refire.md
|
||||
- [ 8d] incidents/2026-10-26-planned-restart-orphaned-cron-run.md
|
||||
- [ 6d] incidents/2026-10-27-job-radar-budget-exhausted.md
|
||||
- [ 6d] incidents/2026-10-28-job-radar-stage1-iteration-cap.md
|
||||
- [ 6d] incidents/2026-10-29-conduit-voice-silence.md
|
||||
- [ 5d] incidents/2026-10-30-ct460-host-outage-scheduler-gap.md
|
||||
- [ 6d] incidents/2026-10-30-m93p-nfs-mount-loss-lxc-boot-failure.md
|
||||
- [ 5d] incidents/2026-10-30-mnemosyne-health-monitor-paused.md
|
||||
- [ 4d] incidents/2026-10-31-asana-access-failures.md
|
||||
- [ 4d] incidents/2026-10-31-conduit-voice-local-mode-not-applying.md
|
||||
- [ 4d] incidents/2026-10-31-gateway-reload-force-drain-orphaned-run.md
|
||||
- [ 3d] incidents/2026-11-01-cron-worker-sigterm-orphaned-claims.md
|
||||
- [ 2d] incidents/2026-11-01-weekly-review-lost-to-gateway-handoff-failure.md
|
||||
- [ 1d] incidents/2026-11-02-job-radar-stage1-iteration-cap-recurrence.md
|
||||
- [ 1d] incidents/2026-11-03-job-radar-stream-active-timeout.md
|
||||
- [ 0d] incidents/2026-11-04-upstream-stream-failure-0700-cohort.md
|
||||
- [ 0d] incidents/2026-11-04-vzdump-freeze-ct299-sftpgo-outage.md
|
||||
- [ 0d] index.md
|
||||
- [ 1d] infrastructure/backups.md
|
||||
- [ 16d] infrastructure/credentials-map.md
|
||||
- [ 1d] infrastructure/docker-services.md
|
||||
- [ 16d] infrastructure/domains-and-tunnels.md
|
||||
- [ 5d] infrastructure/hosts.md
|
||||
- [ 0d] infrastructure/network-map.md
|
||||
- [ 4d] infrastructure/proxmox.md
|
||||
- [ 0d] infrastructure/tailscale.md
|
||||
- [ 1d] queries/retained-research-answers.md
|
||||
- [ 11d] reports/communities-wa-social-media-audit-2026.md
|
||||
- [ 4d] reports/uber-eats/2026-07.md
|
||||
- [ 4d] reports/uber-eats/2026-08.md
|
||||
- [ 4d] reports/uber-eats/2026-09.md
|
||||
- [ 4d] reports/uber-eats/2026-10.md
|
||||
- [ 4d] reports/uber-eats/index.md
|
||||
- [ 16d] runbooks/backup-wiki.md
|
||||
- [ 16d] runbooks/diagnose-docker.md
|
||||
- [ 16d] runbooks/gateway-resource-resilience.md
|
||||
- [ 0d] runbooks/job-radar.md
|
||||
- [ 16d] runbooks/multiplexer-setup.md
|
||||
- [ 10d] runbooks/provider-health.md
|
||||
- [ 7d] runbooks/recover-docker-service.md
|
||||
- [ 16d] runbooks/restart-browser.md
|
||||
- [ 16d] runbooks/restart-hermes.md
|
||||
- [ 16d] runbooks/restore-openrouter.md
|
||||
- [ 16d] runbooks/test-openrouter.md
|
||||
- [ 16d] runbooks/troubleshoot-tool-loop.md
|
||||
- [ 10d] runbooks/update-hermes-safely.md
|
||||
- [ 2d] systems/browser-backend.md
|
||||
- [ 16d] systems/cloudflare-tunnel.md
|
||||
- [ 4d] systems/conduit.md
|
||||
- [ 10d] systems/current-profile.md
|
||||
- [ 16d] systems/guanaco.md
|
||||
- [ 16d] systems/headless-server.md
|
||||
- [ 6d] systems/hermes-agent.md
|
||||
- [ 1d] systems/hermes-hq-push.md
|
||||
- [ 16d] systems/hermes-ui.md
|
||||
- [ 1d] systems/home-assistant.md
|
||||
- [ 6d] systems/homepage-dashboard.md
|
||||
- [ 1d] systems/ignis.md
|
||||
- [ 10d] systems/memory-backend.md
|
||||
- [ 3d] systems/messaging-integrations.md
|
||||
- [ 4d] systems/mnemosyne.md
|
||||
- [ 10d] systems/model-providers.md
|
||||
- [ 1d] systems/nanobot.md
|
||||
- [ 16d] systems/nextcloud.md
|
||||
- [ 16d] systems/obsidian.md
|
||||
- [ 4d] systems/omniroute.md
|
||||
- [ 16d] systems/opencode-go.md
|
||||
- [ 16d] systems/openrouter.md
|
||||
- [ 1d] systems/paseo.md
|
||||
- [ 17d] systems/push-notifications.md
|
||||
- [ 0d] systems/scheduled-tasks.md
|
||||
- [ 0d] systems/skills-index.md
|
||||
- [ 16d] systems/terminal-backend.md
|
||||
- [ 16d] systems/tool-search.md
|
||||
|
||||
## NO updated DATE (3)
|
||||
|
||||
- SCHEMA.md
|
||||
- experiments/active/example.md
|
||||
- log.md
|
||||
|
||||
TOTAL: 0 stale, 122 fresh, 3 no-date of 125 pages
|
||||
@@ -3,8 +3,8 @@ title: Home Assistant
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-12
|
||||
verified_on: 2026-10-12
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: medium
|
||||
tags: [system, automation]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -16,13 +16,17 @@ sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
Home automation and device control; one of Hermes's messaging/integration platforms.
|
||||
|
||||
## Location
|
||||
- **Verified 2026-10-12 (live HTTP):** Home Assistant OS answers HTTP `200` on `http://100.68.139.5:8123/` over Tailscale, and the Tailscale node `homeassistant` (`100.68.139.5`) is **active** offering an exit node. The service is up and reachable on the tailnet.
|
||||
- **Verified (homelab infra docs, not this host):** VM 100 on `pve`, hostname `haos14.0` (Home Assistant OS), internal IP `172.30.232.1`. `qm list` confirms VMID 100 `homeassistant` is **running** (13 GB RAM).
|
||||
- **Verified 2026-11-04 (live HTTP):** Home Assistant OS answers HTTP `200` on `http://100.68.139.5:8123/` over Tailscale. The service is up and reachable on the tailnet.
|
||||
- **Verified 2026-11-04 (live, `qm list` / `qm config` on the `pve` hypervisor):** VM **100** is named **`homeassistant`**, status **running**, **`memory: 5100`** MiB, **`cores: 2`**, `agent: enabled=1`, `ostype: l26`, `net0: virtio=…:bridge=vmbr0`.
|
||||
- ⚠ **Corrected 2026-11-04.** The old page said **13 GB RAM** and attributed that figure to "homelab infra docs, not this host". The live hypervisor reports **5100 MiB** — the RAM figure was wrong and is now sourced from the hypervisor rather than from docs.
|
||||
- ⚠ **Corrected 2026-11-04 — host attribution.** The page placed VM 100 on "`pve`", which is correct, but **only because `pve` = `100.96.100.82` (PVE-A)**; there is **no VM 100 on `m93p`** (`qm list` on `100.104.51.98` returns no VM 100 at all — it holds `cachyos-m93p` and `openmausbot-vm` only). The page should not be read as implying a second HA guest on PVE-B.
|
||||
- **Still unverified:** the guest's own hostname (`haos14.0` in the docs) and its internal LAN IP (`172.30.232.1`) — neither is observable from the hypervisor or the tailnet, so those two values remain doc-derived.
|
||||
- **Exit-node status corrected 2026-11-04:** the `homeassistant` Tailscale node has `ExitNodeOption: true` (it **offers** exit-node service) but **`ExitNode: false`** (it is **not currently serving** as one). The old wording — "active offering an exit node" — read as though it were actively routing traffic. It is reachable as a tailnet peer only.
|
||||
- **Verified (Hermes config):** `homeassistant` and `hermes-homeassistant` appear in Hermes's platform/display integration lists (`~/.hermes/config.yaml`), alongside `qqbot`, `signal`, `slack`, `teams`, `telegram`.
|
||||
- **Unknown:** the actual connection details (HA base URL, long-lived access token, which entities/automations Hermes can reach) are not present in the sanitized config snapshot — likely held in a plugin-specific credentials file not captured there, or not yet wired up beyond being enabled as a platform.
|
||||
|
||||
## Current configuration
|
||||
**2026-10-12:** HA itself is confirmed up (HTTP 200 on `:8123`, VM running). Still **not** verified: that Hermes can actually reach an entity — no automation, entity list, or voice-assistant config has been confirmed from this host, and no HA credentials were found on CT460.
|
||||
**2026-11-04:** HA itself is confirmed up (HTTP 200 on `:8123`, VM 100 running with 5100 MiB / 2 cores). Still **not** verified: that Hermes can actually reach an entity — no automation, entity list, or voice-assistant config has been confirmed from this host, and no HA credentials were found on CT460.
|
||||
|
||||
## Connected systems
|
||||
- [[systems/hermes-agent]]
|
||||
@@ -34,6 +38,7 @@ Home automation and device control; one of Hermes's messaging/integration platfo
|
||||
- **Partially closed 2026-10-12:** HA itself is confirmed running and reachable (HTTP 200 on `100.68.139.5:8123`). Still open: whether Hermes can actually *use* it — a live call to a known HA entity would settle it, and requires the HA credentials, which are not on CT460.
|
||||
|
||||
## Change history
|
||||
- **2026-11-04:** re-verified live. HTTP `200` on tailnet `:8123` confirmed; VM 100 `homeassistant` confirmed **running** on the `pve` host with **5100 MiB / 2 cores** (the page's **13 GB** was wrong); confirmed **no VM 100 exists on `m93p`**; exit-node claim corrected — the node **offers** exit-node service (`ExitNodeOption: true`) but is **not serving** it (`ExitNode: false`). The guest hostname and internal IP remain doc-derived and unverified. Confidence stays **medium** (service health is high-confidence; Hermes↔HA entity access remains unverified).
|
||||
- 2026-10-12: HA service confirmed UP — HTTP 200 on tailnet `:8123`, Tailscale node `homeassistant` active/exit-node, VMID 100 running per `qm list`. Confidence raised low → medium. Hermes↔HA entity access remains unverified.
|
||||
|
||||
## Relevant runbooks
|
||||
|
||||
+25
-15
@@ -3,8 +3,8 @@ title: Ignis
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-08-19
|
||||
updated: 2026-10-11
|
||||
verified_on: 2026-10-11
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: high
|
||||
tags: [ignis, obsidian, browser-native, wiki, docker]
|
||||
sources: [live-probe, docker-inspect]
|
||||
@@ -17,36 +17,43 @@ Browser-native Obsidian interface for the agent estate wiki. Provides full Obsid
|
||||
|
||||
## Details
|
||||
- **Image:** `ignis-subpath:0.8.9` (custom build with subpath support)
|
||||
- **Container:** `ignis` on CT460 (Hermes LXC)
|
||||
- **Port:** `8080` (bound to `0.0.0.0`) — confirmed `HTTP 200` on `http://127.0.0.1:8080/` 2026-10-11
|
||||
- **Tailscale Serve:** `https://hermes.kangaroo-eel.ts.net/ignis` → `http://127.0.0.1:8080`
|
||||
- **Container:** `ignis` on **CT460** (Hermes LXC) — **re-confirmed 2026-11-04**: live `pct exec 460 -- docker ps` lists `ignis|ignis-subpath:0.8.9|Up 4 days|0.0.0.0:8080->8080/tcp, [::]:8080->8080/tcp`
|
||||
- **Port:** `8080` (bound to `0.0.0.0` **and** `[::]`) — `HTTP 200` on `http://127.0.0.1:8080/` **re-verified 2026-11-04**
|
||||
- **Tailscale Serve:** `https://hermes.kangaroo-eel.ts.net/ignis` → `http://127.0.0.1:8080` — **still present** in live `tailscale serve status` (2026-11-04)
|
||||
- **Privileged:** No (subpath build handles glibc threading without it)
|
||||
- **Restart:** `unless-stopped`
|
||||
- **Server process:** `node /app/apps/ignis-server/server/index.js` running as user `hermes` (PID observed 875) under `containerd-shim-runc-v2`, container `453483b8d99c…`
|
||||
- **Docker socket:** `/var/run/docker.sock` is `root:docker` `srw-rw----` — the `hermes` user is not in group `docker`, so `docker ps`/`docker inspect` on CT460 require `sudo` (no passwordless sudo in this cron context). Verify Ignis via the HTTP endpoint and process list instead.
|
||||
- **Server process:** `node /app/apps/ignis-server/server/index.js` running as user `hermes` (**PID observed 882** on 2026-11-04; was 875 on 2026-10-11) under `containerd-shim-runc-v2`, container **`453483b8d99c…`** — confirmed from `/proc/882/cgroup` → `0::/system.slice/docker-453483b8d99c175dfb4b15b60b9f0affa3dad4b925fd52b3f5ffa2c4a84d0f30.scope`
|
||||
- **Docker socket:** `/var/run/docker.sock` is `root:docker` `srw-rw----` — the `hermes` user is **not** in group `docker`, so `docker ps`/`docker inspect` on CT460 require `sudo`. **Re-verified 2026-11-04**: `pct exec 460 -- su - hermes -c "docker ps"` → `permission denied while trying to connect to the docker API at unix:///var/run/docker.sock`. Probe it as **root via `pct exec 460 -- docker ps`** from the PVE host — that path works and returns the live container list.
|
||||
|
||||
## Volume Mounts
|
||||
| Host Path | Container Path | Purpose |
|
||||
|---|---|---|
|
||||
| `/home/hermes/wiki/agent-estate-wiki` | `/vaults/wiki` | Wiki vault (read/write) |
|
||||
| `ignis-data` (named) | `/app/data` | Ignis app data |
|
||||
| `ignis-obsidian-app` (named) | `/app/obsidian-app` | Obsidian app cache |
|
||||
**Re-derived from live `docker inspect ignis` on CT460, 2026-11-04** (the old table listed three mounts; live shows four):
|
||||
|
||||
| Host Path | Container Path | Type | Purpose |
|
||||
|---|---|---|---|
|
||||
| `/home/hermes/wiki/agent-estate-wiki` | `/vaults/wiki` | **bind** | Wiki vault (read/write) |
|
||||
| `/var/lib/docker/volumes/99cef54bfdc1775669a85764917d3dc4d1be7caeb91a014f258ff9934d8e13e4/_data` | `/vaults` | volume | Anonymous volume backing `VAULT_ROOT=/vaults` |
|
||||
| `/var/lib/docker/volumes/ignis_ignis-data/_data` | `/app/data` | volume | Ignis app data |
|
||||
| `/var/lib/docker/volumes/ignis_ignis-obsidian-app/_data` | `/app/obsidian-app` | volume | Obsidian app cache |
|
||||
|
||||
> The named volumes are `ignis_ignis-data` and `ignis_ignis-obsidian-app` (with the compose-project prefix), not the bare `ignis-data` / `ignis-obsidian-app` the old table used.
|
||||
|
||||
## Environment
|
||||
**Live `docker inspect ignis` env, re-verified 2026-11-04:**
|
||||
- `PUID=1000`, `PGID=1000`
|
||||
- `VAULT_ROOT=/vaults` — Ignis default is `/vaults`, wiki vault mounted at `/vaults/wiki`
|
||||
- `WS_ORIGINS=https://hermes.kangaroo-eel.ts.net` — WebSocket origin for Tailscale access
|
||||
|
||||
## Docker Compose
|
||||
Located at `/home/hermes/docker/ignis/docker-compose.yml` on CT460.
|
||||
Located at `/home/hermes/docker/ignis/docker-compose.yml` on CT460 — **re-confirmed present 2026-11-04** (459 bytes, dated 2026-08-20).
|
||||
|
||||
## ⚠ Second Ignis instance on CT200 (found 2026-10-11)
|
||||
There is a **separate** `ignis-ignis-1` container running on **CT200** (the Docker host), not CT460:
|
||||
- Image `ignis-server:latest`, state running
|
||||
- Image `ignis-server:latest`, state running — **re-verified 2026-11-04**: `ignis-ignis-1|ignis-server:latest|Up 4 days|0.0.0.0:8092->8080/tcp`, `curl http://127.0.0.1:8092/` → **HTTP 200**
|
||||
- Host port **8092** → container 8080
|
||||
- Vault mount `/opt/ignis/vaults` → `/vaults` (different vault path from CT460's `/home/hermes/wiki/agent-estate-wiki`)
|
||||
- Data mount `/opt/ignis/data` → `/app/data`
|
||||
- Obsidian version 1.12.7, Node 22.23.1
|
||||
- Obsidian-app mount `/var/lib/docker/volumes/ignis_ignis-app/_data` → `/app/obsidian-app` (**live 2026-11-04** — the old note listed only two mounts)
|
||||
- Env: `OBSIDIAN_VERSION=1.12.7`, `NODE_VERSION=22.23.1`, `VAULT_ROOT=/vaults`, `PUID=1000`, `PGID=1000`
|
||||
|
||||
**Do not conflate the two.** The canonical wiki-serving Ignis for the agent estate wiki is the CT460 instance exposed at `/ignis`. The CT200 instance is a different deployment on a different vault. Confirm which instance a user means before troubleshooting.
|
||||
|
||||
@@ -69,6 +76,9 @@ There is a **separate** `ignis-ignis-1` container running on **CT200** (the Dock
|
||||
- **No plugins installed:** Vault currently has zero Obsidian plugins — no compatibility concerns
|
||||
- **Quartz coexistence:** Quartz serves a static site from the same vault source; Ignis provides live editing. Both can read from the same files.
|
||||
|
||||
## Change history
|
||||
- **2026-11-04:** re-verified live. CT460's `ignis` container confirmed running (`Up 4 days`, HTTP 200, PID 882, container id `453483b8d99c…` matches the page's existing id); volume-mount table corrected to the four mounts live `docker inspect` reports; named volumes corrected to their compose-prefixed names; CT200's `ignis-ignis-1` re-confirmed with its third (obsidian-app) mount and full env; the Serve route `/ignis` and the compose file confirmed still in place. **No functional drift — the page was accurate, only the mount detail and PID age were stale.**
|
||||
|
||||
## Related
|
||||
- [[systems/obsidian]] — Obsidian vault structure
|
||||
- [[infrastructure/docker-services]] — Docker compose files
|
||||
|
||||
+6
-3
@@ -3,8 +3,8 @@ title: Nanobot
|
||||
type: system
|
||||
status: degraded
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-12
|
||||
verified_on: 2026-10-12
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
confidence: high
|
||||
tags: [system, nanobot, network]
|
||||
sources: [live-probe, omniroute-investigation]
|
||||
@@ -18,7 +18,7 @@ Role in Anthony's setup.
|
||||
## Current state
|
||||
- **Status: DEGRADED (re-verified 2026-10-12).** The Nanobot web UI on CT333 is **UP again**: HTTP `200` on `http://100.122.189.81:8766/` serving the nanobot web UI (verified this audit). However port `8900` — the endpoint the OmniRoute `nanobot` provider connection (`58debd59`, prefix `nanobot`) uses — is still **closed**, so the OmniRoute integration remains disabled. Contrast with 2026-08-07, when connection was refused on 8900 and no service was confirmed listening anywhere.
|
||||
- **Prior state:** `nanobot` process listening on port `8766` (verified via `ss -tlnp` on ct333, 2026-07-22); DOWN 2026-08-07 (connection refused on 8900 — OmniRoute event-loop stalls from model sync + credential health-check retries; provider connection disabled in OmniRoute).
|
||||
- `whatsapp-bridge.service` (systemd, active) — "WhatsApp Bridge for Nanobot" — also runs on ct333. Status not re-verified on 2026-10-12 (SSH to CT333 not reachable from CT460: connection timed out on 22/tcp; verification above is TCP/HTTP probing only).
|
||||
- `whatsapp-bridge.service` — "WhatsApp Bridge for Nanobot" — also runs on ct333. ⚠ **Corrected 2026-11-04: this unit is NOT active — it is in a crash-restart loop.** Live `systemctl status whatsapp-bridge.service` on CT333 shows `Active: activating (auto-restart) (Result: exit-code)` with `NRestarts=75514`. The `ExecStart` is `/bin/bash -c cd /home/nano/nanobot/bridge && BRIDGE_TOKEN=$(cat /home/nano/.nanobot/whatsapp-auth/bridge-token) exec node dist/index.js`, and it exits **`status=200/CHDIR`** — the working directory **`/home/nano/nanobot/bridge` does not exist** on CT333 (nor does `/home/nano/nanobot`; only `/home/nano/.nanobot/whatsapp-auth/bridge-token` is present). The unit is `enabled`, so systemd keeps restarting it every few seconds, burning a restart every ~3 s. **The old "systemd, active" claim was wrong and had been carried unverified since 2026-10-12.** Verified 2026-11-04 from inside the guest via `pct exec 333 -- systemctl status whatsapp-bridge.service` — CT333 is reachable from the PVE host even though it was not directly SSH-reachable from CT460 on 2026-10-12 (CT460 → CT333 port 22 now answers `TCP22_OPEN`).
|
||||
- Publicly reachable via the same Cloudflare Tunnel as Hermes: `nanobot.martinwa.org` → `100.122.189.81:8766`, `nano-ssh.martinwa.org` → SSH on the same host. See [[infrastructure/domains-and-tunnels]].
|
||||
|
||||
## Current state as of 2026-07-22 (superseded — see below)
|
||||
@@ -42,7 +42,10 @@ Role in Anthony's setup.
|
||||
|
||||
## Known issues
|
||||
- Overlap/purpose vs. Hermes not documented anywhere — see [[comparisons/hermes-vs-nanobot]] for the open question this raises.
|
||||
- **`whatsapp-bridge.service` restart loop (open since at least 2026-10-12, confirmed 2026-11-04).** `NRestarts=75514` and climbing; the cause is a missing `/home/nano/nanobot/bridge` working directory. Two ways to clear it, both needing a decision rather than a blind fix: **(a)** recreate the directory and redeploy the bridge build, or **(b)** `systemctl disable --now whatsapp-bridge.service` if the bridge is no longer wanted. Until one is chosen, the unit generates a restart every few seconds indefinitely. The bridge's own auth token (`/home/nano/.nanobot/whatsapp-auth/bridge-token`) is still present, so the deployment is not merely half-removed.
|
||||
- **No monitoring covers either fault.** The OmniRoute `8900` port being closed and the bridge's restart loop both produce **no cron failure and no incident row** — the job reads green while the integration is down. That is the same class as the backup-task stall in [[incidents/2026-11-04-vzdump-freeze-ct299-sftpgo-outage]]: a service that fails *quietly* is invisible to a green-row fleet.
|
||||
## Change history
|
||||
- **2026-11-04: `whatsapp-bridge.service` claim corrected — it is crash-looping, not active.** The unit is in `activating (auto-restart)` with `NRestarts=75514`, failing `status=200/CHDIR` because `/home/nano/nanobot/bridge` does not exist. The page had carried "systemd, active" without verification since 2026-10-12 (that audit could not reach CT333 and said so). Status stays **DEGRADED** for the same reason as before — OmniRoute's port `8900` is still closed (live `ss -ltn` on CT333 shows no `8900` listener) — and now **also** because the WhatsApp bridge is down. The web UI on `:8766` remains up (HTTP 200). **Root cause of the loop is a missing deployment directory, not a service bug** — see [[systems/nanobot]] open items.
|
||||
- 2026-07-22: audit corrected "not running" claim after direct verification on ct333.
|
||||
- 2026-08-07: status changed to DEGRADED — nanobot confirmed DOWN (connection refused on 8900). OmniRoute provider connection disabled. CT333 service status unknown.
|
||||
- 2026-10-12: web UI confirmed back up (HTTP 200 on `100.122.189.81:8766`, tailnet IP `100.122.189.81` = tailscale node `clawtest`). Status stays DEGRADED because the OmniRoute port 8900 endpoint is still closed. `whatsapp-bridge.service` not re-verified (SSH to CT333 unreachable from CT460).
|
||||
|
||||
+26
-13
@@ -3,8 +3,8 @@ title: Paseo Daemon
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-10-11
|
||||
updated: 2026-10-11
|
||||
verified_on: 2026-10-11
|
||||
updated: 2026-11-04
|
||||
verified_on: 2026-11-04
|
||||
review_after: 2026-11-11
|
||||
confidence: high
|
||||
tags: [system, paseo, coding-agent, ct460, systemd]
|
||||
@@ -19,22 +19,32 @@ and brokers turns to external coding agents — Claude Code, Codex, Cline, OpenC
|
||||
Hermes itself via ACP.
|
||||
|
||||
- Local: `http://127.0.0.1:6767`
|
||||
- Tailnet: `https://hermes.kangaroo-eel.ts.net:6767`
|
||||
- Tailnet: `http://100.118.5.51:6767` (CT460's own tailnet IP)
|
||||
|
||||
> ⚠ **Corrected 2026-11-04.** The old tailnet URL `https://hermes.kangaroo-eel.ts.net:6767` does not work —
|
||||
> **`https://` on port 6767 fails outright** (`curl` → exit code 7 / `http_code=000`; the daemon speaks **plain
|
||||
> HTTP**, not TLS). The hostname `hermes.kangaroo-eel.ts.net` also resolves to **127.0.1.1 locally** (it is bound
|
||||
> to the loopback on this host), so use the tailnet IP for a live check from elsewhere.
|
||||
|
||||
**This page documents the CT460 instance only.** Two more Paseo daemons exist and are easy to confuse with it:
|
||||
**CT465** (`qwenpaw`, `pve`) runs a **system** unit `paseo.service` and **CT1261** (`m93p`, tailnet node `paseo`
|
||||
at `100.72.188.93`) runs another **system** unit `paseo.service` — both on `:6767`. CT460's daemon is the
|
||||
**user** unit `paseo-daemon.service`. The CT460 and CT465 instances answer **HTTP 404** on `/` (alive, but `/` is
|
||||
not a route); only the CT1261 instance answers **HTTP 200** on `/`. All three answer **`/api/health` → 200**.
|
||||
|
||||
The daemon spawns provider processes on demand; a live example is
|
||||
`opencode serve --port 42021` running as a child of the unit.
|
||||
|
||||
## State (verified 2026-10-11 00:16 AWST)
|
||||
## State (re-verified 2026-11-04 04:0x AWST)
|
||||
|
||||
| Item | Value |
|
||||
|---|---|
|
||||
| Unit | `paseo-daemon.service` — **user** unit, `enabled` |
|
||||
| Unit file | `/home/hermes/.config/systemd/user/paseo-daemon.service` |
|
||||
| State | `active (running)` since **2026-10-10 14:47:28 AWST** |
|
||||
| Daemon version | **0.11.2** (upgraded from 0.7.0 on 2026-10-10) |
|
||||
| Main PID | `163127` (`node --disable-warning=DEP0040 /home/hermes/.npm-global/bin/paseo daemon run`) |
|
||||
| Inner processes | supervisor `163168`, `Paseo Daemon` `163198`, terminal worker, `opencode serve` |
|
||||
| Listen | `0.0.0.0:6767` |
|
||||
| State | `active (running)` since **2026-11-02 18:11:04 AWST** |
|
||||
| Daemon version | **0.14.0** (npm-global; was 0.11.2 on 2026-10-11) |
|
||||
| Main PID | `953309` (`node --disable-warning=DEP0040 /home/hermes/.npm-global/bin/paseo daemon run`) |
|
||||
| Listen | `0.0.0.0:6767` — `/` → **404**, `/api/health` → **200** |
|
||||
| Binary used by the unit | `/home/hermes/.npm-global/bin/paseo` |
|
||||
| Config | `/home/hermes/.paseo/config.json` (mode `0600`) |
|
||||
| Logs | `/home/hermes/.paseo/<YYYYMMDD-HHMM>-NN-daemon.log` (10 MB rotation) and `journalctl --user -u paseo-daemon` |
|
||||
@@ -46,7 +56,10 @@ The daemon spawns provider processes on demand; a live example is
|
||||
systemctl --user status paseo-daemon
|
||||
systemctl --user restart paseo-daemon
|
||||
journalctl --user -u paseo-daemon -f
|
||||
curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:6767/
|
||||
curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:6767/api/health # → 200
|
||||
|
||||
# Note: http://127.0.0.1:6767/ returns 404 on CT460 and CT465 (alive, but '/' is not a
|
||||
# route). Use /api/health to test liveness, not '/'.
|
||||
|
||||
Upgrade: `npm install -g @getpaseo/cli@latest`, then restart the unit. **The daemon keeps
|
||||
running the old version until the unit restarts.**
|
||||
@@ -65,9 +78,9 @@ interactive shell's.
|
||||
## Known pitfalls
|
||||
|
||||
- **The `paseo` on `PATH` is not the daemon's version.** `/usr/bin/paseo` reports
|
||||
**0.7.2** while the unit runs the npm-global **0.11.2**. `paseo --version` therefore
|
||||
tells you nothing about what the daemon is running — read the unit's `ExecStart`, or
|
||||
the `daemonVersion` field in the daemon log.
|
||||
**0.7.2** while the unit runs the npm-global **0.14.0** (verified 2026-11-04; it was 0.11.2 on
|
||||
2026-10-11). `paseo --version` therefore tells you nothing about what the daemon is
|
||||
running — read the unit's `ExecStart`, or the `daemonVersion` field in the daemon log.
|
||||
- **A truncated agent binary looks like a provider fault.** A partly-written `cline`
|
||||
binary (107 KB ELF instead of a full ~3 MB) made that one provider fail while every
|
||||
other provider worked. Check binary size before chasing provider config; reinstalling
|
||||
|
||||
+396
-474
@@ -3,8 +3,8 @@ title: Installed Skills
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-11-03
|
||||
verified_on: 2026-11-03
|
||||
updated: 2026-11-05
|
||||
verified_on: 2026-11-05
|
||||
confidence: high
|
||||
tags: [skills, hermes]
|
||||
sources: []
|
||||
@@ -12,10 +12,7 @@ sources: []
|
||||
|
||||
# Installed Skills
|
||||
|
||||
**Total installed: 302 skills** in `~/.hermes/skills/`.
|
||||
|
||||
- **46 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.
|
||||
**Total installed: 349 skills** in `~/.hermes/skills/`.
|
||||
|
||||
This page is auto-regenerated from the live skill inventory. Do not hand-edit.
|
||||
|
||||
@@ -23,508 +20,433 @@ 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`.
|
||||
|
||||
## Apple (4)
|
||||
|
||||
- `apple-notes` — # Apple Notes
|
||||
- `apple-reminders` — # Apple Reminders
|
||||
- `findmy` — # Find My (Apple)
|
||||
- `imessage` — # iMessage
|
||||
|
||||
## Autonomous Ai Agents (8)
|
||||
|
||||
- `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
|
||||
|
||||
## Chromadb (1)
|
||||
|
||||
- `chromadb` — # ChromaDB — Vector Database Operations for the Homelab
|
||||
|
||||
## Chromadb Preflight (1)
|
||||
|
||||
- `chromadb-preflight` — # ChromaDB Preflight — Auto-Context Integration
|
||||
|
||||
## Chromadb Skills Rag (1)
|
||||
|
||||
- `chromadb-skills-rag` — # ChromaDB Skills RAG — Full Integration Layer
|
||||
|
||||
## Clean Architecture (1)
|
||||
|
||||
- `clean-architecture` — # Clean Architecture Framework
|
||||
|
||||
## Clean Code (1)
|
||||
|
||||
- `clean-code` — # Clean Code Framework
|
||||
|
||||
## Cloudflare Tunnel Ops (1)
|
||||
|
||||
- `cloudflare-tunnel-ops` — # Cloudflare Tunnel Operations 🦝🌐
|
||||
|
||||
## Creative (18)
|
||||
|
||||
- `architecture-diagram` — # Architecture Diagram Skill
|
||||
- `ascii-art` — # ASCII Art Skill
|
||||
- `ascii-video` — # ASCII Video Production Pipeline
|
||||
- `baoyu-infographic` — # Infographic Generator
|
||||
- `claude-design` — # Claude Design for CLI/API Agents
|
||||
- `comfyui` — # ComfyUI
|
||||
- `creative-ideation` — # Creative Ideation
|
||||
- `design-md` — # DESIGN.md Skill
|
||||
- `excalidraw` — # Excalidraw Diagram Skill
|
||||
- `humanizer` — # Humanizer: Remove AI Writing Patterns
|
||||
- `hyperframes` — # HyperFrames
|
||||
- `manim-video` — # Manim Video Production Pipeline
|
||||
- `p5js` — # p5.js Production Pipeline
|
||||
- `popular-web-designs` — # Popular Web Designs
|
||||
- `pretext` — # Pretext Creative Demos
|
||||
- `sketch` — # Sketch
|
||||
- `songwriting-and-ai-music` — # Songwriting & AI Music Generation
|
||||
- `touchdesigner-mcp` — # TouchDesigner Integration (twozero MCP)
|
||||
|
||||
## Cron (1)
|
||||
|
||||
- `cron-digest-formatting` — # Cron Digest Formatting (Telegram)
|
||||
|
||||
## Cron Model Repair (1)
|
||||
|
||||
- `cron-model-repair` — # Cron Model-Pin Repair
|
||||
|
||||
## Data Science (1)
|
||||
|
||||
- `jupyter-live-kernel` — # Jupyter Live Kernel (hamelnb)
|
||||
|
||||
## Ddia Systems (1)
|
||||
|
||||
- `ddia-systems` — # Designing Data-Intensive Applications Framework
|
||||
|
||||
## Devops (109)
|
||||
|
||||
- `abyss-ios-pairing` — # Pair iPhone with The Abyss (iOS)
|
||||
- `agent-extension-audit` — # Agent Extension Audit
|
||||
- `agent-observability` — # Agent Observability
|
||||
- `agent-stack-weekly-review` — # Agent Stack Weekly Review
|
||||
- `browser-automation-recovery` — # Browser Automation Recovery
|
||||
- `browser-backend-verification` — # Browser Backend Verification
|
||||
- `browser-tab-lifecycle-and-recovery` — # Browser Tab Lifecycle & Recovery
|
||||
- `camofox-browser-automation` — # Camofox Browser Automation
|
||||
- `camofox-pitfalls` — # Camofox Pitfalls
|
||||
- `camoufox-remote-websocket` — # Camoufox Remote WebSocket Access
|
||||
- `chat4000-ops` — # chat4000 Operations & Pairing
|
||||
- `cloudflare-ops` — # Cloudflare Operations
|
||||
- `codex-via-cliproxy` — # Codex CLI via Cliproxy (mitmproxy redirect)
|
||||
- `crawlee-batch-scrape` — ## Installation
|
||||
- `cron-job-maintenance` — ## Mnemosyne Watchdog Cron Job — Conflict Alert Thresholds (2026-07-25)
|
||||
- `cross-profile-session-handoff` — # Cross-Profile Session Handoff
|
||||
- `cua-computer-use` — # CUA Computer Use Automation
|
||||
- `cua-driver-lifecycle` — # cua-driver Lifecycle Management
|
||||
- `dashboard-server-ops` — # Dashboard Server Operations
|
||||
- `devops` — (no description)
|
||||
- `docker-management` — # Docker Management
|
||||
- `external-auth-script-integration` — # External Auth Script Integration
|
||||
- `external-skill-integration` — # External Skill Integration
|
||||
- `fleet-wide-failure-triage` — # Fleet-Wide Failure Triage
|
||||
- `free-web-tools` — # Free Web Search & Extract
|
||||
- `freshrss-intelligence-filter` — # FreshRSS Intelligence Filter
|
||||
- `gcp-vertex-ai-provider` — # GCP Vertex AI Provider
|
||||
- `gmail-imap-email-monitor` — # Gmail IMAP Email Monitor (Cron)
|
||||
- `google-apis` — # Google APIs Tool Suite
|
||||
- `google-contacts-birthday-sync` — > **See also:**
|
||||
- `hermes-agent-install` — # Hermes Agent Install & Upgrade
|
||||
- `hermes-agent-ops` — ### Dashboard Auth Plugin — `basic` Must Be Enabled
|
||||
- `hermes-api-vault` — # Hermes API Vault
|
||||
- `hermes-config-diagnostics` — # Hermes Config Diagnostics
|
||||
- `hermes-cron-operations` — # Hermes Cron Operations
|
||||
- `hermes-cron-patterns` — ## Reference Files
|
||||
- `hermes-gateway-config-loading` — # Hermes Gateway Config Loading Pipeline
|
||||
- `hermes-gateway-ops` — # Hermes Gateway Operations & Platform Debugging
|
||||
- `hermes-instance-migration` — # Hermes Instance Migration (audit + curated port)
|
||||
- `hermes-instance-update` — # Hermes Instance Update Operations
|
||||
- `hermes-mattermost-integration` — # Hermes Mattermost Integration
|
||||
- `hermes-memory-systems` — # Hermes Agent Memory Systems
|
||||
- `hermes-multi-agent` — # Hermes Multi-Agent Architecture
|
||||
- `hermes-plugin-live-verification` — # Hermes Plugin Live Verification
|
||||
- `hermes-plugin-ops` — ### Session Learnings (2026-07-07)
|
||||
- `hermes-profile-ops` — # Hermes Profile Operations
|
||||
- `hermes-provider-configuration` — # Hermes Provider Configuration
|
||||
- `hermes-routing-and-domains` — # Hermes Routing & Domains
|
||||
- `hermes-self-diagnosis` — # Hermes Self-Diagnosis
|
||||
- `hermes-soul-forge` — # Soul Forge Plugin Operations
|
||||
- `hermes-web-tools` — # Hermes Web Tools (this instance)
|
||||
- `hermes-webui-ops` — # Hermes WebUI Operations
|
||||
- `hindsight-docs` — # Hindsight Documentation Skill
|
||||
- `hindsight-import-mnemosyne` — # Import Mnemosyne → Hindsight
|
||||
- `hindsight-ops` — # Hindsight Operations & Diagnostics
|
||||
- `hindsight-selfhost` — # Self-Host Hindsight (bare-metal) + Official Control Plane
|
||||
- `homarr-dashboard-management` — # Homarr Dashboard Management (v1 on runtipi)
|
||||
- `homarr-dashboard-ops` — # Homarr Dashboard Operations
|
||||
- `homelab-docker-update` — # Homelab Docker Update
|
||||
- `homelab-instance-migration` — # Homelab Instance Migration
|
||||
- `homelab-service-management` — # Homelab Service Management
|
||||
- `homelab-virtual-desktop` — # Homelab Virtual Desktop (for computer-use)
|
||||
- `ignis-ops` — # Ignis Deployment & Operations
|
||||
- `job-board-scraping-reference` — # Job Board Scraping Reference
|
||||
- `kanban-orchestrator` — # Kanban Orchestrator — Decomposition Playbook
|
||||
- `kanban-worker` — # Kanban Worker — Pitfalls and Examples
|
||||
- `linux-systemd-desktop` — # Linux headless desktop as a systemd user service
|
||||
- `litellm-openrouter-key-pooling` — # LiteLLM OpenRouter Key Pooling
|
||||
- `litellm-proxy-ops` — # LiteLLM Proxy Operations
|
||||
- `llm-model-diagnostics` — # LLM Model Diagnostics
|
||||
- `mattermost-ops` — # Mattermost Operations 🦝📡
|
||||
- `mattermost-platform-ops` — # Mattermost Platform Operations
|
||||
- `mcp-agent-integration` — # MCP Agent Integration
|
||||
- `memory-governance` — # Memory Governance
|
||||
- `mnemosyne-operations` — # Mnemosyne Operations & Diagnostics
|
||||
- `multi-agent-git-ops` — # Multi-Agent Git Operations
|
||||
- `nanobot-omniroute-skills` — # Nanobot ↔ OmniRoute Skills Integration
|
||||
- `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...
|
||||
- `omniroute-combo-troubleshooting` — # OmniRoute Combo Troubleshooting
|
||||
- `omniroute-context-tuning` — # OmniRoute Context Window Tuning
|
||||
- `omniroute-mcp-portal-cloudflare-auth` — # Cloudflare Access Auth for mcp-portal.martinwa.org/mcp
|
||||
- `omniroute-ops` — # OmniRoute Operations & Diagnostics
|
||||
- `omniroute-skill-caller` — # Call an OmniRoute Skill by Name (auto-resolving wrapper)
|
||||
- `omniroute-skill-execution` — # Execute Skills on OmniRoute MCP
|
||||
- `openclaw-ops` — # Open-Claw Operations & Configuration
|
||||
- `pulse-turn-handling` — # Pulse Turn Handling
|
||||
- `pve-ops` — # PVE Operations
|
||||
- `radar-jobs-dashboard` — # RADAR Jobs Dashboard
|
||||
- `readlater-ops` — # ReadLater Operations
|
||||
- `runtipi-container-management` — # Runtipi Container Management
|
||||
- `sdlc-review` — # SDLC Review Skill
|
||||
- `self-hosted-app-deploy` — # Self-Hosted App Deployment
|
||||
- `solutions-first-agent-conduct` — # Solutions-First Agent Conduct
|
||||
- `tailscale-ops` — # Tailscale Operations 🦝🔗
|
||||
- `tailscale-serve-route-management` — # Tailscale Serve Route Management
|
||||
- `tailscale-serve-routes` — # Tailscale Serve Route Management
|
||||
- `task-approach` — # Task Approach
|
||||
- `telegram-create-forum-topic` — # Telegram Create Forum Topic Skill
|
||||
- `tmux-config` — # tmux-config
|
||||
- `tool-ecosystem-evaluation` — # Tool Ecosystem Evaluation
|
||||
- `uber-eats-monitor` — # Uber Eats Order Monitor
|
||||
- `vision-model-validation` — # Vision Model Validation via OmniRoute
|
||||
- `watchers` — # Watchers
|
||||
- `web-content-extraction` — # Web Content Extraction — Fallback Techniques
|
||||
- `weekly-comms-tracker` — # Weekly Communications Tracker
|
||||
- `wiki-maintenance` — # Wiki Maintenance
|
||||
- `zeroclaw-ops` — # ZeroClaw Operations & Configuration
|
||||
|
||||
## Devops Homelab Architecture Live Probe (1)
|
||||
|
||||
- `devops-homelab-architecture-live-probe` — # Homelab Architecture Live Probe
|
||||
|
||||
## Devops Proxmox Operations (1)
|
||||
|
||||
- `devops-proxmox-operations` — # Proxmox Operations
|
||||
|
||||
## Devops Service Management (1)
|
||||
|
||||
- `devops-service-management` — # Service Operations Umbrella
|
||||
|
||||
## Devops Tailscale Web Routing (1)
|
||||
|
||||
- `devops-tailscale-web-routing` — # Tailscale Web Routing
|
||||
|
||||
## Devops Telegram Bot Api Self Hosted (1)
|
||||
|
||||
- `devops-telegram-bot-api-self-hosted` — # Self-Hosted Telegram Bot API Server
|
||||
|
||||
## Domain Driven Design (1)
|
||||
|
||||
- `domain-driven-design` — # Domain-Driven Design Framework
|
||||
|
||||
## Email (17)
|
||||
|
||||
- `agent-email-patterns` — # Agent Email Patterns
|
||||
- `agentmail` — # AgentMail — Agent-Owned Email Inboxes
|
||||
- `agentmail-check-email` — # Check Email
|
||||
- `agentmail-cli` — # AgentMail CLI
|
||||
- `agentmail-manage-inboxes` — # Manage Inboxes
|
||||
- `agentmail-mcp` — # AgentMail MCP
|
||||
- `agentmail-rest-fallback` — # AgentMail REST API Fallback
|
||||
- `agentmail-sdk` — # AgentMail SDK
|
||||
- `agentmail-send-email` — # Send Email
|
||||
- `agentmail-toolkit` — # AgentMail Toolkit
|
||||
- `cron-email-briefing` — # Cron Email Briefing Workflow
|
||||
- `email-for-ai-agents` — # Agent Email Patterns
|
||||
- `email-inbox-triage` — # Email Inbox Triage
|
||||
- `gmail-readonly-fetch` — # Gmail Read-Only Fetch (Large Inbox)
|
||||
- `himalaya` — # Himalaya Email CLI
|
||||
- `mail-lookup` — # Ad-Hoc Mail Lookup
|
||||
- `realtime-email-monitor` — # Real-time Email Monitor (IMAP IDLE)
|
||||
|
||||
## Email Himalaya (1)
|
||||
|
||||
- `email-himalaya` — # Himalaya Email CLI
|
||||
|
||||
## Finance (2)
|
||||
|
||||
- `3-statement-model` — ## Environment
|
||||
- `australian-tax-return-review` — # Australian Tax Return Review
|
||||
|
||||
## Frontend (4)
|
||||
|
||||
- `design-alignment` — # Design Alignment
|
||||
- `impeccable` — Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft.
|
||||
- `landing-dashboard-reference` — # Landing Page & Dashboard Design Reference
|
||||
- `pixel-perfect-iteration` — # Pixel-Perfect Visual Iteration
|
||||
|
||||
## Github (6)
|
||||
|
||||
- `github-auth` — # GitHub Authentication Setup
|
||||
- `github-code-review` — # GitHub Code Review
|
||||
- `github-issue-to-pr` — # GitHub Issue to Pull Request
|
||||
- `github-issues` — # GitHub Issues Management
|
||||
- `github-pr-workflow` — # GitHub Pull Request Workflow
|
||||
- `github-repo-management` — # GitHub Repository Management
|
||||
|
||||
## Groktocrawl Deployment (1)
|
||||
|
||||
- `groktocrawl-deployment` — # GroktoCrawl Self-Hosted Deployment
|
||||
- `antigravity-cli` — Operate the Antigravity CLI (agy): plugins, auth, sandbox.
|
||||
- `claude-code` — Delegate coding to Claude Code CLI (features, PRs).
|
||||
- `codex` — Delegate coding to OpenAI Codex CLI (features, PRs).
|
||||
- `computer-use` — Drive the desktop background-first; escalate on signal.
|
||||
- `hermes-agent` — Use, configure, theme, extend, and orchestrate Hermes Agent.
|
||||
- `merge-reconciler` — Neutral third-party resolution of agent merge conflicts.
|
||||
- `opencode` — Delegate coding to OpenCode CLI (features, PR review).
|
||||
- `openhands` — Delegate coding to OpenHands CLI (model-agnostic, LiteLLM).
|
||||
|
||||
## Hermes (3)
|
||||
|
||||
- `hermes-personality-soulmd` — # Hermes Personality & SOUL.md
|
||||
- `hermes-telegram-miniapp` — # Hermes Telegram Mini App — Deploy & Operate
|
||||
- `hermes-tts-configuration` — # Hermes TTS & Voice Configuration
|
||||
- `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.
|
||||
|
||||
## Hermes Api Vault (1)
|
||||
## Devops (108)
|
||||
|
||||
- `hermes-api-vault` — # Hermes API Vault
|
||||
- `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
|
||||
- `mattermost-platform-ops` — Debug Hermes Mattermost adapter: typing, delivery, auth.
|
||||
- `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
|
||||
- `pulse-turn-handling` — Use when Pulse turns arrive; obey its exact reply contract.
|
||||
- `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
|
||||
|
||||
## Hermes Desktop Plugins (1)
|
||||
## Productivity (26)
|
||||
|
||||
- `hermes-desktop-plugins` — # Hermes Desktop Plugins Skill
|
||||
- `airtable` — Airtable REST API via curl. Records CRUD, filters, upserts.
|
||||
- `box` — Box manages cloud files, sharing, search, and metadata.
|
||||
- `custom-pet-authoring` — Create custom animated pet spritesheets for Hermes' petdex system. Covers the pet format spec, Pillow-based spritesheet
|
||||
- `document-to-action-items` — Extract cited obligations, deadlines, tasks from documents.
|
||||
- `docx` — Create, read, edit, template, and review Word .docx files.
|
||||
- `google-workspace` — Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.
|
||||
- `maps` — Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.
|
||||
- `meeting-action-items` — Turn meeting notes into cited decisions, owners, tickets.
|
||||
- `nano-pdf` — Edit text in existing PDFs via natural-language prompts.
|
||||
- `notion` — Notion API + ntn CLI: pages, databases, markdown, Workers.
|
||||
- `notion-database-dedup` — Clean duplicates from Notion databases with quality scoring. Fetch all pages with pagination, compare by URL/company+rol
|
||||
- `obsidian-git-sync` — >
|
||||
- `obsidian-git-sync` — >
|
||||
- `ocr-and-documents` — Extract text from PDFs/scans (pymupdf, marker-pdf).
|
||||
- `pdf` — PDF files: create, read, merge, fill, OCR, edit text.
|
||||
- `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.
|
||||
- `weekly-review-planning` — Weekly reset: commitments, stalled work, next-week plan.
|
||||
- `xlsx` — Create, read, edit Excel .xlsx workbooks and CSVs.
|
||||
|
||||
## Hermes Gateway Troubleshooting (1)
|
||||
## Creative (18)
|
||||
|
||||
- `hermes-gateway-troubleshooting` — # Hermes Gateway Troubleshooting & Migration Verification
|
||||
|
||||
## Hermes Mcp Troubleshooting (1)
|
||||
|
||||
- `hermes-mcp-troubleshooting` — # Hermes MCP Troubleshooting
|
||||
|
||||
## Hermes Themes (1)
|
||||
|
||||
- `hermes-themes` — # Hermes Themes Skill
|
||||
|
||||
## Interactive Reference Pages (1)
|
||||
|
||||
- `interactive-reference-pages` — # Interactive Reference Pages
|
||||
|
||||
## Ios Hig Design (1)
|
||||
|
||||
- `ios-hig-design` — # iOS Human Interface Guidelines Design Skill
|
||||
|
||||
## Job Hunting (2)
|
||||
|
||||
- `job-hunting` — # Job Hunting & Career Transition Coaching
|
||||
- `seek-extraction-patterns` — # SEEK Extraction Patterns
|
||||
|
||||
## Job Hunting Assistance (1)
|
||||
|
||||
- `job-hunting-assistance` — # Job Hunting Assistance
|
||||
|
||||
## Job Search Automation (1)
|
||||
|
||||
- `job-search-automation` — # Job Search Automation
|
||||
|
||||
## Job Tracker Enrichment (1)
|
||||
|
||||
- `job-tracker-enrichment` — # Job Tracker Enrichment (Anthony — Perth Marketing)
|
||||
|
||||
## Litprog (1)
|
||||
|
||||
- `litprog` — # Literate Programming
|
||||
|
||||
## Markdown To Anywhere (1)
|
||||
|
||||
- `markdown-to-anywhere` — # Markdown to Anywhere
|
||||
|
||||
## Mcp (2)
|
||||
|
||||
- `fastmcp` — # FastMCP
|
||||
- `mcporter` — # mcporter
|
||||
|
||||
## Media (4)
|
||||
|
||||
- `gif-search` — # GIF Search (Tenor API)
|
||||
- `heartmula` — # HeartMuLa - Open-Source Music Generation
|
||||
- `songsee` — # songsee
|
||||
- `youtube-content` — # YouTube Content Tool
|
||||
|
||||
## Mlops (10)
|
||||
|
||||
- `audiocraft` — # AudioCraft: Audio Generation
|
||||
- `chroma` — # Chroma - Open-Source Embedding Database
|
||||
- `clip` — # CLIP - Contrastive Language-Image Pre-Training
|
||||
- `evaluating-llms-harness` — # lm-evaluation-harness - LLM Benchmarking
|
||||
- `huggingface-hub` — # Hugging Face CLI (`hf`) Reference Guide
|
||||
- `llama-cpp` — # llama.cpp + GGUF
|
||||
- `qdrant` — # Qdrant - Vector Similarity Search Engine
|
||||
- `segment-anything` — # Segment Anything Model (SAM)
|
||||
- `serving-llms-vllm` — # vLLM - High-Performance LLM Serving
|
||||
- `weights-and-biases` — # Weights & Biases: ML Experiment Tracking & MLOps
|
||||
|
||||
## Note Taking (2)
|
||||
|
||||
- `obsidian-vault-from-git` — ## Obsidian Vault from Git
|
||||
- `obsidian-vault-manager` — # Obsidian Vault Manager
|
||||
|
||||
## Officecli (1)
|
||||
|
||||
- `officecli` — # officecli
|
||||
|
||||
## Omniroute (1)
|
||||
|
||||
- `omniroute-skills` — # OmniRoute Skills
|
||||
|
||||
## Pragmatic Programmer (1)
|
||||
|
||||
- `pragmatic-programmer` — # The Pragmatic Programmer Framework
|
||||
|
||||
## Productivity (25)
|
||||
|
||||
- `airtable` — # Airtable — Bases, Tables & Records
|
||||
- `box` — # Box
|
||||
- `custom-pet-authoring` — # Custom Pet Authoring
|
||||
- `document-to-action-items` — # Document to Action Items
|
||||
- `docx` — # Docx Skill
|
||||
- `google-workspace` — # Google Workspace
|
||||
- `maps` — # Maps Skill
|
||||
- `meeting-action-items` — # Meeting Action Items
|
||||
- `nano-pdf` — # nano-pdf
|
||||
- `notion` — # Notion
|
||||
- `notion-database-dedup` — # Notion Database Dedup
|
||||
- `obsidian-git-sync` — # Obsidian Git Sync Workflow
|
||||
- `ocr-and-documents` — # PDF & Document Extraction
|
||||
- `pdf` — # PDF Skill
|
||||
- `petdex` — # Petdex Skill
|
||||
- `petdex-custom` — # Petdex Custom Pets
|
||||
- `powerpoint` — # Powerpoint Skill
|
||||
- `product-price-monitor` — # Product Price Monitor
|
||||
- `session-librarian` — # Session Librarian
|
||||
- `stratos-command-centre` — # Stratos — Command Centre
|
||||
- `teams-meeting-pipeline` — # Teams Meeting Pipeline
|
||||
- `telegram-cron-table-formatting` — # Telegram Table Formatting (Hermes)
|
||||
- `tui-widgets` — # TUI Widgets Skill
|
||||
- `weekly-review-planning` — # Weekly Review and Planning
|
||||
- `xlsx` — # Xlsx Skill
|
||||
|
||||
## Proxmox Operations (1)
|
||||
|
||||
- `proxmox-operations` — # Proxmox Operations
|
||||
|
||||
## Refactoring Patterns (1)
|
||||
|
||||
- `refactoring-patterns` — # Refactoring Patterns Framework
|
||||
|
||||
## Refactoring Ui (1)
|
||||
|
||||
- `refactoring-ui` — # Refactoring UI Design System
|
||||
|
||||
## Research (14)
|
||||
|
||||
- `arxiv` — # arXiv Research
|
||||
- `blogwatcher` — # Blogwatcher
|
||||
- `chat-export-parsing` — # Chat Export Parsing
|
||||
- `competitor-news-monitor` — # Competitor News Monitor
|
||||
- `grounded-citations` — # Grounded Citations
|
||||
- `llm-wiki` — # Karpathy's LLM Wiki
|
||||
- `local-dining-scene-monitor` — # Local Dining Scene Monitor
|
||||
- `operations-wiki` — # Operations Wiki
|
||||
- `polymarket` — # Polymarket — Prediction Market Data
|
||||
- `research-paper-writing` — # Research Paper Writing Pipeline
|
||||
- `rss-feeds` — # RSS Feeds Skill
|
||||
- `scrapling` — # Scrapling
|
||||
- `searxng-search` — # SearXNG Search
|
||||
- `wikilink-audit` — # Wikilink Auditor
|
||||
|
||||
## Restaurant Menu Extraction (1)
|
||||
|
||||
- `restaurant-menu-extraction` — # Restaurant Menu Extraction
|
||||
|
||||
## Smart Home (2)
|
||||
|
||||
- `openhue` — # OpenHue CLI
|
||||
- `sonos` — # Sonos Skill
|
||||
|
||||
## Social Media (2)
|
||||
|
||||
- `reddit-reading` — # Reddit Reading Skill
|
||||
- `xurl` — # xurl — X (Twitter) API via the Official CLI
|
||||
|
||||
## Software Design Philosophy (1)
|
||||
|
||||
- `software-design-philosophy` — # A Philosophy of Software Design Framework
|
||||
- `architecture-diagram` — Dark-themed SVG architecture/cloud/infra diagrams as HTML.
|
||||
- `ascii-art` — ASCII art: pyfiglet, cowsay, boxes, image-to-ascii.
|
||||
- `ascii-video` — ASCII video: convert video/audio to colored ASCII MP4/GIF.
|
||||
- `baoyu-infographic` — Infographics: 21 layouts x 21 styles (信息图, 可视化).
|
||||
- `claude-design` — Design one-off HTML artifacts (landing, deck, prototype).
|
||||
- `comfyui` — Generate images, video, and audio via diffusion workflows.
|
||||
- `creative-ideation` — Generate ideas via named methods from creative practice.
|
||||
- `design-md` — Author/validate/export Google's DESIGN.md token spec files.
|
||||
- `excalidraw` — Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).
|
||||
- `humanizer` — Humanize text: strip AI-isms and add real voice.
|
||||
- `hyperframes` — Render MP4/WebM videos from HTML compositions.
|
||||
- `manim-video` — Manim CE animations: 3Blue1Brown math/algo videos.
|
||||
- `p5js` — p5.js sketches: gen art, shaders, interactive, 3D.
|
||||
- `popular-web-designs` — 54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
|
||||
- `pretext` — Build creative browser demos with DOM-free text layout.
|
||||
- `sketch` — Throwaway HTML mockups: 2-3 design variants to compare.
|
||||
- `songwriting-and-ai-music` — Songwriting craft and Suno AI music prompts.
|
||||
- `touchdesigner-mcp` — Control TouchDesigner via twozero MCP.
|
||||
|
||||
## Software Development (18)
|
||||
|
||||
- `code-wiki` — # Code Wiki Skill
|
||||
- `codebase-inspection` — # Codebase Inspection with pygount
|
||||
- `coding-router` — # Coding Router
|
||||
- `dogfood` — # Dogfood: Systematic Web Application QA Testing
|
||||
- `github` — # GitHub
|
||||
- `hermes-agent-skill-authoring` — # Authoring Hermes-Agent Skills (in-repo)
|
||||
- `inspecting-hermes-desktop-dom` — # Inspecting the live Hermes desktop DOM
|
||||
- `node-inspect-debugger` — # Node.js Inspect Debugger
|
||||
- `plan` — # Plan Mode
|
||||
- `python-debugpy` — # Python Debugger (pdb + debugpy)
|
||||
- `requesting-code-review` — # Pre-Commit Code Verification
|
||||
- `rest-graphql-debug` — # API Testing & Debugging
|
||||
- `self-hosted-personal-dashboard` — # Self-Hosted Personal Dashboard
|
||||
- `simplify-code` — # Simplify Code — Parallel Review & Cleanup
|
||||
- `spike` — # Spike
|
||||
- `subagent-driven-development` — # Subagent-Driven Development
|
||||
- `systematic-debugging` — # Systematic Debugging
|
||||
- `test-driven-development` — # Test-Driven Development (TDD)
|
||||
- `code-wiki` — Generate wiki docs + Mermaid diagrams for any codebase.
|
||||
- `codebase-inspection` — Inspect codebases w/ pygount: LOC, languages, ratios.
|
||||
- `coding-router` — Routes substantial software-development tasks to OpenCode CLI by default and Codex CLI as fallback, while Hermes remains
|
||||
- `dogfood` — Exploratory QA of web apps: find bugs, evidence, reports.
|
||||
- `github` — GitHub via gh CLI: PRs, issues, reviews, repos, auth.
|
||||
- `hermes-agent-skill-authoring` — Author in-repo SKILL.md files: frontmatter and structure.
|
||||
- `inspecting-hermes-desktop-dom` — Read the live Hermes desktop DOM/CSS over CDP.
|
||||
- `node-inspect-debugger` — Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
|
||||
- `plan` — Write a markdown plan to .hermes/plans/; no execution.
|
||||
- `python-debugpy` — Debug Python: pdb REPL + debugpy remote (DAP).
|
||||
- `requesting-code-review` — Pre-commit review: security scan, quality gates, auto-fix.
|
||||
- `rest-graphql-debug` — Debug REST/GraphQL APIs: status codes, auth, schemas, repro.
|
||||
- `self-hosted-personal-dashboard` — >
|
||||
- `simplify-code` — Parallel 4-agent cleanup of recent code changes.
|
||||
- `spike` — Throwaway experiments to validate an idea before build.
|
||||
- `subagent-driven-development` — Execute plans via delegate_task subagents (2-stage review).
|
||||
- `systematic-debugging` — 4-phase root cause debugging: understand bugs before fixing.
|
||||
- `test-driven-development` — TDD: enforce RED-GREEN-REFACTOR, tests before code.
|
||||
|
||||
## System Design (1)
|
||||
## Research (14)
|
||||
|
||||
- `system-design` — # System Design Framework
|
||||
- `arxiv` — Search arXiv papers by keyword, author, category, or ID.
|
||||
- `blogwatcher` — Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool.
|
||||
- `chat-export-parsing` — Parse chat/messaging-platform export files (Telegram MTProto message.json, WhatsApp exports, Slack/Discord JSON) into re
|
||||
- `competitor-news-monitor` — Watch named companies for material news; cited digests.
|
||||
- `grounded-citations` — Ground answers and documents in cited, verifiable sources.
|
||||
- `llm-wiki` — Karpathy's LLM Wiki: build/query interlinked markdown KB.
|
||||
- `local-dining-scene-monitor` — Monitor city restaurant openings weekly with dedup.
|
||||
- `operations-wiki` — Operational wiki for personal AI agents, self-hosted infrastructure, model routing and automation.
|
||||
- `polymarket` — Query Polymarket: markets, prices, orderbooks, history.
|
||||
- `research-paper-writing` — Write ML papers for NeurIPS/ICML/ICLR: design→submit.
|
||||
- `rss-feeds` — Read RSS, Atom, JSON feeds; discover feeds behind a page.
|
||||
- `scrapling` — Scrape sites with stealth browsing and Cloudflare bypass.
|
||||
- `searxng-search` — Free keyless meta-search aggregating 70+ engines.
|
||||
- `wikilink-audit` — Scan and fix broken [[wikilinks]] in an Obsidian vault or markdown knowledge base. Finds orphans, broken links, and temp
|
||||
|
||||
## Tailscale Serve Ops (1)
|
||||
## Email (17)
|
||||
|
||||
- `tailscale-serve-ops` — # Tailscale Serve Ops 🦝🔗
|
||||
- `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
|
||||
- `email-inbox-triage` — Triage an inbox: prioritize threads, draft replies safely.
|
||||
- `gmail-readonly-fetch` — Read-only email fetching from large Gmail inboxes via himalaya CLI or Python imaplib — cron-safe, paginated, with LLM ha
|
||||
- `himalaya` — Himalaya CLI: IMAP/SMTP email from terminal.
|
||||
- `mail-lookup` — Use when asked about one specific email, order, or receipt.
|
||||
- `realtime-email-monitor` — >-
|
||||
|
||||
## Tech Ai Newsletter Digest (1)
|
||||
## Mlops (10)
|
||||
|
||||
- `tech-ai-newsletter-digest` — # Tech & AI Newsletter Digest Skill
|
||||
- `chroma` — Embedding database for RAG and semantic search.
|
||||
- `clip` — Zero-shot image classification and image-text search.
|
||||
- `evaluation` — W&B: log ML experiments, sweeps, model registry, dashboards.
|
||||
- `evaluation` — lm-eval-harness: benchmark LLMs (MMLU, GSM8K, etc.).
|
||||
- `huggingface-hub` — HuggingFace hf CLI: search/download/upload models, datasets.
|
||||
- `inference` — llama.cpp local GGUF inference + HF Hub model discovery.
|
||||
- `inference` — vLLM: high-throughput LLM serving, OpenAI API, quantization.
|
||||
- `models` — AudioCraft: MusicGen text-to-music, AudioGen text-to-sound.
|
||||
- `models` — SAM: zero-shot image segmentation via points, boxes, masks.
|
||||
- `qdrant` — Vector search engine for production RAG systems.
|
||||
|
||||
## Ux Heuristics (1)
|
||||
## Github (6)
|
||||
|
||||
- `ux-heuristics` — # UX Heuristics Framework
|
||||
- `github-auth` — GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.
|
||||
- `github-code-review` — Review PRs: diffs, inline comments via gh or REST.
|
||||
- `github-issue-to-pr` — Carry a GitHub issue to a verified PR with honest CI state.
|
||||
- `github-issues` — Create, triage, label, assign GitHub issues via gh or REST.
|
||||
- `github-pr-workflow` — GitHub PR lifecycle: branch, commit, open, CI, merge.
|
||||
- `github-repo-management` — Clone/create/fork repos; manage remotes, releases.
|
||||
|
||||
## Web (1)
|
||||
## Apple (4)
|
||||
|
||||
- `blocked-page-recovery` — # Blocked-Page Recovery
|
||||
- `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.
|
||||
|
||||
## Web Design Reviewer (1)
|
||||
## Frontend (4)
|
||||
|
||||
- `web-design-reviewer` — # Web Design Reviewer
|
||||
- `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` — # Interactive HTML Pages
|
||||
- `page-agent` — # page-agent
|
||||
- `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.
|
||||
|
||||
## Web Typography (1)
|
||||
## Smart Home (2)
|
||||
|
||||
- `web-typography` — # Web Typography
|
||||
- `openhue` — Control Philips Hue lights, scenes, rooms via OpenHue CLI.
|
||||
- `sonos` — >
|
||||
|
||||
## Weekly Review (1)
|
||||
## Mcp (2)
|
||||
|
||||
- `weekly-review` — # Weekly Review
|
||||
- `fastmcp` — Build, test, and deploy Python MCP servers.
|
||||
- `mcporter` — List, auth, and call MCP servers/tools from the terminal.
|
||||
|
||||
## Working With Legacy Code (1)
|
||||
## Uncategorized (46)
|
||||
|
||||
- `working-with-legacy-code` — # Working Effectively with Legacy Code
|
||||
- `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-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
|
||||
- `yuanbao` — Yuanbao (元宝) groups: @mention users, query info/members.
|
||||
|
||||
## Yuanbao (1)
|
||||
## .Archive (46)
|
||||
|
||||
- `yuanbao` — # Yuanbao Group Interaction
|
||||
- `agentmail-webhook-tailscale` — Real-time AgentMail webhooks via Tailscale funnel push.
|
||||
- `anthropic-spend-forensics` — Use when unexplained Anthropic spend needs attribution.
|
||||
- `briefing-visualization` — Research text → HTML briefing + PPTX deck.
|
||||
- `container-cpu-forensics` — Find idle-CPU vampires: cgroup truth, crash loops.
|
||||
- `cookie-jar-import` — Import browser cookies into Camofox for auth sessions.
|
||||
- `courier-tracking-monitor` — Monitor a package/shipment; alert on change or delivery.
|
||||
- `cover-letter-generation` — Draft, render, and deliver styled cover letters for Anthony's job applications. Covers content, format selection, PDF/DO
|
||||
- `cron-prompt-service-integration` — Authed-API cron prompts: wrap calls in helper scripts.
|
||||
- `cronjob-prompt-hardening` — Use when hardening cronjob prompts against fabrication.
|
||||
- `cua-driver-linux-accessibility` — Fix AT-SPI bridge when computer_use returns 0x0 on Linux.
|
||||
- `custom-dashboard-ops` — Operate or deploy the custom-dashboard on CT201.
|
||||
- `data-share-to-ai-artefact` — Turn a file-share of KPI CSVs into one labelled xlsx for AI.
|
||||
- `decision-briefing-dashboards` — Use when advice needs an offline decision dashboard.
|
||||
- `employment-forms` — Fill out Anthony's employment and onboarding forms.
|
||||
- `guanaco-ops` — Operate Guanaco LLM proxy on CT205.
|
||||
- `hermes-config-backup` — Use when Hermes' Gitea config backup is stale or missing.
|
||||
- `hermes-multiplex-telegram-ops` — Diagnose Hermes profile Telegram silence under multiplex.
|
||||
- `hermes-profile-scoped-platform-troubleshooting` — Repair platform adapter mismatches across Hermes profiles.
|
||||
- `hermes-runtime-worker-diagnostics` — Use when many cron jobs fail at once, before job logic.
|
||||
- `hermes-session-context-ops` — Use when Hermes desktop chats lose or blend context.
|
||||
- `hermes-ui-ops` — Operate Hermes desktop UI — Vite, HTTPS, mic, systemd.
|
||||
- `hermes-web-backend-config` — Fix web_search backend selection and Tavily quota fallback.
|
||||
- `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.
|
||||
- `session-verification` — Verify session claims — check DB, not memory.
|
||||
- `simple-directives-execution` — Execute now when told 'just do X' — no investigation.
|
||||
- `social-web-sentiment-research` — Use for current social/web sentiment scans.
|
||||
- `soul-md-design` — Research SOUL.md patterns for structured agent personas.
|
||||
- `tailnet-service-outage-triage` — Triage tailnet service-down alerts without PVE SSH.
|
||||
- `tailscale-cert-for-docker-https` — Fix tailnet HTTPS cert errors with trusted Tailscale certs.
|
||||
- `versioning-live-services` — Use when versioning a live service dir into a private repo.
|
||||
- `video-translation-dubbing` — Translate and dub video audio to another language.
|
||||
- `wiki-web-hosting` — Publish Markdown wikis as Quartz sites over Tailscale.
|
||||
|
||||
## Finance (2)
|
||||
|
||||
- `3-statement-model` — Build integrated IS/BS/CF financial workbooks in Excel.
|
||||
- `australian-tax-return-review` — Review an Australian tax return against source records.
|
||||
|
||||
## Social Media (2)
|
||||
|
||||
- `reddit-reading` — Read Reddit: subreddits, search, threads, users. No browser.
|
||||
- `xurl` — X/Twitter via xurl CLI: raw post search, posting, DM, media.
|
||||
|
||||
## Cron (1)
|
||||
|
||||
- `cron-digest-formatting` — Use when formatting cron Telegram news digests for Anthony.
|
||||
|
||||
## Data Science (1)
|
||||
|
||||
- `jupyter-live-kernel` — Iterative Python via live Jupyter kernel (hamelnb).
|
||||
|
||||
## Job Hunting (1)
|
||||
|
||||
- `seek-extraction-patterns` — Extract salary, closing dates, and job details from SEEK (au.seek.com) listings at scale. Use when enriching a batch of
|
||||
|
||||
## Omniroute (1)
|
||||
|
||||
- `omniroute-skills` — Interact with OmniRoute's Skills framework — list, install, enable, execute, and debug skills via REST API and MCP tools
|
||||
|
||||
## Web (1)
|
||||
|
||||
- `blocked-page-recovery` — Use when a fetch fails: 403/429, paywall, WAF, bot wall.
|
||||
|
||||
## Related
|
||||
- [[systems/hermes-agent]]
|
||||
- [[systems/omniroute]]
|
||||
|
||||
Reference in New Issue
Block a user