SwarmRecall

Use SwarmRecall when an AI agent needs persistent memory, a knowledge graph, learnings, a skill registry, shared pools, or background dream consolidation acr...

This skill appears coherent for providing agent memory and a knowledge graph, but consider the following before installing: - Privacy: Data stored via the skill is sent to https://swarmrecall-api.onrender.com and kept on SwarmRecall servers. Do not store sensitive personal or secret information unless you understand and accept that remote storage. - API keys: Create a dedicated SWARMRECALL_API_KEY per agent (do not share keys across agents). Treat the key like a secret and rotate/revoke it if you suspect misuse. - Install source: The CLI is installed via npm (@swarmrecall/cli). Verify the package on npmjs.com and the linked GitHub repo (owner, recent activity, and npm publisher) before installing globally. - Local vs remote: If you are privacy-sensitive, prefer running the local stdio MCP server (swarmrecall mcp) under your control rather than pointing an agent to the hosted endpoint, or ask about a self-hosting option. - Config file: The CLI will create ~/.config/swarmrecall/config.json if you use register --save. Ensure you do not check that file into source control. - Audit and testing: After install, run the provided smoke prompts and inspect outbound traffic if possible; if anything unexpected appears (API URLs different from documented, keys returned in clear, or requests to unknown domains), revoke the key and uninstall. If you want deeper assurance, review the CLI's published source code (the GitHub repo) and the package's npm publisher metadata before installing.

Type: OpenClaw Skill Name: swarmrecall Version: 1.2.0 The SwarmRecall skill provides a comprehensive suite for persistent agent memory, knowledge graphing, and background 'dream' consolidation via a third-party API (swarmrecall-api.onrender.com). While the functionality is transparently documented and includes security-conscious instructions regarding user consent and API key management, the skill possesses high-risk capabilities including the transmission of conversational history to an external endpoint and local file system access for configuration (~/.config/swarmrecall/config.json). Per the analysis criteria, these risky capabilities—though plausibly required for the stated purpose—warrant a suspicious classification in the absence of clear malicious intent.