context-memory
v1.0.0解决AI记忆混乱问题——"今天讲明天忘"。通过文件系统和规则流程实现持久记忆，确保新任务开始时自动回顾上下文，而不是靠"想"。核心机制：任务开始判断→读取记忆→执行→保存。适用于频繁切换话题或任务的AI协作场景。
⭐ 1· 30·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
Name/description match the actual instructions: the skill defines a file-based persistent memory layout and prescribes read/write rules for new tasks. No unrelated binaries, env vars, or installs are requested.
Instruction Scope
Instructions are focused on reading/writing files under a declared workspace layout (SOUL.md, MEMORY.md, .learnings/, memory/YYYY-MM-DD.md). This is coherent for a memory skill. However, the instructions mandate immediate persistent writes of potentially sensitive user data and allow the agent to auto-load '相关技能文档' and '其他业务技能按需加载' (related skill docs), which is somewhat open-ended and could cause the agent to access other skill documentation or persist unexpected information unless the workspace boundaries and content rules are enforced.
Install Mechanism
Instruction-only skill with no install spec and no code files—no artifacts will be downloaded or written by an installer, so install risk is minimal.
Credentials
The skill requests no environment variables, credentials, or config paths. The file access it prescribes is limited to a workspace directory, which is proportional to its stated purpose.
Persistence & Privilege
The skill intentionally creates and writes persistent files (this is its purpose). It is not force-enabled (always:false) and does not request elevated platform privileges. Users should note the privacy and retention implications of persistent storage.
Scan Findings in Context
[no_code_files] expected: This is an instruction-only skill; the regex scanner had no code to analyze. That is expected for this type of skill.
Assessment
This skill is coherent and low-risk from an install/credential perspective, but it will persistently write user- and task-related data to files. Before installing, decide where the workspace/ directory will live and who can read it. Avoid writing secrets (passwords, API keys, private PII) into these memory files or ensure they are encrypted and access-controlled. Consider tightening BOOTSTRAP.md rules so ambiguous cases require explicit user confirmation (to avoid unintended autonomous actions), and set a retention/deletion policy and audit process for the memory files. Finally, test the behavior in a sandboxed agent environment to verify it only reads/writes the intended workspace paths.Like a lobster shell, security has layers — review code before you run it.
latestvk975e82xhzrr31kdgxphx9yqbx842c0q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.