Memory Architect
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent for reorganizing existing memory files, but users should review it because it changes persistent agent memory and may structure sensitive personal or account-related notes.
This skill appears safe for its stated purpose, but it changes long-lived agent memory. Before installing or using it, be comfortable with the agent reading the full MEMORY.md, creating persistent memory files, and preserving existing directives. After use, review the generated files and consider keeping a backup.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Information from the old MEMORY.md may become easier for the agent to retrieve and reuse in later sessions.
The skill creates persistent structured memory that can be reused across tasks. This fits the memory-organization purpose, but persistent stored context can contain stale, sensitive, or misleading information.
memory/ontology/graph.jsonl → Structured entities + relations (JSONL append-only)
Review the generated memory files and graph, especially entries about people, projects, accounts, and instructions, and remove anything that should not persist.
Old or unwanted memory instructions could continue influencing future agent behavior after the restructuring.
The skill instructs the agent to carry forward existing memory directives that may affect future behavior. This is disclosed and likely intended to avoid losing existing rules, but those directives should be reviewed.
Preserves any system directives (NO_REPLY rules, heartbeat instructions)
Before or after running the skill, check preserved directives and remove any that should no longer guide the agent.
Important memory content could be misplaced or made less visible if the restructuring is wrong.
The skill intentionally rewrites the main memory file and moves content into multiple tier files. This is purpose-aligned, but mistakes in classification or rewriting could persist across future sessions.
Replace MEMORY.md with a ~25-line index
Keep a backup or review a diff of MEMORY.md and the generated memory/ files after use.