← Back to Skills Marketplace
shared-memory-governor
by
jiy29104983
· GitHub ↗
· v1.0.2
· MIT-0
279
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install shared-memory-governor
Description
Govern a file-based shared-memory layer for OpenClaw multi-agent and subagent systems. Preserve each agent’s private memory while adding a separate, reviewab...
Usage Guidance
This is an instruction-only governance skill (no code, no installs, no credentials requested) and appears coherent with its purpose. Before enabling it in your workspace: 1) confirm the intended sharedRoot path — the reference defaults to /root/.openclaw/shared-memory, so change it if your workspace is elsewhere; 2) review schedule settings in the example config (privateMaintenance is enabled in the example) and disable any recurring tasks you do not want running; 3) ensure local SHARED_ATTACH.md and AGENTS.md guidance are accurate for each agent so the read/attach rules are enforced; and 4) remember this is documentation for operator behavior — the safety guarantees rely on the agent implementation following these rules, so audit any runtime that will implement these steps if you need stronger enforcement (e.g., code-level guards or OS permissions).
Capability Analysis
Type: OpenClaw Skill
Name: shared-memory-governor
Version: 1.0.2
The 'shared-memory-governor' skill is a governance framework designed to manage shared data layers across multiple AI agents within the OpenClaw environment. The skill's logic, defined across SKILL.md and several reference documents, focuses on maintaining strict identity isolation and preventing the accidental promotion of private data or secrets into shared space. It includes explicit safety boundaries that forbid reading credentials, SSH keys, or browser data. While it performs file modifications (e.g., updating AGENTS.md for startup guidance) and manages task schedules for maintenance, these actions are transparently documented and strictly scoped to the stated purpose of memory management, with no evidence of malicious intent, data exfiltration, or harmful prompt injection.
Capability Assessment
Purpose & Capability
Name/description match the content: all files are configuration and governance references for a file-based shared-memory layer. The skill does not request unrelated credentials, binaries, or external services that would be inconsistent with a local shared-file governance tool.
Instruction Scope
SKILL.md and references clearly constrain behavior (operate only inside user-designated workspace paths; never read credentials/secrets; keep shared memory supplemental). The only notable point is that the documented default config path resolves to /root/.openclaw/shared-memory/shared-memory.config.json (explicit in config-reference.md), so users should confirm that the default location matches their intended workspace; otherwise, commands may operate on the workspace under that path. Overall the instructions are specific and scoped to the stated purpose.
Install Mechanism
Instruction-only skill with no install spec, no binaries, and no archives to download. This is the lowest-risk install profile and is proportional to the described governance role.
Credentials
No environment variables, no credentials, and no required config paths beyond the documented workspace-shared path. The included example config explicitly disables shared recurring schedules by default (sharedScan/sharedMaintenance false) and sets sharing flags to disallow secrets and assistant identity; these align with the stated privacy-first goals.
Persistence & Privilege
Skill does not request always:true and does not claim autonomous persistent background execution. Example config contains schedule entries (privateMaintenance enabled, shared schedules disabled) — schedule activation would be a local config choice and is documented; the skill itself does not install persistent agents or services.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install shared-memory-governor - After installation, invoke the skill by name or use
/shared-memory-governor - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
Change default shared-memory path semantics to workspace-parent sibling and update config docs/example.
v1.0.1
Refined skill structure, clarified safety boundaries, reduced high-risk wording, renamed references, and aligned default config examples.
v0.1.0
Initial publish: shared memory governance workflow, attach/detach rules, and reference docs.
Metadata
Frequently Asked Questions
What is shared-memory-governor?
Govern a file-based shared-memory layer for OpenClaw multi-agent and subagent systems. Preserve each agent’s private memory while adding a separate, reviewab... It is an AI Agent Skill for Claude Code / OpenClaw, with 279 downloads so far.
How do I install shared-memory-governor?
Run "/install shared-memory-governor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is shared-memory-governor free?
Yes, shared-memory-governor is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does shared-memory-governor support?
shared-memory-governor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created shared-memory-governor?
It is built and maintained by jiy29104983 (@jiy29104983); the current version is v1.0.2.
More Skills