ClawHub

MemPalace

v1.0.0

Integración con MemPalace para gestión de memoria semántica persistente. Use when you need to search, add, or query memories stored in a MemPalace palace. Su...

⭐ 0· 76·0 current·0 all-time
by@anderotxoa
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Crypto
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description describe semantic memory management and the shipped scripts implement search, add, status, and KG queries against a ChromaDB-backed 'palace' — the requested capabilities align with the stated purpose.
ℹ
Instruction Scope
SKILL.md and the scripts restrict actions to a local palace path (default ~/.mempalace/palace) and to ChromaDB operations. One repeated pattern: scripts insert '/root/.openclaw/workspace/mempalace' into sys.path to import a mempalace package that is not included in the bundle; this is a fragile dependency but not itself a sign of malicious behavior.
ℹ
Install Mechanism
No install spec (instruction-only + scripts). The scripts rely on external Python packages (chromadb and a mempalace package) but do not install them. This is low risk but means the runtime environment must already provide these dependencies.
✓
Credentials
The skill declares no environment variables, credentials, or config paths. The scripts operate on a local path and accept a --palace-path override; there are no requests for unrelated secrets or external service keys.
✓
Persistence & Privilege
always is false and the skill does not attempt to modify other skills or global agent settings. It reads and writes local ChromaDB storage (expected for its function).
Assessment
This skill appears coherent with its stated purpose, but before installing: (1) ensure you trust the mempalace package that will be imported at /root/.openclaw/workspace/mempalace (inspect its code if present), (2) confirm chromadb and any Python deps are installed in the runtime environment, and (3) be aware the scripts read/write the local directory (~/.mempalace/palace or a custom --palace-path). If you are unsure, run these scripts in an isolated environment (container or VM) and inspect the mempalace package to ensure it doesn't perform unexpected network/exfiltration actions.

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

latestvk970pe9jeh4sj6tw0mdxqmvk1584e376

License

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

Comments