← Back to Skills Marketplace
345
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install hippocampus-subagent-memory
Description
Isolate and coordinate sub-agent memory in OpenClaw with Hippocampus using scoped IDs, bounded merge-back, and explicit cross-agent imports.
README (SKILL.md)
Hippocampus Subagent Memory
Use this skill when OpenClaw spawns sub-agents that need their own memory without contaminating the parent agent context.
Use It For
- creating isolated sub-agent memory namespaces
- preventing accidental memory leakage across siblings
- returning only bounded summaries or artifacts to the parent
- coordinating explicit import from child to parent
Preferred Flow
- Spawn a child with a scoped
HIPOKAMP_SUBAGENT_ID. - Let the child write only into its own namespace.
- Return a bounded result package at the end of the task.
- Import back to parent only what is explicitly approved.
Guidance
- Default to isolation.
- Do not flatten full child memory into the parent.
- Prefer summary, artifacts, and references over transcript copy.
- Tag child memory with session and parent linkage metadata.
- Root-agent bootstrap should happen once in the portal; child agents should inherit scope automatically and should not require separate portal signup.
Related
hippocampus-memory-corefor core memory operationshippocampus-openclaw-onboardingfor base config@hippocampus/openclaw-context-enginefor automated spawn/end lifecycle hooks
Usage Guidance
This skill is mostly a policy document, but there are a few things to check before you use it in production: 1) Confirm the intended environment variable name — the doc uses 'HIPOKAMP_SUBAGENT_ID' which looks like a typo; ask the author what the canonical scoped-ID is and how it's set. 2) Ask how the 'portal' bootstrap and related packages are provided: do you need hippocampus-memory-core or onboarding code installed elsewhere? If so, request a concrete install/auth plan and minimal required credentials. 3) If you will let agents inherit scope automatically, verify this does not grant them access to unrelated credentials or agent configuration. 4) Test this in a sandbox: ensure child agents only write to their namespace and that the merge-back mechanism only returns the bounded summaries you expect. 5) Prefer the author add explicit env/credential requirements (or confirm none are needed) and fix the typo to avoid accidental misconfiguration. If those clarifications are provided and implemented minimally, the skill can be considered coherent; without them, treat it cautiously.
Capability Analysis
Type: OpenClaw Skill
Name: hippocampus-subagent-memory
Version: 0.1.0
The skill bundle contains metadata and architectural instructions for managing sub-agent memory isolation. The SKILL.md file provides logical guidance on using scoped IDs and bounded data merging to prevent context contamination between parent and child agents, with no evidence of malicious code, data exfiltration, or harmful prompt injection.
Capability Assessment
Purpose & Capability
Skill name/description (Hippocampus sub-agent memory) matches the instructions (create isolated namespaces, bounded merge-back). However the SKILL.md references related packages and onboarding artifacts (hippocampus-memory-core, hippocampus-openclaw-onboarding, @hippocampus/openclaw-context-engine) and a 'portal' process without declaring any install steps or required credentials—this is plausible for an instruction-only policy but is an unexplained dependency surface. Also the SKILL.md uses a differently spelled env token 'HIPOKAMP_SUBAGENT_ID' which is likely a typo and could cause misconfiguration.
Instruction Scope
The runtime instructions stay within the stated purpose: spawn child agents, restrict writes to a scoped namespace, return bounded summaries, and import explicitly. There are no directives to read arbitrary host files, exfiltrate data, or contact external endpoints outside the conceptual 'portal' mention.
Install Mechanism
This is an instruction-only skill with no install spec and no code files — low disk/write risk. Because no install occurs, there is no direct supply-chain risk from this repository itself.
Credentials
The skill declares no required env vars or credentials, which is proportionate for an instruction doc. But it references a scoped ID value ('HIPOKAMP_SUBAGENT_ID') and a portal bootstrap process without specifying how scope/authentication is obtained. That inconsistency (missing declared env usage, and the probable typo) should be clarified; otherwise implementers may hardcode sensitive tokens or invent unsafe workarounds.
Persistence & Privilege
The skill does not request permanent presence (always:false) and has no install steps that modify agent/system configuration. Autonomous invocation is allowed (platform default) but not combined here with other clear red flags.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install hippocampus-subagent-memory - After installation, invoke the skill by name or use
/hippocampus-subagent-memory - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
- Initial release of hippocampus-subagent-memory skill.
- Enables isolated sub-agent memory in OpenClaw using scoped IDs.
- Prevents accidental memory leakage across sibling/parent contexts.
- Supports bounded merge-back and explicit import from child to parent.
- Includes guidance for namespace management and session linkage.
Metadata
Frequently Asked Questions
What is Hippocampus Subagent Memory?
Isolate and coordinate sub-agent memory in OpenClaw with Hippocampus using scoped IDs, bounded merge-back, and explicit cross-agent imports. It is an AI Agent Skill for Claude Code / OpenClaw, with 345 downloads so far.
How do I install Hippocampus Subagent Memory?
Run "/install hippocampus-subagent-memory" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Hippocampus Subagent Memory free?
Yes, Hippocampus Subagent Memory is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Hippocampus Subagent Memory support?
Hippocampus Subagent Memory is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Hippocampus Subagent Memory?
It is built and maintained by cezexPL (@cezexpl); the current version is v0.1.0.
More Skills