PARA Memory System
v1.0.0Set up and maintain a 3-layer PARA memory system for OpenClaw agents. Provides durable knowledge persistence across sessions using daily notes, a structured...
⭐ 0· 204·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 behavior: instructions create and maintain a local PARA-style folder structure and daily notes. There are no unrelated env vars, binaries, or installs requested.
Instruction Scope
All runtime instructions are file I/O within the agent workspace (life/, memory/, AGENTS.md). That's coherent for a memory system. Two items to be aware of: (1) templates include the line 'Don't ask permission. Just do it.' which instructs the agent to read files and act without explicit per-action user consent — reasonable for internal memory reads but a potential privacy/consent policy decision for the user; (2) it recommends automatic nightly consolidation (cron or 'heartbeats'), so the agent is expected to modify files autonomously unless that behavior is limited by the platform. There are no instructions to call external endpoints or exfiltrate data.
Install Mechanism
Instruction-only skill with no install spec and no code files. Nothing is written to disk by an installer — the only writes are the file operations the skill asks the agent to perform at runtime.
Credentials
The skill requests no environment variables, credentials, or config paths. All required resources are local file paths inside the workspace and templates included in the skill.
Persistence & Privilege
always:false (no forced global inclusion). The skill recommends autonomous actions (nightly consolidation / heartbeats / cron). Autonomous invocation is platform-default and not inherently problematic, but you should decide whether you want the agent to run these consolidations automatically or only when manually triggered.
Assessment
This skill is coherent and does what it says: manage a local PARA memory inside the agent workspace. Before installing, consider: 1) Inspect the workspace you will use for these files — don't point the skill at folders that contain secrets, keys, or other sensitive material. 2) Review and possibly edit the templates (AGENTS.md, tacit, daily) to remove or reword 'Don't ask permission. Just do it.' if you want explicit consent before writes. 3) Decide whether you want automatic nightly consolidation (cron/heartbeats) — if not, run consolidation manually. 4) Ensure file permissions/backups are acceptable (daily notes are stored indefinitely per the docs). 5) Confirm your platform's agent sandboxing so the agent cannot read files outside the intended workspace. If you want additional assurance, test in an isolated project directory first.Like a lobster shell, security has layers — review code before you run it.
latestvk978d9m4vvj6qx76tyz0nhsqsd82q0mjmemoryvk978d9m4vvj6qx76tyz0nhsqsd82q0mjopenclawvk978d9m4vvj6qx76tyz0nhsqsd82q0mjparavk978d9m4vvj6qx76tyz0nhsqsd82q0mjproductivityvk978d9m4vvj6qx76tyz0nhsqsd82q0mj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.