Whatsapp Memory
v1.0.0Maintain separate memory contexts per WhatsApp conversation — both groups and direct messages (DMs). Use when: tracking what was discussed with a specific pe...
⭐ 0· 45·0 current·0 all-time
byNetanel Abergel@netanel-abergel
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (per-conversation WhatsApp memory) aligns with the instructions: creating per-chat directories, writing context/decisions/notes files, reading them back, and searching across them. The operations (file I/O, tail/grep, small python snippets) are appropriate for a local, file-backed memory store. Minor note: the SKILL.md relies on common system utilities (python3, grep, tail, date) even though the registry metadata lists no required binaries.
Instruction Scope
Instructions stay within the stated purpose (read/write conversation-specific files and use them before responding). They do tell the agent to run these steps on every incoming message (injecting context before replying) which is expected for a memory skill, but this grants the skill broad read access to all conversation memory files in the workspace. The SKILL.md also includes explicit 'never log secrets' guidance but does not enforce redaction or retention — that's an operational concern the user should address.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That is the lowest-risk mechanism and consistent with the skill's purpose.
Credentials
The skill declares no environment variables or credentials and does not request unrelated secrets. It uses $HOME/.openclaw/workspace as its storage location which is proportionate for local memory. Note: runtime relies on python3 and standard Unix utilities; these are not declared but are common.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent platform-wide privileges. It persists data to its own workspace path only and does not instruct modifying other skills or system-wide settings.
Assessment
This skill appears to be what it says: a local, file-based per-conversation memory for WhatsApp. Before installing or enabling it, consider: 1) Privacy and encryption — the skill writes chat content to disk under $HOME/.openclaw/workspace/memory/whatsapp; ensure that directory has strict filesystem permissions (e.g., chmod 700) and consider encrypting backups if messages are sensitive. 2) Secrets risk — the instructions say 'never log secrets' but do not enforce it; implement redaction/filters or a retention policy to avoid accidentally storing credentials or private media. 3) Runtime dependencies — the scripts use python3, grep, tail, date and expect a POSIX shell; verify these are available in your agent environment. 4) Sanitization/safety — the ID sanitization replaces '@', '.', '+' but may not remove other unsafe characters (e.g., slashes); confirm incoming IDs are validated to avoid file-path surprises. 5) Scope of access — the skill will read/write all files under its memory path and will load recent context on every incoming message; if multiple users or teams share the same machine, consider isolating the workspace. If these concerns are acceptable and you trust local disk storage, the skill is coherent and reasonable to use.Like a lobster shell, security has layers — review code before you run it.
latestvk978fbtr1bspssvr9c6rcney6s8405e5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.