Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Mempalace Memory
v1.1.0基于MemPalace融合SuperMem增强层，提供自动hook注入、多样性重排、相似度去重和高效上下文记忆管理。
⭐ 0· 54·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
medium confidencePurpose & Capability
The name/description (memory retrieval + MMR/dedup) aligns with the included scripts (search, dedup, mmr, strip, ChromaDB bridge). However the code hardcodes paths tied to a specific developer environment (/Users/mars/Library/Python/3.9/bin/mempalace, sys.path insert to /Users/mars/...site-packages) and references local storage locations (~/.mempalace, ~/.super-mem, ~/.openclaw) and a local Ollama endpoint. Those hardcoded environment assumptions are not justified by the skill metadata (which declares no required binaries or env) and are likely to fail or cause unintended file access on other machines.
Instruction Scope
SKILL.md instructs running the packaged Python scripts and registering a hook under ~/.openclaw/hooks/... and the scripts do exactly that: they call a local mempalace CLI, access local ChromaDB stores, read/inspect files (source file paths, identity file, workspaces) and call a local embeddings endpoint (http://localhost:11434). The instructions and code also reference creating/reading ~/.mempalace/identity.txt and deleting memories (ChromaDB). While these operations are consistent with a memory skill, they grant the skill broad local file and DB access and assume specific local services; the instructions do not ask for explicit confirmation or provide a safe fallback for environments where these paths/services are absent.
Install Mechanism
There is no formal install spec (instruction-only), which limits automatic risk from downloads. But the skill ships executable Python scripts that will be executed by the agent (via /usr/bin/python3). Those scripts depend on external binaries/services (mempalace CLI at a hardcoded path, Ollama embedding endpoint, chromadb/persistent client). Because the skill contains runnable code, it will execute with the agent's local file and network privileges if invoked — review the code before running.
Credentials
The skill declares no environment variables or credentials, which is appropriate, but the code inspects and manipulates local files and local ChromaDB stores (e.g., ~/.mempalace/palace, ~/.super-mem/chroma, ~/.openclaw/workspace). It also embeds an explicit reference to a developer's Python binary location and site-packages. These file-system accesses are broad relative to the metadata (no explicit permission/consent steps) and could expose or modify local data. The scripts include credential-detection/filtering code (masking patterns) which indicates they may process data that contains secrets — that makes the local data access capability more sensitive.
Persistence & Privilege
The skill is not forced-always and does not request elevated platform privileges. However SKILL.md expects a hook file at ~/.openclaw/hooks/mempalace-recall/handler.ts to be installed/registered for automatic invocation; that implies persistent integration with the agent if you or the integrator place that file. The skill itself does not include an install step to create system-wide effects, but following the document will involve adding a persistent hook and allowing scripts to access local storages.
What to consider before installing
This skill is plausibly a local-memory enhancement, but it makes strong assumptions about the environment (hardcoded /Users/mars paths, Python site-packages, local Ollama at http://localhost:11434, and local ChromaDB paths). Before installing or activating: 1) Review the three Python scripts line-by-line (they will execute on your machine and access local files and DBs). 2) Replace or parameterize hardcoded paths (MEMPALACE_CLI, sys.path inserts) to match your system or remove them. 3) Ensure Ollama/chroma services are intended and secured (they are contacted locally via curl/subprocess). 4) Back up any local ~/.mempalace or ~/.super-mem data you care about; the scripts include deletion/forget functionality. 5) Prefer running first in a sandbox or test account, and only register the hook under ~/.openclaw/hooks when you trust the code. If you want, provide the full remainder of the truncated mempalace_cli.py (credential filter section) so I can re-evaluate any missing behaviors.Like a lobster shell, security has layers — review code before you run it.
latestvk9700v0yps9fgqf8ndwbva2acs84f1gs
License
MIT-0
Free to use, modify, and redistribute. No attribution required.