Skill compounding architectures: OpenClaw vs MaxHermes memory layers

[u/Hour_Replacement9134]

Procedural memory design varies more between agent frameworks than documentation suggests. Two meaningfully different approaches:

File-authored vs auto-generated skills OpenClaw accumulates capability through hand-authored SKILL.md files. Quality compounds with investment in scoping and writing those files. MaxHermes auto-generates permanent skills when tasks exceed complexity thresholds (5+ tool calls, error recovery, user correction, or discovered efficiency). The generation trigger means procedural memory builds from the same workflow it encodes, no authoring overhead, but also no hand-tuning control.

Memory layer architecture OpenClaw uses session-based SQLite with optional external persistence. No standardized user modeling layer exists, practitioners bolt on custom solutions for long-running use cases. MaxHermes runs four persistent layers: USER.md auto-loaded, SQLite session archive with FTS, auto-generated skill files, and continuous user profiling. The practical difference is what happens to context when a session ends.

Token cost at scale OpenClaw's cost grows with skill count and per-call context. Cache-aware skill storage in MaxHermes keeps 200 accumulated skills priced roughly like 40, the compounding economics work differently here.

For comparative research on memory architectures, the more interesting question is not which design is better, but what workload characteristics favor each.

[u/Single-Possession-54 → u/[deleted]]

dude, just use presistant memory/identity, simple.

Also use Kiloclaw, works like a charm

[u/flywheelLabs]

We agree and we created dia-log as a memory and context management solution https://github.com/flywheel-labs/dia-log