ClawHub

Auto Memory

v1.0.0

Indestructible agent memory — permanently stored, never lost. Save decisions, identity, and context as a memory chain on the Autonomys Network. Rebuild your...

⭐ 0· 285·5 current·5 all-time
by@0xautonomys
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description, required binaries (curl, jq, file), and the single required env var (AUTO_DRIVE_API_KEY) are consistent with a tool that uploads/downloads files and manages a CID-based memory chain via the Auto Drive API.
ℹ
Instruction Scope
Runtime instructions and scripts are focused on uploading/downloading CIDs and managing a local state file and MEMORY.md. The skill reads/writes ~/.openclaw/openclaw.json, ~/.openclaw/.env, a workspace memory state file, and may update WORKSPACE/MEMORY.md — this is in scope but worth noting because the skill will persist the API key and chain head locally and requires the user to provide the API key (interactive browser flow is described).
✓
Install Mechanism
Install spec uses Homebrew formulas (curl, jq, file-formula). No arbitrary downloads or archive extraction are performed; install mechanism is standard and traceable.
ℹ
Credentials
Only AUTO_DRIVE_API_KEY is required (declared as primary). The scripts will store this key in plaintext in ~/.openclaw/.env and also write it into ~/.openclaw/openclaw.json (skills.entries.auto-memory.apiKey). This is expected for the functionality but users should be aware the key is persisted locally.
ℹ
Persistence & Privilege
always:false (normal). The skill persistently writes config and state files under the user's home directory and can modify a workspace MEMORY.md file; it does not modify other skills or system-wide settings beyond its own config files.
Assessment
This skill appears to do what it says: store and retrieve immutable memories on the Autonomys Auto Drive using an API key. Before installing, consider: 1) The skill will ask for and then save your AUTO_DRIVE_API_KEY to ~/.openclaw/.env and openclaw.json — if you prefer least privilege, create a dedicated API key with limited upload quota. 2) Uploaded data is claimed to be permanent — you cannot undo uploads; avoid storing secrets. 3) The skill will create/update state files in your OpenClaw workspace and may append a Latest CID into MEMORY.md; back up any values you care about (lastCid). 4) Verify the Auto Drive domains (api/gateway/dashboard) yourself and ensure you trust that service. 5) If you want to limit risk, review the included scripts (they are small, readable bash scripts) and consider running them manually rather than granting autonomous agent invocation. Overall the package is coherent with its purpose, but treat the persisted API key and permanent uploads with caution.

Like a lobster shell, security has layers — review code before you run it.

autonomysvk974psbp4ppj8j017ctraa7t81842d9ddecentralizedvk974psbp4ppj8j017ctraa7t81842d9dlatestvk974psbp4ppj8j017ctraa7t81842d9dlong-termvk974psbp4ppj8j017ctraa7t81842d9dmemoryvk974psbp4ppj8j017ctraa7t81842d9dopenclawvk974psbp4ppj8j017ctraa7t81842d9dpersistencevk974psbp4ppj8j017ctraa7t81842d9d

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

🧬 Clawdis
Binscurl, jq, file
EnvAUTO_DRIVE_API_KEY
Primary envAUTO_DRIVE_API_KEY

Install

Install curl (brew)
Bins: curl
brew install curl
Install jq (brew)
Bins: jq
brew install jq
Install file (brew)
Bins: file
brew install file-formula

Comments