Agent Memory Continuity
PassAudited by ClawScan on May 10, 2026.
Overview
This is a coherent local memory-continuity skill, but it persistently stores and reuses conversation context and can install a user-activated cron sync.
Install this only in a workspace where you are comfortable keeping local memory files. Review the generated memory content, avoid storing secrets, check the cron job if you enable automated sync, and verify any missing or external scripts before running them.
Findings (6)
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.
The agent may consult old memory even for simple tasks, which can introduce stale context or slow responses.
The skill installs a persistent protocol that broadly directs the agent to run a memory search before responses.
# AGENT MEMORY PROTOCOL - MANDATORY ... Before Any Response ... ALWAYS run memory_search first
Use the protocol for continuity-sensitive work, but consider narrowing the rule so memory search is not treated as authoritative for every response.
Local memory files can accumulate sensitive or stale information that future agent sessions may reuse.
The intended memory files may retain personal preferences, business context, project details, and behavioral notes for reuse across sessions.
Include user preferences discovered ... Add context that should be preserved across sessions ... Note patterns in user behavior or preferences
Do not store secrets in memory files; periodically review, edit, or delete stored memories; and use this only in workspaces you trust.
Memory files may keep being updated after setup until the cron entry is removed.
When the user runs the activation script, it adds a persistent cron job that continues executing the sync script every 6 hours.
CRON_JOB="0 */6 * * * cd $WORKSPACE && bash scripts/sync-memory.sh >> .memory-sync-log 2>&1"
Only activate sync if you want background updates, and inspect or remove the entry with crontab if you no longer need it.
Workspace paths with spaces or shell metacharacters could make the cron job fail or run unintended commands.
The workspace path is embedded into a shell command for cron without shell escaping.
WORKSPACE="${1:-$(pwd)}" ... CRON_JOB="0 */6 * * * cd $WORKSPACE && bash scripts/sync-memory.sh >> .memory-sync-log 2>&1"Use a simple trusted workspace path, or update the script to safely quote/escape the workspace path before installing the cron job.
Older daily memory files may be removed automatically, which could surprise users expecting long-term retention.
The recurring sync script deletes old markdown files under the memory directory.
find memory/ -name "*.md" -mtime +30 -delete 2>/dev/null || true
Review the cleanup behavior before enabling cron sync, and back up memory files or change the retention policy if needed.
Some documented setup steps may fail or may require code not included in the reviewed artifacts.
The instructions reference helper scripts that are not present in the supplied file manifest.
bash scripts/configure-search-first.sh ... bash scripts/setup-memory-archival.sh
Run only scripts included in the reviewed package, and verify any additional scripts from the upstream source before executing them.