Memory Stack Core
v1.0.0Core memory resilience layer: WAL (Write-Ahead Log), Working Buffer, and three-layer memory integration. Prevents context loss during compaction and ensures...
⭐ 0· 68·0 current·0 all-time
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 delivered artifacts: SKILL.md describes a WAL, working buffer, daily logs and recovery; the included scripts/run.py implements file-backed WAL and buffer, reads a local config (memory-stack-config.json), and exposes the declared tool-like actions (wal_write, wal_read, buffer_write, buffer_read, memory_health, wal-auto). No unrelated binaries, env vars, or services are requested.
Instruction Scope
Instructions and script intentionally read and write files under the workspace/memory directory (wal.jsonl, working-buffer.md, daily logs). This is consistent with the purpose, but the automatic 'auto_capture' behavior scans every human message for paths, URLs, decisions, preferences, values, and corrections and appends matches to the WAL — meaning any sensitive specifics typed by users (passwords, API keys, tokens, paths, URLs) can be persisted to disk. That behavior is expected for this purpose but is a privacy/sensitive-data risk and should be configured/limited if needed.
Install Mechanism
No install spec is provided (instruction-only + included script). Nothing is downloaded or executed from external URLs; the included Python script is the only code. This is low-risk from an install mechanism perspective.
Credentials
The skill requests no environment variables, no external credentials, and no config paths outside the workspace. Its file I/O is limited to workspace/memory and a workspace config file — proportionate to the stated purpose.
Persistence & Privilege
always:false (no forced inclusion). The skill is invokable/autonomous by default (normal), and its core privilege is persistent local storage in the workspace. That persistence is necessary for the feature but increases the blast radius if the workspace is backed up, uploaded, or under version control. The skill does not modify other skills or system-wide agent settings.
Assessment
This skill does what it says (local WAL + working buffer) and contains no network exfiltration or secret-env requirements, but it will persist specifics from user messages to files in your workspace by default. Before installing: (1) decide whether you want automatic capture enabled and, if not, disable auto_capture in memory-stack-config.json; (2) ensure the memory/ directory is excluded from backups and version control (add to .gitignore) and set restrictive file permissions; (3) lower max_entries / max_size_mb or enable rotation to limit retained data; (4) test in an isolated workspace first to confirm behavior; (5) avoid pasting secrets (API keys, passwords) into chats that will be captured, or add filtering rules. If you need stricter guarantees (encryption, secure storage, remote retention policies), consider hardening or rejecting this skill until those controls exist.Like a lobster shell, security has layers — review code before you run it.
compactionvk977723fe98qvc8at14315ww3s840xnacorevk977723fe98qvc8at14315ww3s840xnalatestvk977723fe98qvc8at14315ww3s840xnamemoryvk977723fe98qvc8at14315ww3s840xnapersistencevk977723fe98qvc8at14315ww3s840xna
License
MIT-0
Free to use, modify, and redistribute. No attribution required.