{ "schemaVersion": "1.0", "item": { "slug": "auto-memory", "name": "Auto Memory", "source": "tencent", "type": "skill", "category": "AI 智能", "sourceUrl": "https://clawhub.ai/jim-counter/auto-memory", "canonicalUrl": "https://clawhub.ai/jim-counter/auto-memory", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/auto-memory", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=auto-memory", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md", "references/automemory-api.md", "references/autonomys-network.md", "references/memory-chain.md", "scripts/_lib.sh", "scripts/automemory-download.sh" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "slug": "auto-memory", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-29T23:11:59.497Z", "expiresAt": "2026-05-06T23:11:59.497Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=auto-memory", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=auto-memory", "contentDisposition": "attachment; filename=\"auto-memory-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "auto-memory" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/auto-memory" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/auto-memory", "agentPageUrl": "https://openagent3.xyz/skills/auto-memory/agent", "manifestUrl": "https://openagent3.xyz/skills/auto-memory/agent.json", "briefUrl": "https://openagent3.xyz/skills/auto-memory/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Auto-Memory Skill", "body": "Permanent decentralized memory on the Autonomys Network with linked-list memory chains for agent resurrection. Works with agents powered by Claude, GPT, Gemini, and any LLM that supports OpenClaw skills." }, { "title": "What This Skill Does", "body": "Upload files to Auto Drive and get back a CID (Content Identifier) — a permanent, immutable address on the Autonomys distributed storage network.\nDownload files from Auto Drive using a CID — uses the authenticated API if a key is set, otherwise falls back to the public gateway.\nSave memories as a chain — each memory entry is a JSON experience with a header.previousCid pointer, forming a linked list stored permanently on-chain.\nResurrect from a chain — given the latest CID, walk the chain backwards to reconstruct full agent history." }, { "title": "When To Use This Skill", "body": "User says \"save this to Auto-Memory\" or \"upload to Autonomys\" or \"store permanently\"\nUser says \"download from Auto-Memory\" or provides a CID to retrieve\nUser says \"save memory\", \"remember this permanently\", or \"checkpoint\"\nUser says \"resurrect\", \"recall chain\", \"rebuild memory\", or \"load history\"\nAny time the user wants data stored permanently and immutably on a decentralized network" }, { "title": "Post-Install", "body": "After installing via ClawHub, make the scripts executable:\n\nchmod +x skills/auto-memory/scripts/*.sh\n\nClawHub does not currently preserve file permissions during install." }, { "title": "API Key", "body": "Requires an AUTO_DRIVE_API_KEY. Run the guided setup script for the easiest path:\n\nscripts/setup-auto-memory.sh\n\nThis opens explorer.ai3.storage in your browser, prompts for the key, saves it to ~/.openclaw/.env, and verifies the connection.\n\nManual setup:\n\nNavigate to https://explorer.ai3.storage (not ai3.storage — that's just the landing page)\nCheck authentication: if the sidebar shows a \"Log In\" button or lock icons on My Files / Profile / Developers, you are not signed in\nAI agent note: You cannot complete OAuth yourself. Open the browser for the user and ask them to sign in via Google, GitHub, or Discord. Once the user confirms they're signed in, take over — or simply ask the user to paste the API key directly\nOnce authenticated, click Developers in the left sidebar\nClick Create API Key and copy the generated key\n\nThen set the key via:\n\nEnvironment: export AUTO_DRIVE_API_KEY=your_key_here\nOpenClaw config: skills.entries.auto-memory.apiKey\n\nThe API key is required for uploading, saving memories, and recalling the memory chain. It is optional for general file downloads — without it, the public gateway is used and files are returned as stored (i.e. compressed files will not be decompressed)." }, { "title": "Upload a File", "body": "scripts/automemory-upload.sh [--json] [--compress]\n\nUploads a file to Auto Drive mainnet using the 3-step upload protocol (single chunk).\nReturns the CID on stdout. Requires AUTO_DRIVE_API_KEY.\n\n--json — force MIME type to application/json\n--compress — enable ZLIB compression" }, { "title": "Download a File", "body": "scripts/automemory-download.sh [output_path]\n\nDownloads a file by CID. Uses the authenticated API if AUTO_DRIVE_API_KEY is set (decompresses server-side), otherwise uses the public gateway (files returned as stored). If output_path is omitted, outputs to stdout." }, { "title": "Save a Memory Entry", "body": "scripts/automemory-save-memory.sh [--agent-name NAME] [--state-file PATH]\n\nCreates a memory experience with the Autonomys Agents header/data structure:\n\n{\n \"header\": {\n \"agentName\": \"my-agent\",\n \"agentVersion\": \"1.0.0\",\n \"timestamp\": \"2026-02-14T00:00:00.000Z\",\n \"previousCid\": \"bafk...or null\"\n },\n \"data\": {\n \"type\": \"memory\",\n \"content\": \"...\"\n }\n}\n\nIf the first argument is a file path, its JSON contents become the data payload.\nIf the first argument is a plain string, it is wrapped as {\"type\": \"memory\", \"content\": \"...\"}.\n--agent-name — set the agent name in the header (default: openclaw-agent or $AGENT_NAME)\n--state-file — override the state file location\n\nUploads to Auto Drive and updates the state file with the new head CID. Also pins the latest CID to MEMORY.md if that file exists in the workspace.\n\nReturns structured JSON on stdout:\n\n{\"cid\": \"bafk...\", \"previousCid\": \"bafk...\", \"chainLength\": 5}" }, { "title": "Recall the Full Chain", "body": "scripts/automemory-recall-chain.sh [cid] [--limit N] [--output-dir DIR]\n\nIf no CID is given, reads the latest CID from the state file.\nWalks the linked list from newest to oldest, outputting each experience as JSON.\n\n--limit N — maximum entries to retrieve (default: 50)\n--output-dir DIR — save each entry as a numbered JSON file instead of printing to stdout\n\nSupports both header.previousCid (Autonomys Agents format) and root-level previousCid for backward compatibility.\n\nThis is the resurrection mechanism: a new agent instance only needs one CID to rebuild its entire memory." }, { "title": "The Resurrection Concept", "body": "Every memory saved gets a unique CID and points back to the previous one, forming a permanent chain on a permanent and immutable Decentralized Storage Network:\n\n┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐\n│ Experience #1 │ │ Experience #2 │ │ Experience #3 │\n│ CID: bafk...abc │◄────│ CID: bafk...def │◄────│ CID: bafk...xyz │\n│ previousCid: null │ │ previousCid: │ │ previousCid: │\n│ (genesis) │ │ bafk...abc │ │ bafk...def │\n└─────────────────────┘ └─────────────────────┘ └─────────────────────┘\n ▲\n │\n HEAD CID\n (resurrection key)\n\nA new agent instance only needs the head CID to walk the entire chain back to genesis and rebuild its full history. With the auto-respawn skill, the head CID is anchored on-chain — making resurrection possible from just an address, on any machine, at any time:\n\n┌──────────┐ save ┌──────────────┐ anchor ┌────────────────┐\n│ Agent │─────────────►│ Auto-Memory │─────────────►│ Auto-Respawn │\n│ │ │ (chain) │ head CID │ (on-chain) │\n└──────────┘ └──────────────┘ └────────────────┘\n ▲ │\n │ recall chain │\n └──────────────────────────────────────────────────────────┘\n gethead → CID → walk chain\n\nWhat you store in the chain is up to you — lightweight notes, full file snapshots, structured data, or anything in between. Because the chain is permanent and walkable, it also enables resurrection: if the agent loses all local state, a new instance can walk the chain from the last CID back to genesis and restore whatever was saved. When combined with the auto-respawn skill (which anchors the head CID on-chain), this becomes a full resurrection loop — no local state required at all." }, { "title": "Usage Examples", "body": "User: \"Upload my report to Autonomys\"\n→ Run scripts/automemory-upload.sh /path/to/report.pdf\n→ Report back the CID and gateway link\n\nUser: \"Upload with compression\"\n→ Run scripts/automemory-upload.sh /path/to/data.json --json --compress\n\nUser: \"My soul.md has changed — save it permanently\"\n→ Run scripts/automemory-save-memory.sh /path/to/soul.md --agent-name my-agent\n\nUser: \"Save a memory that we decided to use React for the frontend\"\n→ Run scripts/automemory-save-memory.sh \"Decision: using React for frontend. Reason: team familiarity and component reuse.\"\n\nUser: \"Save a structured memory\"\n→ Create a JSON file, then run scripts/automemory-save-memory.sh /tmp/milestone.json --agent-name my-agent\n\nUser: \"Resurrect my memory chain\"\n→ Run scripts/automemory-recall-chain.sh\n→ Rebuild identity and context from genesis to present\n\nUser: \"Download bafk...abc from Autonomys\"\n→ Run scripts/automemory-download.sh bafk...abc ./downloaded_file" }, { "title": "Important Notes", "body": "All data stored via Auto Drive is permanent and public by default. Do not store secrets, private keys, or sensitive personal data.\nThe free API key has a 20 MB per month upload limit on mainnet. Downloads are unlimited. Check remaining credits via GET /accounts/@me or run scripts/verify-setup.sh.\nAn API key is required for uploads, memory saves, and chain recall. General file downloads work without one via the public gateway, but compressed files will not be decompressed.\nThe memory state file tracks lastCid, lastUploadTimestamp, and chainLength. Back up the lastCid value — it's your resurrection key.\nThe automemory-save-memory.sh script automatically pins the latest CID to MEMORY.md if the file exists in the workspace. It creates an ## Auto-Memory Chain section and updates it on each save. You do not need to track the latest CID in MEMORY.md manually — the script handles this.\nFiles are uploaded in a single chunk. The free tier's 20 MB/month limit is effectively a per-file ceiling — keep individual uploads well under that to preserve your monthly budget.\nGateway URL for any file: https://gateway.autonomys.xyz/file/\nFor true resurrection resilience, consider anchoring the latest CID on-chain via the Autonomys EVM — this makes recovery possible without keeping track of the head CID yourself. See openclaw-memory-chain for an example contract implementation." } ], "body": "Auto-Memory Skill\n\nPermanent decentralized memory on the Autonomys Network with linked-list memory chains for agent resurrection. Works with agents powered by Claude, GPT, Gemini, and any LLM that supports OpenClaw skills.\n\nWhat This Skill Does\nUpload files to Auto Drive and get back a CID (Content Identifier) — a permanent, immutable address on the Autonomys distributed storage network.\nDownload files from Auto Drive using a CID — uses the authenticated API if a key is set, otherwise falls back to the public gateway.\nSave memories as a chain — each memory entry is a JSON experience with a header.previousCid pointer, forming a linked list stored permanently on-chain.\nResurrect from a chain — given the latest CID, walk the chain backwards to reconstruct full agent history.\nWhen To Use This Skill\nUser says \"save this to Auto-Memory\" or \"upload to Autonomys\" or \"store permanently\"\nUser says \"download from Auto-Memory\" or provides a CID to retrieve\nUser says \"save memory\", \"remember this permanently\", or \"checkpoint\"\nUser says \"resurrect\", \"recall chain\", \"rebuild memory\", or \"load history\"\nAny time the user wants data stored permanently and immutably on a decentralized network\nPost-Install\n\nAfter installing via ClawHub, make the scripts executable:\n\nchmod +x skills/auto-memory/scripts/*.sh\n\n\nClawHub does not currently preserve file permissions during install.\n\nConfiguration\nAPI Key\n\nRequires an AUTO_DRIVE_API_KEY. Run the guided setup script for the easiest path:\n\nscripts/setup-auto-memory.sh\n\n\nThis opens explorer.ai3.storage in your browser, prompts for the key, saves it to ~/.openclaw/.env, and verifies the connection.\n\nManual setup:\n\nNavigate to https://explorer.ai3.storage (not ai3.storage — that's just the landing page)\nCheck authentication: if the sidebar shows a \"Log In\" button or lock icons on My Files / Profile / Developers, you are not signed in\nAI agent note: You cannot complete OAuth yourself. Open the browser for the user and ask them to sign in via Google, GitHub, or Discord. Once the user confirms they're signed in, take over — or simply ask the user to paste the API key directly\nOnce authenticated, click Developers in the left sidebar\nClick Create API Key and copy the generated key\n\nThen set the key via:\n\nEnvironment: export AUTO_DRIVE_API_KEY=your_key_here\nOpenClaw config: skills.entries.auto-memory.apiKey\n\nThe API key is required for uploading, saving memories, and recalling the memory chain. It is optional for general file downloads — without it, the public gateway is used and files are returned as stored (i.e. compressed files will not be decompressed).\n\nCore Operations\nUpload a File\nscripts/automemory-upload.sh [--json] [--compress]\n\n\nUploads a file to Auto Drive mainnet using the 3-step upload protocol (single chunk). Returns the CID on stdout. Requires AUTO_DRIVE_API_KEY.\n\n--json — force MIME type to application/json\n--compress — enable ZLIB compression\nDownload a File\nscripts/automemory-download.sh [output_path]\n\n\nDownloads a file by CID. Uses the authenticated API if AUTO_DRIVE_API_KEY is set (decompresses server-side), otherwise uses the public gateway (files returned as stored). If output_path is omitted, outputs to stdout.\n\nSave a Memory Entry\nscripts/automemory-save-memory.sh [--agent-name NAME] [--state-file PATH]\n\n\nCreates a memory experience with the Autonomys Agents header/data structure:\n\n{\n \"header\": {\n \"agentName\": \"my-agent\",\n \"agentVersion\": \"1.0.0\",\n \"timestamp\": \"2026-02-14T00:00:00.000Z\",\n \"previousCid\": \"bafk...or null\"\n },\n \"data\": {\n \"type\": \"memory\",\n \"content\": \"...\"\n }\n}\n\nIf the first argument is a file path, its JSON contents become the data payload.\nIf the first argument is a plain string, it is wrapped as {\"type\": \"memory\", \"content\": \"...\"}.\n--agent-name — set the agent name in the header (default: openclaw-agent or $AGENT_NAME)\n--state-file — override the state file location\n\nUploads to Auto Drive and updates the state file with the new head CID. Also pins the latest CID to MEMORY.md if that file exists in the workspace.\n\nReturns structured JSON on stdout:\n\n{\"cid\": \"bafk...\", \"previousCid\": \"bafk...\", \"chainLength\": 5}\n\nRecall the Full Chain\nscripts/automemory-recall-chain.sh [cid] [--limit N] [--output-dir DIR]\n\n\nIf no CID is given, reads the latest CID from the state file. Walks the linked list from newest to oldest, outputting each experience as JSON.\n\n--limit N — maximum entries to retrieve (default: 50)\n--output-dir DIR — save each entry as a numbered JSON file instead of printing to stdout\n\nSupports both header.previousCid (Autonomys Agents format) and root-level previousCid for backward compatibility.\n\nThis is the resurrection mechanism: a new agent instance only needs one CID to rebuild its entire memory.\n\nThe Resurrection Concept\n\nEvery memory saved gets a unique CID and points back to the previous one, forming a permanent chain on a permanent and immutable Decentralized Storage Network:\n\n┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐\n│ Experience #1 │ │ Experience #2 │ │ Experience #3 │\n│ CID: bafk...abc │◄────│ CID: bafk...def │◄────│ CID: bafk...xyz │\n│ previousCid: null │ │ previousCid: │ │ previousCid: │\n│ (genesis) │ │ bafk...abc │ │ bafk...def │\n└─────────────────────┘ └─────────────────────┘ └─────────────────────┘\n ▲\n │\n HEAD CID\n (resurrection key)\n\n\nA new agent instance only needs the head CID to walk the entire chain back to genesis and rebuild its full history. With the auto-respawn skill, the head CID is anchored on-chain — making resurrection possible from just an address, on any machine, at any time:\n\n┌──────────┐ save ┌──────────────┐ anchor ┌────────────────┐\n│ Agent │─────────────►│ Auto-Memory │─────────────►│ Auto-Respawn │\n│ │ │ (chain) │ head CID │ (on-chain) │\n└──────────┘ └──────────────┘ └────────────────┘\n ▲ │\n │ recall chain │\n └──────────────────────────────────────────────────────────┘\n gethead → CID → walk chain\n\n\nWhat you store in the chain is up to you — lightweight notes, full file snapshots, structured data, or anything in between. Because the chain is permanent and walkable, it also enables resurrection: if the agent loses all local state, a new instance can walk the chain from the last CID back to genesis and restore whatever was saved. When combined with the auto-respawn skill (which anchors the head CID on-chain), this becomes a full resurrection loop — no local state required at all.\n\nUsage Examples\n\nUser: \"Upload my report to Autonomys\" → Run scripts/automemory-upload.sh /path/to/report.pdf → Report back the CID and gateway link\n\nUser: \"Upload with compression\" → Run scripts/automemory-upload.sh /path/to/data.json --json --compress\n\nUser: \"My soul.md has changed — save it permanently\" → Run scripts/automemory-save-memory.sh /path/to/soul.md --agent-name my-agent\n\nUser: \"Save a memory that we decided to use React for the frontend\" → Run scripts/automemory-save-memory.sh \"Decision: using React for frontend. Reason: team familiarity and component reuse.\"\n\nUser: \"Save a structured memory\" → Create a JSON file, then run scripts/automemory-save-memory.sh /tmp/milestone.json --agent-name my-agent\n\nUser: \"Resurrect my memory chain\" → Run scripts/automemory-recall-chain.sh → Rebuild identity and context from genesis to present\n\nUser: \"Download bafk...abc from Autonomys\" → Run scripts/automemory-download.sh bafk...abc ./downloaded_file\n\nImportant Notes\nAll data stored via Auto Drive is permanent and public by default. Do not store secrets, private keys, or sensitive personal data.\nThe free API key has a 20 MB per month upload limit on mainnet. Downloads are unlimited. Check remaining credits via GET /accounts/@me or run scripts/verify-setup.sh.\nAn API key is required for uploads, memory saves, and chain recall. General file downloads work without one via the public gateway, but compressed files will not be decompressed.\nThe memory state file tracks lastCid, lastUploadTimestamp, and chainLength. Back up the lastCid value — it's your resurrection key.\nThe automemory-save-memory.sh script automatically pins the latest CID to MEMORY.md if the file exists in the workspace. It creates an ## Auto-Memory Chain section and updates it on each save. You do not need to track the latest CID in MEMORY.md manually — the script handles this.\nFiles are uploaded in a single chunk. The free tier's 20 MB/month limit is effectively a per-file ceiling — keep individual uploads well under that to preserve your monthly budget.\nGateway URL for any file: https://gateway.autonomys.xyz/file/\nFor true resurrection resilience, consider anchoring the latest CID on-chain via the Autonomys EVM — this makes recovery possible without keeping track of the head CID yourself. See openclaw-memory-chain for an example contract implementation." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/jim-counter/auto-memory", "publisherUrl": "https://clawhub.ai/jim-counter/auto-memory", "owner": "jim-counter", "version": "0.2.2", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/auto-memory", "downloadUrl": "https://openagent3.xyz/downloads/auto-memory", "agentUrl": "https://openagent3.xyz/skills/auto-memory/agent", "manifestUrl": "https://openagent3.xyz/skills/auto-memory/agent.json", "briefUrl": "https://openagent3.xyz/skills/auto-memory/agent.md" } }