Total Recall

The only memory skill that watches on its own. No database. No vectors. No manual saves. Just an LLM observer that compresses your conversations into priorit...

Key things to check before installing: - Verify declared requirements: the registry metadata did not list required env vars but SKILL.md and scripts require an LLM API key (OPENROUTER_API_KEY / LLM_API_KEY). Confirm which keys are actually needed and where they will be used. - Audit the scripts (setup.sh, observer-*.sh, reflector-*.sh, dream-cycle.sh, session-recovery.sh) before running setup.sh. setup.sh will create memory/ and logs/, install cron jobs and (on Linux) a systemd watcher — review and optionally run the commands manually rather than blindly executing setup.sh. - Start in safe mode: run Dream Cycle in READ_ONLY_MODE=true and run observer scripts manually to see outputs before enabling automatic writes. The prompts default to writing (READ_ONLY_MODE=false) if you don't explicitly set this. - Consider using a local LLM endpoint first (LLM_BASE_URL pointing to localhost) or a dummy API key during evaluation to avoid sending your session data to a remote provider until you are comfortable. If you must use a hosted provider, be aware that session transcripts and derived observations will be transmitted to that provider. - Check cron/systemd entries that will be created and remove or restrict them if you prefer manual invocation. Back up your current workspace and existing memory/observations.md before enabling automatic schedules. - Be cautious about the memoryFlush config: it instructs an agent turn to run the observer and to write a session summary automatically. If you keep that hook, that summary will be generated and persisted at compaction time. If you want, I can: (1) list the exact files/lines in setup.sh that create services/crontab entries, (2) summarize which scripts call network endpoints and where, or (3) produce a safe checklist to run the skill in read-only/evaluation mode.

Type: OpenClaw Skill Name: total-recall Version: 1.5.1 The skill is classified as suspicious due to its extensive use of high-risk capabilities, including direct shell command execution (`exec: bash`, `Run bash`) via agent instructions in `config/memory-flush.json`, `templates/AGENTS-snippet.md`, and `config/cron-job.json`. It also installs a systemd service (`scripts/setup.sh`) and performs `git reset --hard` (`scripts/dream-cycle.sh`). While these actions are integral to the skill's stated purpose of autonomous memory management and include explicit defenses against prompt injection (e.g., path traversal protection in `scripts/dream-cycle.sh` and `scripts/staging-review.sh`, and instructions to the agent not to write to sensitive files in `prompts/dream-cycle-prompt.md`), the inherent power of these operations and the potential for a sophisticated prompt injection or a compromised LLM to bypass defenses elevate the risk beyond benign. There is no evidence of intentional malicious behavior such as data exfiltration to unauthorized endpoints or stealthy backdoors.