← Back to Skills Marketplace
deki18

OpenClaw Cortex Memory

by deki18 · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ⚠ suspicious
75
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install openclaw-cortex-memory
Description
Independent skill for Cortex Memory operations in OpenClaw. Use when users ask for cross-session memory continuity, prior decisions, preferences, relationshi...
Usage Guidance
This skill appears to be a legitimate Cortex memory helper, but review these before installing: 1) Confirm the plugin source (clawhub repository or npm package) and inspect the package contents (don’t install from an unknown registry without review). 2) Expect to provide API keys/endpoints for embeddings, LLM, and reranker — verify where those requests will go (baseURL values) and use trusted endpoints. 3) Back up your openclaw.json before applying the recommended config changes; the docs instruct disabling other memory backends which can disrupt existing memory plugins. 4) Prefer installing in a sandbox or test workspace first and run the recommended diagnostics (cortex_diagnostics) before enabling in production. 5) Ask the publisher/maintainer to reconcile the registry metadata (which lists no required env vars) with the SKILL.md/configuration, and provide a signed or verifiable release location if possible.
Capability Tags
requires-sensitive-credentials
Capability Assessment
Purpose & Capability
The skill's stated purpose (long-term Cortex memory operations) aligns with the runtime instructions and tool names (search_memory, query_graph, store_event, sync_memory, etc.). However the registry metadata lists no required environment variables while the SKILL.md frontmatter and references/configuration.md clearly expect EMBEDDING_API_KEY (primaryEnv) plus LLM_API_KEY and RERANKER_API_KEY. That mismatch between declared registry requirements and the skill's own docs is an inconsistency the operator should resolve.
Instruction Scope
SKILL.md and references constrain runtime behavior to checking/installing an OpenClaw plugin, running retrieval/persistence/diagnostic tool calls, and editing OpenClaw config. The instructions do not ask the agent to read arbitrary host files or exfiltrate secrets. Two items worth noting: (1) the docs instruct disabling other memory backends (memory-core, memory-lancedb) before install — this changes system configuration and could disrupt other memory plugins; (2) the fallback installation flow uses npm pack and local tgz handling which will write an archive to disk during install. Both are within the plugin-install domain but are impactful and deserve operator review.
Install Mechanism
The skill package itself is instruction-only (no install spec), but its recommended install flows call out 'openclaw plugins install clawhub:openclaw-cortex-memory' and a fallback using 'npm pack [email protected]' and installing a local .tgz. 'clawhub' is an unknown registry in this context (not a well-known OS package source), and npm pack results in a local archive that will be written and installed. This is a moderate install risk: installing third-party plugin code from an unverified registry or package can execute arbitrary code. There are no direct suspicious network endpoints embedded in files, but the install source should be validated.
Credentials
The plugin legitimately needs API keys for embedding, LLM, and reranker providers to function; those are proportionate to a memory/embedding system. The concern is the inconsistency: registry metadata shows no required env vars while SKILL.md/configuration require EMBEDDING_API_KEY (primaryEnv), LLM_API_KEY, and RERANKER_API_KEY and provide example baseURLs. Requireing multiple provider credentials is reasonable for the feature set, but the mismatch in declared requirements and the need to provide endpoints/API keys should be surfaced to users before install.
Persistence & Privilege
The skill is not 'always' enabled and does not claim elevated autonomic privileges. It instructs enabling and configuring an external plugin and modifying OpenClaw config, which is normal for a plugin of this nature. There's no evidence it tries to persist settings outside its own scope or auto-enable itself across the system.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install openclaw-cortex-memory
  3. After installation, invoke the skill by name or use /openclaw-cortex-memory
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Added a detailed Chinese introduction and documentation covering core features, technical details, and diagnostics for the Cortex Memory plugin. - Expanded feature explanations to include semantic retrieval, event storage, graph relationships, rule evolution, and operational diagnostics. - The English section remains, describing runtime flows and usage instructions. - No code or functional changes detected in this version.
v1.0.0
面向 OpenClaw 的长期记忆插件,集成多路检索、事件归档、图谱关系、向量化与反衰减排序,支持历史增量导入、规则反思和可观测诊断,可以将会话中零碎的记忆去噪整理、分层存储,支持对话中自动搜索回忆,吸收了LLM wiki的概念,帮助 Agent 在跨会话中持续积累并稳定调用高价值记忆。
Metadata
Slug openclaw-cortex-memory
Version 1.0.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is OpenClaw Cortex Memory?

Independent skill for Cortex Memory operations in OpenClaw. Use when users ask for cross-session memory continuity, prior decisions, preferences, relationshi... It is an AI Agent Skill for Claude Code / OpenClaw, with 75 downloads so far.

How do I install OpenClaw Cortex Memory?

Run "/install openclaw-cortex-memory" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is OpenClaw Cortex Memory free?

Yes, OpenClaw Cortex Memory is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does OpenClaw Cortex Memory support?

OpenClaw Cortex Memory is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created OpenClaw Cortex Memory?

It is built and maintained by deki18 (@deki18); the current version is v1.0.1.

💬 Comments