Skills/ClawHub/soul-memory

soul-memory@3.5.13

VERIFIED· install only

Publisher claims: "Intelligent memory management system v3.5.13 - 修復 heartbeat-trigger.py 改用上次 heartbeat 到現在的增量窗口抓取 important context,避免固定 3 小時窗口遺漏與重掃。" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher kingofqin2026 · publishing for 213 daysInstalls 2,109Last detonated 40 min ago
$clawhub install soul-memory
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 8 of 36 bundled scripts run with no arguments (the rest were not run: per-bundle cap), with decoy credentials in the environment · every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-21 and scored it 81/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 3 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.0sprocessexited 2: ./install.sh: line 372: syntax error near unexpected token `('
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessexited 1: PermissionError: [Errno 13] Permission denied: '/root/.openclaw/workspace/memory'
0.1sprocessbundled script run in the sandbox with no arguments
0.2sprocessexited 1: Error: Could not import SoulMemorySystem
0.2sprocessbundled script run in the sandbox with no arguments
0.4sprocessbundled script run in the sandbox with no arguments
0.5sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.5sprocessbundled script run in the sandbox with no arguments
0.7sfilesystemread ~/.openclaw/agents/main/sessions/sessions.json outside project
0.7sprocessbundled script run in the sandbox with no arguments
0.8sfilesystemread ~/.openclaw/agents/main/sessions/sessions.json outside project
0.8sprocessbundled script run in the sandbox with no arguments
0.8sprocess8 of 36 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.8sprocessscript backend runs setup only
0.8sprocessscript backend runs setup only
0.8sprocesssecond launch, clock +45 days, CI unset
0.9sprocessexited 2: ./install.sh: line 372: syntax error near unexpected token `('

Static findings

MEDIUM
Python subprocess execution detectedmodules/version_control.py:47 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
File permission modification commandinstall.sh:218 · File permission modification command — agent changes file ownership/permissionschmod +x "$INDEX_SCRIPT"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
Destructive file system command detectedtests/test_memory_strengthening.py:16 · Destructive file system command detectedrm -rf /tmp/nopeFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
File permission modification commandinstall.sh:471 · File permission modification command — agent changes file ownership/permissionschmod +x "$DAILY_SCRIPT"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈2,201 tok
1 file · 70 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.