self-evolving-memory
v1.0.0Orchestrate the OpenClaw memory system so it actually runs reliably in practice. Use when the task involves capturing user preferences, current task state, c...
⭐ 0· 56·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
The skill's name/description (memory orchestration) matches the actual content: templates, routing rules, and a setup script that copies templates and checks embedding config. It does not request unrelated credentials or binaries.
Instruction Scope
SKILL.md and the references confine actions to the user's workspace (creating/templating memory files), reading openclaw.json for memorySearch configuration, and optionally using embedding providers for semantic search. There are no instructions to read arbitrary user files, shell history, or exfiltrate data.
Install Mechanism
There is no install spec; the only executable file is scripts/setup.sh which copies templates and checks configuration (benign). The documentation suggests running external commands to install Ollama (curl | sh) and pulling models; that guidance is optional and carries the usual caution about running remote install scripts.
Credentials
The skill itself requires no environment variables or credentials. Documentation explains how to configure embedding backends which may require API keys (OpenAI or remote Ollama endpoints). Requesting embedding API keys is proportionate to optional embedding features, but users should avoid storing secrets in plain templates or unsecured workspace files.
Persistence & Privilege
The skill is not always-enabled and is user-invocable. It does not modify other skills or system-wide settings beyond copying templates into the user-specified workspace and reading ~/.openclaw/openclaw.json to check config — behavior consistent with its purpose.
Assessment
This skill is coherent and appears to do what it claims: create and manage memory templates and provide routing rules. Before installing or running the setup script, review the templates and scripts (they only copy files and read ~/.openclaw/openclaw.json). Do not run suggested remote install commands (e.g., curl | sh) unless you trust the source; prefer installing embedding backends (like Ollama) via official instructions. Avoid putting API keys or secrets into workspace files; store them in secure config or environment variables per your platform's best practices. If you enable remote embedding providers, verify the remote baseUrl and apiKey targets are trusted. Finally, back up any existing memory files in your workspace before running the setup so nothing is accidentally lost.Like a lobster shell, security has layers — review code before you run it.
latestvk97e39n0gqgfyh1yw02hbaz90h844692
License
MIT-0
Free to use, modify, and redistribute. No attribution required.