ClawHub

WAL Memory

v1.0.2

Session crash and compaction recovery using a two-file WAL (Write-Ahead Log) system. Use when setting up persistent memory for an OpenClaw agent that needs t...

⭐ 0· 296·0 current·0 all-time
by@maikunari
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (WAL memory for session recovery) aligns with the delivered artifacts: a small Node script that appends timestamped entries to ~/clawd/STATE.log and a GOALS template. No unrelated binaries, env vars, or services are requested.
✓
Instruction Scope
SKILL.md directs local operations only: copying script to ~/clawd/scripts, creating ~/clawd/memory/GOALS.md, reading/tailing local STATE.log and memory files, and adding heartbeat logging. These actions match the stated recovery workflow and do not instruct reading unrelated system state or contacting external endpoints.
✓
Install Mechanism
No install spec; this is instruction-only with one small JS script (no downloads or external packages). The only runtime requirement is Node.js being on PATH, which is consistent with the script.
✓
Credentials
The skill does not request environment variables, credentials, or config paths. The only implicit requirement is write access to ~/clawd/STATE.log when the script is installed and run, which is reasonable for a local logger.
✓
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent platform privileges, modify other skills, or alter system-wide agent settings. Its persistence is limited to creating/rotating a local log file.
Assessment
This skill appears to do exactly what it claims: append timestamped local log entries for session recovery. Before installing: (1) Only run the script from a trusted source — the package metadata has no homepage and a single owner ID, so verify the file if you care about provenance. (2) Do not log passwords, API keys, or other secrets — the log file is plaintext and the README explicitly warns about this. (3) Add ~/clawd/STATE.log to .gitignore as recommended and restrict file permissions (e.g., chmod 600) or consider encrypting the logfile if you will store sensitive operational details. (4) Consider a retention/rotation policy beyond simple rename for long-term storage and ensure backups (if any) are secure.

Like a lobster shell, security has layers — review code before you run it.

agentsvk97a49r6mme10xsberm7vb6xhs827kswlatestvk97a49r6mme10xsberm7vb6xhs827kswmemoryvk97a49r6mme10xsberm7vb6xhs827kswrecoveryvk97a49r6mme10xsberm7vb6xhs827ksw

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments