Individual skill
Hermes
Hermes sidecar observability: health, failure triage, cron, guard blocks, logs, traces. USE WHEN hermes, sidecar, hermes failed, hermes task failed, iMessage task failed, message task failed, why did hermes fail, hermes not calling LifeOS, hermes status, hermes health, trace hermes, hermes session, hermes logs, hermes cron, guard blocks, triage hermes, sidecar broken, update hermes, upgrade hermes, is hermes up to date, keep hermes updated. NOT FOR mounting (LIFEOS/HERMES/Mount.ts), LifeOS services (Services.ts), messaging (the communication skill).
LifeOS/install/skills/Hermes/SKILL.md
Source commit b7efec97d8c3885feee285bee468c35602fb0606
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 19,767
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- augmentation Repository topic
- productivity Repository topic
- humans Repository topic
- ai-harness Repository topic
- intent-engineering Repository topic
- personal-ai Repository topic
- coding Repository topic
- lifeos Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Intents/Status.mddoc · 1,658 bytesIntents/Trace.mddoc · 2,558 bytesIntents/Triage.mddoc · 2,081 bytesIntents/Update.mddoc · 5,112 bytesSKILL.mdcore · 7,533 bytesSetup.mddoc · 4,415 bytes
Read excerpt
# Hermes
Observability over a mounted Hermes sidecar. The sidecar keeps its own records (session store, cron execution history, error logs, guard audit trail), and this skill turns them into answers: is it healthy, what failed and why, and exactly what happened inside one task.
Everything runs against the live install at `$HERMES_HOME` (default `~/.hermes`) through deterministic tools in `LIFEOS/HERMES/`: `Observe.ts status|failures|sessions|trace` (the aggregator: sessions, failure classes, end-to-end traces), `Health.ts` (process health: up/degraded/flapping/down/absent, per-channel state), `LogAnalysis.ts [--days N]` (guard audit trail: hot rules, retry loops, taint findings) and `Mount.ts --check` (identity/config drift, report-only). Diagnosis mutates nothing: no config writes, no restarts, no cron edits. The Update intent is the one place the sidecar changes. Fixes route through `Policy.ts` + `Mount.ts` (the mount owns config), never hand-edits.
## Ideal State
- Every answer about the sidecar is grounded in its own records through the `LIFEOS/HERMES/` tools, and success is judged from traces, never from an execution status.
- Whether sessions actually load the LifeOS soul is always answered, and a blocked soul leads any report it appears in.
- Every failure or fix names its owner (`Policy.ts` or soul sources plus a re-mount, the approval allowlist, or upstream Hermes) and the sidecar is never mutated by a diagnosis.
## Intent Routing