Memory-Dream
Security checks across static analysis, malware telemetry, and agentic risk
Overview
The skill's requests and actions are coherent with its stated purpose (reading recent daily memory files and surgically updating MEMORY.md); it has no declared credentials or install steps, but exercise normal caution because the registry/source metadata is incomplete and the skill will modify your memory files if run.
What to consider before installing or enabling: - Backup: Make a copy of MEMORY.md and your memory/ directory before first run so you can inspect changes and recover if needed. - Inspect source: The registry lists no homepage/source; README points to a GitHub repo. If you plan to clone/install, review that repository (SKILL.md/README/LICENSE) yourself to ensure it matches what's in the registry. - Manual first run: Trigger the skill manually (e.g., say "dream") and review the consolidation report and the diff of changes to MEMORY.md before allowing automatic cron runs. - Cron/automation: If you enable the recommended cron job, start with a low-frequency schedule (manual or weekly) until you confirm behavior is safe and idempotent. - Principle of least surprise: The skill will read recent daily logs and edit MEMORY.md and today's journal (append log). It claims not to delete files or surface secrets, but verify reports do not accidentally leak sensitive data. - Trust boundary: Because the skill can autonomously edit files, only enable it if you trust the author/source. If the source is unknown, keep confidence lower and require manual review of changes. - If you want higher assurance: ask the publisher for a signed release or a repository URL included in registry metadata; check for community reviews or run the skill in a sandbox/workspace copy first.
SkillSpector
SkillSpector findings are pending for this release.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.