← Back to Skills Marketplace
BenOS Memory Core
by
benmjohnson69
· GitHub ↗
· v0.1.2
783
Downloads
0
Stars
2
Active Installs
3
Versions
Install in OpenClaw
/install benos-memory-core
Description
Core runtime/volatile memory module for BenOS agent environment. Use to: store and retrieve active session state, open loops, decisions, and scratch notes at...
README (SKILL.md)
BenOS Memory Core
Purpose:
- Interface for runtime/volatile memory for BenOS agents and submodules.
- Store session info, open loops, decisions, and notes through index.js commands or direct file edits.
State/storage location:
- Default:
~/.openclaw/workspace/benos/runtime/state.json - Convention: Also supports related runtime and session files under
benos/runtime/.
Usage:
- Use skill commands for agent-controlled read/write.
- Edit files directly for manual repairs or migration as needed.
Schema v1:
- schemaVersion: number
- lastHydratedAt: ISO8601 or null
- lastSessionRef: string or null
- activeInitiatives: array
- openLoops: array
- recentDecisions: array
- notes: array
Extension: Add new fields via additional versioned schemas or skill upgrades as needed.
Usage Guidance
This skill simply reads two files in your home workspace (~/.openclaw/workspace/benos/runtime/state.json and last-session.md) and returns their contents. Before installing, review those files for any sensitive data (API keys, passwords, secrets, or PII) since the skill (and any agent using it) could expose their contents. Note the SKILL.md mentions write capability but the included code does not implement a write API — data changes must be made by editing files directly. The skill has no install script and no external network calls, but it comes from an unknown source with no homepage; prefer packages from trusted authors, and restrict which agents/skills are allowed to invoke this module if those files contain confidential information.
Capability Analysis
Type: OpenClaw Skill
Name: benos-memory-core
Version: 0.1.2
The skill is designed to manage the agent's runtime memory and state. All file system operations in `index.js` are strictly confined to the agent's designated workspace (`~/.openclaw/workspace/benos/runtime/`), which is explicitly documented in `SKILL.md`. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts against the agent. The code's behavior is entirely consistent with its stated purpose of storing and retrieving internal session state.
Capability Assessment
Purpose & Capability
The name/description claim a runtime/volatile memory module and the code reads the stated state file and last-session file under ~/.openclaw/workspace/benos/runtime — this matches the declared purpose. Minor mismatch: SKILL.md suggests 'agent-controlled read/write' via index.js, but index.js only implements reading (hydrate) and a no-op run; it does not expose a write API.
Instruction Scope
SKILL.md instructs agents to use skill commands for read/write or edit files directly. The runtime instructions and the code are narrowly scoped to reading two files in the user's home workspace. The skill will return file contents from state.json and last-session.md, so the agent could surface any sensitive data stored there. The code does not reference other system paths or external endpoints.
Install Mechanism
No install spec is provided (instruction-only skill with a small native entry file). Nothing is downloaded or written during install; only a 953-byte index.js is included. Low install risk.
Credentials
The skill declares no required environment variables or credentials. The code uses process.env.HOME implicitly to locate files (standard and expected) but HOME was not listed in requires.env — this is typical but worth noting. No other credentials, keys, or external services are requested.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request persistent system-wide privileges or modify other skills' configs. It only reads files within a subdirectory of the user's home.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install benos-memory-core - After installation, invoke the skill by name or use
/benos-memory-core - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.2
- Updated dependencies and internal logic in index.js.
- Refreshed skill.json metadata.
- No changes to external API or documented usage.
v0.1.1
- No user-facing changes in this version.
- No file or documentation updates detected.
v0.1.0
Initial release of benos-memory-core, providing runtime memory management for BenOS agents.
- Stores and retrieves active session state, open loops, decisions, and scratch notes at runtime.
- Uses a schema-based state file at `~/.openclaw/workspace/benos/runtime/state.json`.
- Supports both agent-controlled commands and direct file edits.
- Designed for extension with additional schema fields and upgrades.
Metadata
Frequently Asked Questions
What is BenOS Memory Core?
Core runtime/volatile memory module for BenOS agent environment. Use to: store and retrieve active session state, open loops, decisions, and scratch notes at... It is an AI Agent Skill for Claude Code / OpenClaw, with 783 downloads so far.
How do I install BenOS Memory Core?
Run "/install benos-memory-core" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is BenOS Memory Core free?
Yes, BenOS Memory Core is completely free (open-source). You can download, install and use it at no cost.
Which platforms does BenOS Memory Core support?
BenOS Memory Core is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created BenOS Memory Core?
It is built and maintained by benmjohnson69 (@benmjohnson69); the current version is v0.1.2.
More Skills