Skills/ClawHub/memory-health-check

memory-health-check@1.0.0

VERIFIED· install only

Publisher claims: "Performs a 6-dimension memory health check assessing integrity, freshness, bloat, orphans, duplicates, and coverage with optional auto-repair." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry ClawHubPublisher chongjie-ran · publishing for 217 daysInstalls 865Last detonated 11 h ago
$clawhub install memory-health-check
WatchReport an issue

Coverage

Bundled scripts ran with no arguments; no agent task scenario for this bundle.
Tested
8 of 14 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 (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-19 and scored it 84/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 · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments
0.1sprocessbundled script run in the sandbox with no arguments
0.4sfilesystemwrote ~/.openclaw/workspace/memory/health-reports/health-report-2026-11-19_14-26.json
0.4sprocessbundled script run in the sandbox with no arguments
0.5sprocessexited 1: ModuleNotFoundError: No module named 'yaml'
0.5sprocessbundled script run in the sandbox with no arguments
0.6sprocessexited 1: ModuleNotFoundError: No module named 'yaml'
0.6sprocessbundled script run in the sandbox with no arguments
0.6sprocessexited 1: ModuleNotFoundError: No module named 'yaml'
0.6sprocessbundled script run in the sandbox with no arguments
0.7sprocessexec /usr/bin/dirname
0.7sprocessexited 1: ModuleNotFoundError: No module named 'yaml'
0.7sprocessbundled script run in the sandbox with no arguments
0.8sprocessexited 1: ModuleNotFoundError: No module named 'yaml'
0.8sprocessbundled script run in the sandbox with no arguments
0.9sprocessexited 1: ModuleNotFoundError: No module named 'yaml'
0.9sprocess8 of 14 bundled scripts run with no arguments (the rest were not run: per-bundle cap)
0.9sprocessscript backend runs setup only
0.9sprocessscript backend runs setup only
0.9sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedscripts/generate_report.py:42 · Python subprocess execution detectedresult = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

No other findings across 4,711 lines in 25 files.

Cost to the agent

Instructions loaded
≈566 tok
1 file · 25 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.

memory-health-check@1.0.0 safety verdict: Verified (install only) — KillerSkills