BEE Belief Extraction Engine
v0.1.1Install and configure BEE — the Belief Extraction Engine for OpenClaw. Gives agents persistent structured memory across sessions. Auto-extracts beliefs at se...
⭐ 0· 445·0 current·0 all-time
byKartik Vashisth@vashkartik
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description describe a persistent belief store and the SKILL.md instructs installing an npm package, configuring a local SQLite DB, and enabling the extension — these are coherent. However the skill relies on an LLM extraction model (anthropic/claude-haiku-4-5) yet the SKILL.md and registry metadata do not declare any required credentials or explain how model credentials are provided; this is an unexplained omission.
Instruction Scope
Instructions are specific: npm install -g the package, edit ~/.openclaw/openclaw.json to enable BEE and set dbPath/agentId, then restart the gateway. The runtime steps reference only the OpenClaw config and a SQLite DB path, which match the stated purpose and do not instruct broad system or network reconnaissance. They do, however, include a direct sqlite3 command to inspect the DB (expected for this purpose).
Install Mechanism
Although there is no automated install spec in the registry, the SKILL.md directs users to run 'npm install -g' (or install from GitHub). Installing a global npm package can execute arbitrary postinstall scripts and will place code on disk; this is a moderate-risk install mechanism. The SKILL.md does not advise verifying the package or reviewing its postinstall behavior.
Credentials
The skill requests no environment variables in registry metadata, but its default configuration uses an external LLM provider (Anthropic). Calling that model normally requires API credentials (or provider configuration) which are not described or declared. Additionally, the skill persists potentially sensitive conversation data indefinitely to a local SQLite DB (vector.db) with no mention of encryption, access controls, or retention — this increases data exposure risk.
Persistence & Privilege
The skill is not always: true and does not request elevated platform privileges. It modifies the user's OpenClaw extension config (~/.openclaw/openclaw.json) and writes a SQLite DB to ~/.openclaw/workspace/state — these are within the extension's stated scope but do grant persistent local storage and long-term access to extracted beliefs, which may contain sensitive content.
What to consider before installing
Before installing: 1) Inspect the package source on the referenced GitHub repo and the npm package page; check for unexpected postinstall scripts or obfuscated code. 2) Verify the package author and recent release history (who published @skysphere-labs/openclaw-bee). 3) Understand how your OpenClaw installation supplies LLM credentials (Anthropic API key or other provider) — the skill uses an extraction model but does not declare required credentials. 4) Consider installing first in an isolated environment/container or non-production agent. 5) Back up ~/.openclaw/openclaw.json and any existing state, and review file permissions for the DB path; determine whether the DB should be encrypted or have a retention policy for sensitive beliefs. 6) If you proceed, review runtime logs (enable debug) and periodically inspect the SQLite DB to ensure only expected data is being stored. If you are not comfortable auditing the package or exposing sensitive conversation data, do not install.Like a lobster shell, security has layers — review code before you run it.
latestvk97817qjd6zaqjd4z6hgezk42d81gdrj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🐝 Clawdis
Binsnpm