Skillv1.0.1

ClawScan security

elite memory skill · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousMar 11, 2026, 6:50 AM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill mostly matches a memory-sync tool, but there are inconsistencies (missing referenced Node scripts and mismatched requirement declarations) and a couple of design choices you should verify before installing.
Guidance: This skill appears to be a local memory manager that writes daily memory files and can push them to a GitHub repo and notify a Feishu user. Before installing: 1) Inspect the package contents — SKILL.md references Node scripts (init.mjs, analyze.mjs, sync.mjs, status.mjs) that are not included; ask the publisher why they are missing or obtain the complete source. 2) Confirm you actually need 'node' on PATH — if the implementation is purely shell-based you can remove the node requirement. 3) Understand and control Git behavior: the scripts will git add/commit/push to whatever 'memory' remote you configure — do not configure a remote pointing to a public or sensitive repo until you’ve reviewed which files will be committed. 4) FEISHU_USER_ID is declared required in metadata but described as optional in docs — decide whether you want Feishu notifications and verify how the 'openclaw message' command will behave on your system. 5) If you install, review and run install.sh in a safe environment, and do not add the suggested crontab entries until you’ve tested the scripts manually. If the author can provide the missing Node scripts or a clear explanation for their absence, and clarify the FEISHU_USER_ID requirement, that would reduce concerns.

Review Dimensions

Purpose & Capability: concernThe skill claims a Node-based workflow (SKILL.md shows node scripts: init.mjs, analyze.mjs, sync.mjs, status.mjs) and declares 'node' as a required binary, but the package only includes Bash scripts (analyze-memory.sh, sync-memory-to-github.sh, morning-memory-read.sh). Requiring 'node' and advertising Node scripts without those files is inconsistent and could indicate missing/altered files or sloppy packaging. FEISHU_USER_ID is declared required in metadata but SKILL.md describes it as optional — another mismatch.
Instruction Scope: concernRuntime instructions and the included shell scripts read and write files under ~/.openclaw/workspace (memory files, SESSION-STATE.md, MEMORY.md), run git operations (add/commit/push/pull) and attempt to send notifications via an 'openclaw' command to Feishu using FEISHU_USER_ID. Those actions are coherent with a memory-sync skill, but the SKILL.md instructs users to run Node scripts that are not present. The scripts will push local data to a Git remote you must configure — that can leak personal data to GitHub if misconfigured, so the push behavior should be explicitly reviewed before use.
Install Mechanism: okNo remote downloads or package installs. install.sh simply copies local files into the target workspace and makes script files executable. This is low-risk compared to installs that fetch arbitrary archives from the network.
Credentials: concernThe only declared environment requirement is FEISHU_USER_ID (primaryEnv), which aligns with Feishu notifications, but SKILL.md treats Feishu config as optional. 'git' is required and used; 'node' is declared required but not used by the provided scripts — disproportionate. There's no request for unrelated credentials, but you should verify whether FEISHU_USER_ID must be set for operation and why node is listed.
Persistence & Privilege: okThe skill is not set to always:true and does not request persistent platform-wide privileges. Installation copies files into the user's workspace and suggests adding cron entries; it does not modify other skills or system-wide agent settings.