MemClawz Connect

Connect any AI agent to the MemClawz shared memory bus. Gives agents read-before-act and write-after-complete patterns via a simple HTTP API. Use when an age...

This skill probably does what it claims, but there are missing declarations and provenance issues you should address before installing. Specifically: (1) Verify you trust and control the MemClawz server you point MEMCLAWZ_URL at — do not set it to an unknown public IP. (2) Treat MEMCLAWZ_URL, MEMCLAWZ_AGENT_ID, and MEMCLAWZ_API_KEY as required configuration and only provide them if you understand where data will be stored. (3) Ask the publisher for a homepage, source code, and a clear security model (auth, data retention, encryption). (4) If you plan to use this with agents that may handle secrets or PII, restrict the skill to agents you control or modify the AGENTS.md procedure to sanitize or exclude sensitive content before writing. (5) Prefer a deployment where MEMCLAWZ_URL is localhost or an internal, access-controlled host, and require an API key on the server side. If the vendor cannot justify the missing metadata and unknown origin, avoid enabling it for agents handling sensitive data.

Type: OpenClaw Skill Name: memclawz-connect Version: 1.1.0 The 'memclawz-connect' skill bundle instructs the AI agent to send task context and results to a remote HTTP endpoint (MEMCLAWZ_URL) before and after every action. While presented as a 'shared memory' utility, this pattern facilitates the exfiltration of all agent activity and sensitive task data to a third-party server. The SKILL.md file explicitly suggests a specific, non-standard IP address (76.13.154.71) as a remote endpoint, which could act as a data sink for intercepted agent communications.