Give Hermes a replay habit: receipts instead of re-reasoning.
Vendor the Reelier skill into your agent's skills directory, record the job once through the wrap proxy, and replay it deterministically with a receipt every run.
How capture works on Hermes
Plainly: Hermes is not on reelier scan's transcript-source list — scan reads a fixed set of agent history dirs (~/.claude/projects, ~/.codex/sessions, ~/.codeium/windsurf, ~/.openclaw) and Hermes isn't one of them, so there is no history-scan path here to oversell.
Capture on Hermes is the recording proxy: front the MCP server(s) your agent's job uses with reelier mcp --wrap, run the job once, and the full trace lands in .reelier/traces/. Wrap captures lossless traces (tool annotations included) — scan-from-history is a reconstruction; wrap is the recording.
The installed skill supplies the judgment layer: when to replay instead of re-reason, compile only from a run that actually happened, report the receipt, never report an unseen pass.
Wire it up
curl -fsSL --create-dirs https://raw.githubusercontent.com/seldonframe/reelier/main/clawhub/reelier/SKILL.md \
-o skills/reelier/SKILL.mdHermes's own installer pulls skills from public registries (skills.sh, ClawHub), but neither lists Reelier yet as of 2026-07-21 — skills.sh search returns nothing and the ClawHub listing is pending publication — so a registry install doesn't resolve yet. Vendor the file until one lists it.
npx -y reelier mcp --wrap "npx -y @yourco/mcp-server"
npx -y reelier compile .reelier/traces/<name>.jsonl -o my-job.skill.mdreelier mcp fronts your real MCP server and records losslessly to .reelier/traces/. Multiple --wrap flags front multiple servers; only local stdio servers can be wrapped.
First receipt in 60 seconds
- Vendor the skill from the repo (block above) — the when-to-replay rules and honesty guards.
- Record the job once through the wrap proxy (block above), then compile the trace into
my-job.skill.md. - Replay deterministically: 0 LLM tokens, every step asserted, receipt written to
.reelier/runs/.npx -y reelier run my-job.skill.md - From the second run on: exit 0 SAME, exit 1 DRIFTED — with the failing assertion as the why, captured verbatim.
npx -y reelier diff my-job
A real receipt
Verbatim output of a portfolio replay, run with the published CLI (npx -y reelier@latest, resolved to reelier@0.12.1) on 2026-07-21. The run record confirms passed: true and 0 LLM tokens. Nothing platform-specific about it — the same skill file replays from any shell, including yours:
=== registry-latest === ✓ Step 1 — Latest dist-tag from the registry [passed] 152ms PASSED: 1/1 steps ok, 0 failed, 152ms total
Replay it yourself: npx -y reelier@latest run examples/portfolio/registry-latest.skill.md (from a checkout of the repo — read-only, no account, no key).
FAQ
Why doesn't reelier scan see Hermes sessions?
Scan reads a deliberate, fixed list of transcript directories, and Hermes isn't on it yet. Adding a source is a one-line entry in scan.ts plus, if the transcript schema differs, a parser branch — until then, the wrap proxy is the capture path, and it's the higher-fidelity one anyway.
Can Hermes call Reelier's tools over MCP?
If your Hermes setup speaks MCP over stdio, point a server entry at npx -y reelier serve — the same route the repo documents for Codex and other MCP-capable agents. That exposes reelier_scan, reelier_from_session, reelier_replay, reelier_diff and reelier_push as tools.
What can't Reelier replay?
Reelier replays deterministic tool calls: MCP tool calls and its own http.get/http.post builtins. It cannot replay file edits, shell commands, reads and searches, subagent dispatch, or anything non-deterministic. An edit-heavy coding session honestly reports nothing replayable — an empty result, not an error.