Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Three-Dimensional Memory
v1.0.0Manages AI assistant memory by organizing files across three dimensions: timeline logs, full conversation backups, and topic-based project folders for easy r...
⭐ 0· 456·0 current·0 all-time
by@amlyx
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description match the behavior: the skill documents a filesystem layout and instructs the agent to write daily logs, conversation backups, and topic folders. No unrelated binaries, env vars, or external services are requested.
Instruction Scope
SKILL.md explicitly instructs the agent to save 'every word exchanged' to AI-memory-backup and to write daily logs and topic updates — this is consistent with the purpose but the instructions do not address redaction, encryption, access controls, or retention policies for potentially sensitive conversation transcripts.
Install Mechanism
No install spec; instruction-only skill with example shell script. The example script only creates/updates local files and prints guidance — it does not download or execute remote code.
Credentials
The skill requests no environment variables, credentials, or config paths. The lack of credential requests is appropriate for a local file-organization/backup skill.
Persistence & Privilege
always is false and the skill is user-invocable; the skill does not request elevated or persistent platform privileges. Autonomous invocation is allowed by default but not unusual here.
Assessment
This skill is internally coherent and does what it says: it instructs an assistant to persist daily logs, full conversation transcripts, and topic folders to local files. Before installing, consider the privacy risks: full conversation backups can contain secrets, PII, or sensitive business data. Ask how and where the files will be stored (workspace path), whether they will be encrypted at rest, who/what can read them, how long backups are retained, and whether transcripts should be redacted (credentials, API keys, personal data). If you intend to use this in a shared or cloud-mounted workspace, add encryption, access controls, and a retention/rotation policy, or modify the workflow to redact or exclude secrets from backups. The supplied example script writes plain files to the current workspace — review and run it manually first to confirm it behaves as you expect.Like a lobster shell, security has layers — review code before you run it.
latestvk975mqycn7sb4ewrzyz9pxrvqx81q88qmemoryvk975mqycn7sb4ewrzyz9pxrvqx81q88qorganizationvk975mqycn7sb4ewrzyz9pxrvqx81q88qproductivityvk975mqycn7sb4ewrzyz9pxrvqx81q88qworkflowvk975mqycn7sb4ewrzyz9pxrvqx81q88q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.