openclaw-siliconflow-memory
v1.0.0Configure OpenClaw semantic memory to use SiliconFlow embeddings through the OpenAI-compatible API, especially `BAAI/bge-m3`. Use when enabling or repairing...
⭐ 0· 82·0 current·0 all-time
byWeiHan@otweihan
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the SKILL.md only covers switching OpenClaw's memory_search to SiliconFlow (OpenAI-compatible endpoint), setting model to BAAI/bge-m3, adding extraPaths, and validating indexing—these are the exact config and CLI actions described.
Instruction Scope
Instructions are scoped to reading and patching OpenClaw config (gateway config.get/patch), adding curated local Markdown paths, running OpenClaw memory status/index/search, and troubleshooting. There is no instruction to read unrelated system files or to exfiltrate data. It does recommend storing an API key in the config (see environment_proportionality note).
Install Mechanism
This is instruction-only with no install spec and no code files — nothing will be downloaded or written by the skill itself. Low installation risk.
Credentials
The skill declares no required env vars, but it explicitly instructs setting remote.apiKey in OpenClaw config. Requesting the SiliconFlow API key is proportionate to the task, but storing API keys in config can expose them to other users/tools or source control; the SKILL.md does not advise a secure storage method.
Persistence & Privilege
always:false and no install means the skill has no forced persistent presence. Note: agent autonomous invocation is allowed by platform default (not a red flag alone). If you place an API key in OpenClaw config, that credential will be accessible to components that can read that config, so consider the blast radius before storing secrets there.
Assessment
This skill appears to do what it says: help you switch OpenClaw to SiliconFlow embeddings and validate indexing. Before proceeding: (1) be prepared to provide a SiliconFlow API key — prefer a secure secret store instead of pasting it into a repo-tracked config file; (2) review the exact gateway config.patch commands and who/what can read OpenClaw config in your environment (storing the key in config increases its exposure to other tools/skills); (3) add external extraPaths conservatively to avoid indexing sensitive or noisy files; (4) test changes in a staging instance if possible and be ready to rotate/revoke the API key after testing. If you want stronger protections, request guidance from the skill author on using secret references or environment-backed config rather than embedding the key directly in JSON config patches.Like a lobster shell, security has layers — review code before you run it.
latestvk976v1meqrx0x1cjw5b6r4gz3s83j0df
License
MIT-0
Free to use, modify, and redistribute. No attribution required.