← Back to Skills Marketplace
77
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install shared-memory-stack
Description
Complete reference for the shared memory architecture connecting Claude Code, OpenClaw/Kimi, and LM Studio subagents through Obsidian vault + MemPalace (Chro...
Usage Guidance
This skill is a documentation-only guide for running a local shared-memory stack; it appears coherent in purpose but the metadata omits many operational requirements. Before installing or running anything mentioned here: 1) Do not allow an agent to run these commands autonomously — the doc includes concrete commands that will read and write local directories and could transmit data. 2) Manually verify the existence and contents of the referenced paths and binaries (/Volumes/2TB_APFS/..., /opt/homebrew/bin/mempalace, capture-idea, openclaw CLI). 3) Confirm SSH keys and 'gh' config are present and intended for use; never expose or copy private keys. 4) Review any local scripts (capture-idea, mempalace wrapper) before execution to ensure they don't call out to remote endpoints or exfiltrate data. 5) Ask the skill author to update metadata to list required binaries/credentials and to clarify which actions are purely descriptive vs meant to be executed. If you cannot validate these points, treat the skill as high-risk and avoid running the documented commands.
Capability Analysis
Type: OpenClaw Skill
Name: shared-memory-stack
Version: 1.0.0
The skill bundle defines a complex multi-agent workflow that grants an AI agent instructions for high-risk operations, specifically the automated creation of public GitHub repositories and pushing local code using a pre-configured SSH key (~/.ssh/github_nerua1). It relies on hardcoded absolute paths (/Volumes/2TB_APFS/openclaw-data/) and specific user identities (nerua1), which is highly irregular for a portable skill. While these appear to be intended features for a personal 'shared memory' architecture, the instructions to use 'gh repo create --public' and 'git push' provide a direct mechanism for accidental or coerced data exfiltration of local workspace content to a public forum.
Capability Tags
Capability Assessment
Purpose & Capability
The documented purpose — coordinating a shared local memory (Obsidian vault + ChromaDB/MemPalace) between Claude Code, OpenClaw and LM Studio — is coherent with the instructions. However the registry metadata declares no required binaries, env vars, or config paths while the SKILL.md repeatedly references specific binaries (/opt/homebrew/bin/mempalace, /opt/homebrew/bin/capture-idea, openclaw CLI, python3), absolute filesystem paths (/Volumes/2TB_APFS/...), and GitHub/SSH usage. That mismatch (metadata says 'none' but the doc requires many local tools/keys) is an incoherence and should be explained by the author before use.
Instruction Scope
The SKILL.md tells operators to read/write specific local directories, run local binaries that mine and index vault contents, and communicate over a local gateway (port 18789). It also references publishing to GitHub and assumes an SSH key and gh are configured. These instructions require filesystem access and existing credentials; if an agent were allowed to execute them automatically they could read and transmit potentially sensitive local data. The instructions are not purely descriptive — they include concrete commands that would perform IO on the host.
Install Mechanism
No install specification or code files are present; the skill is instruction-only. This reduces supply-chain risk because nothing will be automatically downloaded or written by the registry install itself. All executable behavior depends on local binaries described in the documentation.
Credentials
The skill metadata lists no required environment variables or credentials, yet the documentation explicitly assumes access to an SSH key and the 'gh' CLI, a local OpenClaw gateway, and specific home/workspace directories. That gap is concerning: the skill expects privileged local artifacts (keys, repos, large data directories) but does not declare them. Users should not expose SSH keys, tokens, or allow automatic execution of the described commands without verifying what will run and what data will be read or transmitted.
Persistence & Privilege
The skill is not force-included (always: false) and is user-invocable. Autonomous invocation is permitted by default but is not by itself flagged here. The skill does not request to modify other skills or system-wide settings in the provided documentation.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install shared-memory-stack - After installation, invoke the skill by name or use
/shared-memory-stack - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of shared-memory-stack skill: complete documentation of multi-agent shared memory architecture connecting Claude Code, OpenClaw/Kimi, and LM Studio via Obsidian vault and MemPalace (ChromaDB).
- Reference covers: vault/file structure, semantic/keyword search, idea capture pipeline, mempalace setup, and inter-agent communication.
- Details provided for key file paths, mining/searching procedures, CLI scripts, and skill publishing workflows for both Claude Code and OpenClaw.
- Outlines required Python environment, common issues, and troubleshooting tips for memory management and agent interoperability.
- Quick reference section for all major commands and daily usage scenarios.
Metadata
Frequently Asked Questions
What is Shared Memory Stack?
Complete reference for the shared memory architecture connecting Claude Code, OpenClaw/Kimi, and LM Studio subagents through Obsidian vault + MemPalace (Chro... It is an AI Agent Skill for Claude Code / OpenClaw, with 77 downloads so far.
How do I install Shared Memory Stack?
Run "/install shared-memory-stack" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Shared Memory Stack free?
Yes, Shared Memory Stack is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Shared Memory Stack support?
Shared Memory Stack is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Shared Memory Stack?
It is built and maintained by nerua1 (@nerua1); the current version is v1.0.0.
More Skills