Adaptive Memory
v1.0.0Hierarchical memory management for AI agents across sessions. Maintains three layers — daily notes (raw logs), active context (working memory), and long-term...
⭐ 0· 43·0 current·0 all-time
byYoshikazu Terashi@yozu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (hierarchical memory) matches what is provided: SKILL.md describes daily notes, active context, long-term memory and distillation workflows, and the init script creates the described files and directories. No unrelated credentials, binaries, or services are requested.
Instruction Scope
Instructions direct the agent to read/write files under the workspace (memory/*.md, MEMORY.md, pending_tasks.json, heartbeat-state.json). This is appropriate for a local memory manager. The docs caution against storing secrets and include an example reference path (~/.secrets/service.env) — the skill does not instruct reading external secret stores, but reviewers should be aware the agent will be instructed to read workspace files (so sensitive data should not be placed there).
Install Mechanism
No install spec; the only executable artifact is a small bash init script (scripts/init_memory.sh) that creates folders/files. Nothing is downloaded or extracted from external URLs and no packages are installed.
Credentials
The skill declares no required environment variables, credentials, or config paths. The SKILL.md's single example path for secrets is advisory (to avoid storing secrets in memory files) and is not a requirement to provide any secret.
Persistence & Privilege
Skill is not always-enabled and does not request elevated/persistent platform privileges. It creates and updates files only within the provided workspace (init script uses a workspace_dir argument or current directory). It does not modify other skills or system-wide agent settings.
Assessment
This skill appears internally consistent and implements a local file-based memory system. Before installing, ensure you: (1) do not place passwords, API keys, or other secrets in the workspace memory files (the docs explicitly advise against that), (2) restrict filesystem access to the workspace so other actors can't read sensitive notes, and (3) decide whether you want an autonomous agent reading/writing these files — the skill instructs the agent to load context from disk at session start. If you need secrets referenced in memory, store them in a secure secret store outside the workspace and avoid putting secret contents into MEMORY.md or daily notes.Like a lobster shell, security has layers — review code before you run it.
latestvk971ckjtr6rsmxhfahhx84az8d8409d1
License
MIT-0
Free to use, modify, and redistribute. No attribution required.