Skillv0.1.3

ClawScan security

maasv Memory · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousFeb 20, 2026, 7:57 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's purpose (local long-term memory) is plausible and its runtime instructions mostly match that purpose, but the registry metadata omits the API keys and config requirements the SKILL.md tells you to create and the skill instructs modifying agent config and capturing conversations — these mismatches deserve attention before installing.
Guidance: This skill appears to be what it says (a local memory backend) but the registry metadata under-reports required credentials and configuration. Before installing: 1) Decide whether you will use cloud LLM/embedding providers (OpenAI/Anthropic/Voyage) — those require API keys and will cause data to leave your machine; prefer Ollama/local models for fully local operation. 2) Inspect the maasv GitHub and the @maasv/openclaw-memory npm package source to confirm you trust the maintainers. 3) Back up and secure the SQLite database the server creates and confirm where it will be stored. 4) Be aware the plugin will capture conversation summaries and inject memories back into agent context — test with non-sensitive data first and confirm delete/forget workflows work as you expect. 5) Because the registry omitted required env vars, a careful manual review of .env.example and any plugin docs is recommended before providing secrets.

Review Dimensions

Purpose & Capability: noteThe name/description (long-term, semantic/keyword/graph memory) aligns with the instructions to run a local maasv server and install an OpenClaw memory plugin. Requesting LLM and embedding providers is consistent with entity extraction and semantic search. However, the registry lists no required environment variables or primary credential while the SKILL.md clearly requires multiple API keys/configuration — a metadata mismatch.
Instruction Scope: noteSKILL.md gives explicit, bounded runtime steps: install the maasv Python server, fill a .env with provider API keys, run maasv-server, install the @maasv/openclaw-memory plugin, and edit ~/.openclaw/openclaw.json to point memory slot at the local server. The instructions will cause the agent to send conversation summaries to the local server (autoCapture) and to inject memories back into context (autoRecall). These behaviors are expected for a memory backend but you should be aware that conversation content will be written to a local SQLite DB and that external LLM/embedding providers (if used) will receive data.
Install Mechanism: okThis is an instruction-only skill (no install spec, no code files). The install steps are manual: pip install maasv[...], run maasv-server, and openclaw plugins install @maasv/openclaw-memory. Because nothing in the registry will be automatically downloaded or executed by the platform, install risk is limited to the third-party packages you choose to install yourself. Review maasv and the npm plugin source before running pip/npm installs.
Credentials: concernThe SKILL.md requires multiple environment variables/API keys (MAASV_LLM_PROVIDER, MAASV_OPENAI_API_KEY, MAASV_ANTHROPIC_API_KEY, MAASV_EMBED_PROVIDER, MAASV_VOYAGE_API_KEY, optional MAASV_API_KEY) which are proportionate to the described functionality. The problem: the skill registry metadata lists no required env vars or primary credential, so the registry under-reports the secrets the user must supply. That mismatch makes it easy to overlook that you must provide potentially sensitive API keys or choose a fully-local option (e.g., Ollama) to avoid cloud calls.
Persistence & Privilege: notealways is false (good). The skill instructs editing the agent's config (~/.openclaw/openclaw.json) to register the memory plugin — this is normal for enabling a memory backend but is a persistent change to your agent setup. The maasv server will persist conversations and extracted entities to a local SQLite file; ensure you understand where that DB lives and how to secure or delete it (the SKILL.md mentions memory_forget for deletion).