Agent Session State
v2.0.0Per-channel session isolation, Write-Ahead Log (WAL) protocol, and working buffer management. Prevents cross-session interference, captures decisions and fac...
⭐ 0· 51·0 current·0 all-time
byRich@richgoodson
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the runtime instructions: the skill defines per-channel session files, a write‑ahead logging protocol, and a working buffer. It asks only that the agent create and write under memory/ (e.g., memory/sessions, memory/working-buffer.md), which aligns with the stated goal.
Instruction Scope
Instructions stay within the stated domain (reading/writing session files, working buffer, daily notes, and running 'memory_search'). Two implementation notes: (1) the skill asks the agent to "scan every message" for triggers and to write WAL entries before responding — this is expected but means user content (including potentially sensitive items) will be written to disk automatically; (2) parts are deliberately judgment-based (when to activate working buffer, what counts as 'important') which grants the agent open-ended discretion. Both are operational considerations rather than incoherence.
Install Mechanism
No install spec and no code files (instruction-only). This minimizes installation risk because nothing is downloaded or written during install.
Credentials
The skill requires no environment variables, credentials, or config paths. The declared requirements are minimal and proportional to the purpose.
Persistence & Privilege
The skill instructs the agent to persist session state and WAL entries to disk. 'always' is false and autonomous invocation is the platform default. Persisting conversation content and decisions is expected for this functionality, but it creates a steady on-disk record that could contain sensitive information — review storage permissions, retention, and access controls.
Assessment
This skill is internally consistent and does what it says: keep per-channel session files and a WAL-style working buffer. Before installing, consider the following: (1) Data sensitivity — the WAL and working buffer will store user messages, corrections, decisions, and possibly personally identifiable or secret data; decide what should never be persisted and ensure the agent is configured not to write secrets. (2) Storage controls — place memory/ under an access‑controlled location, enable filesystem permissions, consider encryption at rest, retention policies, and periodic pruning/rotation. (3) Audit & recovery — add logs and periodic integrity checks so you can detect unwanted writes. (4) Operational tuning — the skill uses human judgment for triggers (when to activate the working buffer and what is 'important'); test in a sandbox to tune thresholds and summaries to avoid excessive writes. (5) Integration review — if you plan to combine with other skills (hierarchical-agent-memory, agent-provenance), verify file layout and naming conventions to avoid accidental cross-session reads. If you need stricter guarantees (no disk writes, or redaction of sensitive tokens), modify the workflow or refuse to persist certain message types.Like a lobster shell, security has layers — review code before you run it.
latestvk973kkwhhe76xq7m2k5bppdxe584b3df
License
MIT-0
Free to use, modify, and redistribute. No attribution required.