Layered Memory Architecture
v0.1.2Build cheap, truthful long-term memory for agents with a layered architecture instead of a memory blob. Design, explain, audit, or improve a system that sepa...
⭐ 0· 137·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (layered memory architecture) match the included SKILL.md and reference documents. There are no unrelated requirements (no env vars, binaries, or install steps) and all referenced materials are documentation for designing or migrating memory systems.
Instruction Scope
The runtime instructions are purely prescriptive guidance about classification, layering, promotion/demotion, retrieval order, and audit practices. They do not tell the agent to read arbitrary system files, access credentials, call external endpoints, or transmit data. The skill only references internal document files bundled with the skill.
Install Mechanism
There is no install spec and no code files; this is instruction-only. No downloads, package installs, or extracts are declared, so nothing is written to disk by an installer.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate for a documentation/design skill. There are no hidden references to external secrets in the instructions or bundled references.
Persistence & Privilege
The skill does not request persistent or elevated privileges (always is false). It does not modify other skills or system-wide settings in the documentation. Autonomous invocation is allowed by default on the platform, but that is normal and not excessive here given the skill's benign content.
Scan Findings in Context
[no-findings] expected: The regex-based scanner had no code files to analyze; this is an instruction-only skill composed of documentation files, so the absence of code findings is expected.
Assessment
This skill is documentation and guidance for designing layered memory systems and appears coherent. Before you adopt it operationally, consider: 1) how you will implement the storage layer (databases, vector stores) — that implementation will need access controls and credentials and is where real risk lives; 2) avoid automations that auto-promote summaries into canon without human review (the docs warn about this); and 3) if you or a developer implements helpers/automation based on these patterns, review that code/install process for network calls, secret usage, or persistent installs. In short: the skill content is safe and consistent, but any concrete implementation built from it should be audited separately for credentials, network access, and persistence behaviors.Like a lobster shell, security has layers — review code before you run it.
latestvk973me3j9ngdtexwpg760948ns83jmqh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.