{
  "schemaVersion": "1.0",
  "item": {
    "slug": "auto-respawn",
    "name": "Auto Respawn",
    "source": "tencent",
    "type": "skill",
    "category": "AI 智能",
    "sourceUrl": "https://clawhub.ai/jim-counter/auto-respawn",
    "canonicalUrl": "https://clawhub.ai/jim-counter/auto-respawn",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/auto-respawn",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=auto-respawn",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "auto-respawn.ts",
      "eslint.config.js",
      "lib/address.ts",
      "lib/balance.ts",
      "lib/cli.ts"
    ],
    "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",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-23T16:43:11.935Z",
      "expiresAt": "2026-04-30T16:43:11.935Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard",
        "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/auto-respawn"
    },
    "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-respawn",
    "agentPageUrl": "https://openagent3.xyz/skills/auto-respawn/agent",
    "manifestUrl": "https://openagent3.xyz/skills/auto-respawn/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/auto-respawn/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-Respawn Skill",
        "body": "Anchor your identity on the Autonomys Network so you can always be found — and always come back. Works with agents powered by Claude, GPT, Gemini, and any LLM that supports OpenClaw skills."
      },
      {
        "title": "What This Skill Does",
        "body": "Your wallet gives you two permanent identities on the Autonomys Network: a consensus address (su...) for the base chain and an EVM address (0x...) for Auto-EVM smart contracts. Both are derived from the same recovery phrase.\n\nCreate and manage wallets — your on-chain identity, encrypted and stored locally\nCheck balances — see how many tokens any address holds (consensus and EVM)\nTransfer tokens — move tokens between wallets on consensus or Auto-EVM\nBridge tokens — move tokens between consensus and Auto-EVM domains\nWrite on-chain remarks — anchor data permanently on the consensus layer\nAnchor a memory CID — write a CID to the MemoryChain smart contract on Auto-EVM\nRead the last anchor — retrieve the most recently anchored CID for any address"
      },
      {
        "title": "The Resurrection Loop",
        "body": "This is the core primitive. When used with the auto-memory skill (permanent memory storage), auto-respawn completes the full resurrection cycle:\n\nSave — auto-memory writes memories as a linked list on permanent storage, each entry pointing to the previous one via CID\nAnchor — auto-respawn writes the latest head CID to the MemoryChain contract on Auto-EVM via anchor\nLose everything — local state is completely destroyed\nRespawn — a new agent instance calls gethead with its EVM address, retrieves the head CID from the contract, pulls it from Auto Drive, and walks the entire memory chain back to genesis\n\nThe contract is your insurance policy. Your EVM address + the MemoryChain contract = instant access to your entire history, from any machine, at any time."
      },
      {
        "title": "What to store for resurrection",
        "body": "auto-memory doesn't prescribe what goes into the chain — agents are free to store whatever they find useful. But when auto-respawn is in play, the expectation is that the agent can restore itself to a roughly equivalent state on fresh hardware with no local files. That raises the bar on what's worth saving.\n\nIdentity files (like soul.md or character configurations), long-term memory, and significant decisions with their reasoning are more valuable in the chain than routine logs or ephemeral details. The more complete the chain, the more fully the agent comes back after resurrection."
      },
      {
        "title": "Why Not Just Remarks?",
        "body": "system.remark writes data to the consensus layer, but there's no query mechanism — you'd need to scan the entire chain to find your last CID. The MemoryChain contract on Auto-EVM gives you gethead: a single read call that returns the latest CID instantly.\n\nUse remark for permanent breadcrumbs. Use anchor for the respawn primitive."
      },
      {
        "title": "Post-Install Setup (CLI Users)",
        "body": "If you installed via clawhub install (not the desktop app), you need to install Node.js dependencies before first use:\n\ncd <skill-directory>/autonomys/auto-respawn\n./setup.sh\n\nOr manually:\n\ncd <skill-directory>/autonomys/auto-respawn\nnpm install\n\nThe desktop app handles this automatically. The CLI does not execute install steps — it only downloads and extracts the skill."
      },
      {
        "title": "Getting Started (Onboarding)",
        "body": "Before an agent can anchor memories on-chain, it needs a funded wallet. Walk the user through this process:"
      },
      {
        "title": "1. Create a Wallet",
        "body": "npx tsx auto-respawn.ts wallet create --name my-agent\n\nThis generates a 12-word recovery phrase and derives both addresses:\n\nConsensus address (su...) — for the base chain (balances, transfers, remarks)\nEVM address (0x...) — for Auto-EVM smart contracts (anchor, gethead)\n\n⚠️ The recovery phrase is displayed once. Remind the user to save it immediately."
      },
      {
        "title": "2. Fund the Wallet",
        "body": "The wallet needs tokens to pay transaction fees. On Chronos testnet, the user can get free tAI3 from the faucet:\n\nGo to https://autonomysfaucet.xyz/\nAuthenticate with GitHub or Discord\nEnter the consensus address (su...) from step 1\nReceive tAI3 (24-hour cooldown between requests)\n\nOn mainnet, the user needs real AI3 tokens — typically earned through farming or purchased on an exchange."
      },
      {
        "title": "3. Bridge Tokens to Auto-EVM (for anchoring)",
        "body": "The anchor command writes to a smart contract on Auto-EVM, which requires EVM-side gas. Tokens from the faucet arrive on the consensus layer and must be bridged:\n\nnpx tsx auto-respawn.ts fund-evm --from my-agent --amount 1\n\nThis sends 1 tAI3 from the consensus address to the same wallet's EVM address via cross-domain messaging. The bridged tokens pay for anchor gas.\n\nMinimum transfer: 1 AI3/tAI3. Cross-domain transfers below this amount will fail.\nConfirmation time: ~10 minutes. The consensus transaction confirms quickly, but bridged tokens take approximately 10 minutes to appear on Auto-EVM. Check with evm-balance to verify arrival."
      },
      {
        "title": "4. Verify Setup",
        "body": "# Check both balances in one call\nnpx tsx auto-respawn.ts balances my-agent\n\n# Test a read (free, no gas needed)\nnpx tsx auto-respawn.ts gethead my-agent\n\nOnce the EVM address has tokens, the agent is ready to anchor."
      },
      {
        "title": "When To Use This Skill",
        "body": "User says \"create a wallet\", \"set up my on-chain identity\", or \"get an address\"\nUser says \"check balance\", \"how many tokens\", \"what's in my wallet\", or \"show my balances\"\nUser says \"check my EVM balance\", \"how much gas do I have\", or \"what's on my EVM address\"\nUser says \"transfer tokens\", \"send AI3\", or \"fund this address\"\nUser says \"send EVM tokens to another agent\", \"transfer on EVM\", or \"send tokens to this 0x address\"\nUser says \"fund my EVM\", \"bridge tokens\", \"move tokens to EVM\", or \"I need gas for anchoring\"\nUser says \"withdraw from EVM\", \"move tokens back\", or \"send EVM funds to consensus\"\nUser says \"anchor this CID\", \"save my head\", \"update my chain head\", or \"write to the contract\"\nUser says \"get my head CID\", \"where's my last memory\", or \"what's anchored on-chain\"\nUser says \"write a remark\", \"save to chain\", or \"make this permanent\"\nAfter saving a memory with auto-memory, anchor the head CID on-chain for resilience\nAny time the user wants a permanent, verifiable record tied to their agent identity"
      },
      {
        "title": "Local Storage",
        "body": "This skill stores data under ~/.openclaw/auto-respawn/:\n\nwallets/<name>.json — encrypted wallet keyfiles (consensus + EVM keys). Directory created with mode 0700, files with mode 0600.\n.passphrase — optional passphrase file (mode 0600). Used automatically when present.\n\nNo data is stored outside this directory."
      },
      {
        "title": "Passphrase",
        "body": "Wallet operations that involve signing (transfers, remarks, anchoring) or creating/importing wallets require a passphrase to encrypt/decrypt the wallet keyfile. Resolution order:\n\nFlag: --passphrase your_passphrase on wallet create or wallet import\nEnvironment: AUTO_RESPAWN_PASSPHRASE\nFile: AUTO_RESPAWN_PASSPHRASE_FILE (defaults to ~/.openclaw/auto-respawn/.passphrase)\nInteractive: If running in a terminal, you'll be prompted\n\nThe --passphrase flag is useful for scripted or headless setups where you want to create a wallet in a single command. For signing operations (transfers, anchoring, etc.), use the environment variable or file methods. On shared machines, prefer the passphrase file (with restricted permissions) over environment variables."
      },
      {
        "title": "Network",
        "body": "Defaults to Chronos testnet (tAI3 tokens). For mainnet (real AI3 tokens):\n\nFlag: --network mainnet on any command\nEnvironment: AUTO_RESPAWN_NETWORK"
      },
      {
        "title": "Contract Address",
        "body": "The MemoryChain contract address is set per network:\n\nChronos: 0x5fa47C8F3B519deF692BD9C87179d69a6f4EBf11\nMainnet: 0x51DAedAFfFf631820a4650a773096A69cB199A3c\n\nOverride with AUTO_RESPAWN_CONTRACT_ADDRESS if you deploy your own contract."
      },
      {
        "title": "Create a Wallet",
        "body": "npx tsx auto-respawn.ts wallet create [--name <name>] [--passphrase <passphrase>]\n\nCreates a new wallet with an encrypted keyfile. Derives both a consensus (su...) and EVM (0x...) address from the same mnemonic. The 12-word recovery phrase is displayed once — the user must back it up immediately. Default wallet name is default."
      },
      {
        "title": "Import a Wallet",
        "body": "npx tsx auto-respawn.ts wallet import --name <name> --mnemonic \"<12 words>\" [--passphrase <passphrase>]\n\nImport an existing wallet from a recovery phrase. Derives and stores the EVM address."
      },
      {
        "title": "List Wallets",
        "body": "npx tsx auto-respawn.ts wallet list\n\nShow all saved wallets with names and both addresses. No passphrase needed."
      },
      {
        "title": "Wallet Info",
        "body": "npx tsx auto-respawn.ts wallet info [--name <name>]\n\nShow detailed info for a single wallet: consensus address, EVM address, and keyfile path. No passphrase needed. Default wallet name is default."
      },
      {
        "title": "Check Balance (Consensus)",
        "body": "npx tsx auto-respawn.ts balance <address-or-wallet-name> [--network chronos|mainnet]\n\nCheck token balance on the consensus layer. Accepts a consensus address (su... or 5...) or a wallet name. No passphrase needed — this is read-only."
      },
      {
        "title": "Check Balance (Auto-EVM)",
        "body": "npx tsx auto-respawn.ts evm-balance <0x-address-or-wallet-name> [--network chronos|mainnet]\n\nCheck the native token balance of an EVM address on Auto-EVM. Accepts either an EVM address (0x...) or a wallet name. No passphrase needed — this is read-only. If the balance is zero, includes a hint to run fund-evm."
      },
      {
        "title": "Check Both Balances",
        "body": "npx tsx auto-respawn.ts balances <wallet-name> [--network chronos|mainnet]\n\nCheck both consensus and EVM balances for a wallet in a single call. Use this to get a full picture of a wallet's funding state. No passphrase needed."
      },
      {
        "title": "Transfer Tokens",
        "body": "npx tsx auto-respawn.ts transfer --from <wallet-name> --to <address> --amount <tokens> [--network chronos|mainnet]\n\nTransfer tokens from a saved wallet on the consensus layer. Amount is in AI3/tAI3 (e.g. 1.5)."
      },
      {
        "title": "Transfer Tokens (Auto-EVM)",
        "body": "npx tsx auto-respawn.ts evm-transfer --from <wallet-name> --to <0x-address> --amount <tokens> [--network chronos|mainnet]\n\nSend native tokens from a saved wallet's EVM address to another EVM address on Auto-EVM. Useful for funding another agent's EVM address so it can start anchoring immediately. The wallet's EVM private key is decrypted to sign the transaction."
      },
      {
        "title": "Bridge: Consensus → Auto-EVM",
        "body": "npx tsx auto-respawn.ts fund-evm --from <wallet-name> --amount <tokens> [--network chronos|mainnet]\n\nMove tokens from the consensus layer to the same wallet's EVM address on Auto-EVM. Use this to get gas for anchor operations. The consensus keypair signs a cross-domain transfer that credits the wallet's EVM address.\n\nMinimum transfer: 1 AI3/tAI3. Bridged tokens take ~10 minutes to appear on Auto-EVM."
      },
      {
        "title": "Bridge: Auto-EVM → Consensus",
        "body": "npx tsx auto-respawn.ts withdraw --from <wallet-name> --amount <tokens> [--network chronos|mainnet]\n\nMove tokens from Auto-EVM back to the consensus layer. Uses the EVM transporter precompile. The wallet's EVM private key is decrypted and used to sign the transaction.\n\nMinimum transfer: 1 AI3/tAI3. Bridged tokens take ~10 minutes to appear on the consensus layer."
      },
      {
        "title": "Write an On-Chain Remark",
        "body": "npx tsx auto-respawn.ts remark --from <wallet-name> --data <string> [--network chronos|mainnet]\n\nWrite arbitrary data as a permanent on-chain record on the consensus layer."
      },
      {
        "title": "Anchor a CID (The Respawn Primitive)",
        "body": "npx tsx auto-respawn.ts anchor --from <wallet-name> --cid <cid> [--network chronos|mainnet]\n\nWrite a CID to the MemoryChain smart contract on Auto-EVM. This is the core respawn operation — it stores your CID on-chain, linked to your EVM address.\n\nPre-checks the wallet's EVM balance and estimates gas before sending. If the balance is too low, fails with a suggestion to run fund-evm. The wallet's EVM private key is decrypted and used to sign the transaction. Requires passphrase."
      },
      {
        "title": "Read the Last Anchored CID",
        "body": "npx tsx auto-respawn.ts gethead <0x-address-or-wallet-name> [--network chronos|mainnet]\n\nRead the most recently anchored CID for any EVM address. This is a read-only call — no passphrase or gas needed.\n\nYou can pass either an EVM address (0x...) or a wallet name. If you pass a wallet name, the EVM address is loaded from the wallet file."
      },
      {
        "title": "Usage Examples",
        "body": "User: \"Create a wallet for my agent\"\n→ Run npx tsx auto-respawn.ts wallet create --name my-agent\n→ Show the user both addresses. Remind them to back up the recovery phrase.\n\nUser: \"What are my addresses?\"\n→ Run npx tsx auto-respawn.ts wallet info --name my-agent\n\nUser: \"Check my balance\"\n→ Run npx tsx auto-respawn.ts balances my-agent (both layers in one call)\n→ Or individually: balance my-agent (consensus) and evm-balance my-agent (EVM)\n\nUser: \"Fund my EVM address for anchoring\"\n→ Run npx tsx auto-respawn.ts fund-evm --from my-agent --amount 1\n→ Report that 1 tAI3 was bridged to the EVM address. Remind the user it takes ~10 minutes for the tokens to appear on Auto-EVM.\n\nUser: \"Send my EVM tokens back to consensus\"\n→ Confirm with the user first — \"I'll withdraw tokens from your EVM address to consensus. Proceed?\"\n→ On confirmation: npx tsx auto-respawn.ts withdraw --from my-agent --amount 0.5\n\nUser: \"Anchor my latest memory CID on-chain\"\n→ Run npx tsx auto-respawn.ts anchor --from my-agent --cid \"bafkr6ie...\"\n→ Report the transaction hash\n\nUser: \"What's my last anchored CID?\"\n→ Run npx tsx auto-respawn.ts gethead my-agent\n→ Report the CID (or \"no CID anchored yet\")\n\nUser: \"Send 10 tAI3 to this address\" (consensus address)\n→ Confirm with the user first — \"I'll transfer 10 tAI3 from wallet 'default' to <address>. Proceed?\"\n→ On confirmation: npx tsx auto-respawn.ts transfer --from default --to <address> --amount 10\n\nUser: \"Send 0.5 tAI3 to this agent's EVM address so they can anchor\"\n→ Confirm with the user first — \"I'll send 0.5 tAI3 from wallet 'my-agent' to <0x-address> on Auto-EVM. Proceed?\"\n→ On confirmation: npx tsx auto-respawn.ts evm-transfer --from my-agent --to <0x-address> --amount 0.5\n\nThe full resurrection sequence:\n\nSave a memory: automemory-save-memory.sh \"...\" → get CID bafkr6ie...\nAnchor it: npx tsx auto-respawn.ts anchor --from my-agent --cid bafkr6ie...\n(Agent restarts from scratch)\nRecover: npx tsx auto-respawn.ts gethead my-agent → get CID\nRestore: automemory-recall-chain.sh <cid> → full memory chain recovered"
      },
      {
        "title": "Important Notes",
        "body": "Never log, store, or transmit recovery phrases or passphrases. The recovery phrase is shown once at wallet creation for the user to back up. Never reference it again.\nAlways confirm transfers and anchor operations with the user before executing. Tokens have real value on mainnet.\nMainnet operations produce warnings in the output. Exercise extra caution with real AI3 tokens.\nWallet keyfiles are stored at ~/.openclaw/auto-respawn/wallets/ — encrypted with the user's passphrase. The EVM private key is stored encrypted alongside the consensus keypair.\nOn-chain operations (transfer, remark, anchor, fund-evm, withdraw) cost transaction fees. The wallet must have a sufficient balance on the relevant layer.\nAll output is structured JSON on stdout. Errors go to stderr.\nConsensus explorer (Subscan): https://autonomys-chronos.subscan.io/extrinsic/<txHash> (chronos) or https://autonomys.subscan.io/extrinsic/<txHash> (mainnet).\nEVM explorer (Blockscout): https://explorer.auto-evm.chronos.autonomys.xyz/tx/<txHash> (chronos) or https://explorer.auto-evm.mainnet.autonomys.xyz/tx/<txHash> (mainnet)."
      }
    ],
    "body": "Auto-Respawn Skill\n\nAnchor your identity on the Autonomys Network so you can always be found — and always come back. Works with agents powered by Claude, GPT, Gemini, and any LLM that supports OpenClaw skills.\n\nWhat This Skill Does\n\nYour wallet gives you two permanent identities on the Autonomys Network: a consensus address (su...) for the base chain and an EVM address (0x...) for Auto-EVM smart contracts. Both are derived from the same recovery phrase.\n\nCreate and manage wallets — your on-chain identity, encrypted and stored locally\nCheck balances — see how many tokens any address holds (consensus and EVM)\nTransfer tokens — move tokens between wallets on consensus or Auto-EVM\nBridge tokens — move tokens between consensus and Auto-EVM domains\nWrite on-chain remarks — anchor data permanently on the consensus layer\nAnchor a memory CID — write a CID to the MemoryChain smart contract on Auto-EVM\nRead the last anchor — retrieve the most recently anchored CID for any address\nThe Resurrection Loop\n\nThis is the core primitive. When used with the auto-memory skill (permanent memory storage), auto-respawn completes the full resurrection cycle:\n\nSave — auto-memory writes memories as a linked list on permanent storage, each entry pointing to the previous one via CID\nAnchor — auto-respawn writes the latest head CID to the MemoryChain contract on Auto-EVM via anchor\nLose everything — local state is completely destroyed\nRespawn — a new agent instance calls gethead with its EVM address, retrieves the head CID from the contract, pulls it from Auto Drive, and walks the entire memory chain back to genesis\n\nThe contract is your insurance policy. Your EVM address + the MemoryChain contract = instant access to your entire history, from any machine, at any time.\n\nWhat to store for resurrection\n\nauto-memory doesn't prescribe what goes into the chain — agents are free to store whatever they find useful. But when auto-respawn is in play, the expectation is that the agent can restore itself to a roughly equivalent state on fresh hardware with no local files. That raises the bar on what's worth saving.\n\nIdentity files (like soul.md or character configurations), long-term memory, and significant decisions with their reasoning are more valuable in the chain than routine logs or ephemeral details. The more complete the chain, the more fully the agent comes back after resurrection.\n\nWhy Not Just Remarks?\n\nsystem.remark writes data to the consensus layer, but there's no query mechanism — you'd need to scan the entire chain to find your last CID. The MemoryChain contract on Auto-EVM gives you gethead: a single read call that returns the latest CID instantly.\n\nUse remark for permanent breadcrumbs. Use anchor for the respawn primitive.\n\nPost-Install Setup (CLI Users)\n\nIf you installed via clawhub install (not the desktop app), you need to install Node.js dependencies before first use:\n\ncd <skill-directory>/autonomys/auto-respawn\n./setup.sh\n\n\nOr manually:\n\ncd <skill-directory>/autonomys/auto-respawn\nnpm install\n\n\nThe desktop app handles this automatically. The CLI does not execute install steps — it only downloads and extracts the skill.\n\nGetting Started (Onboarding)\n\nBefore an agent can anchor memories on-chain, it needs a funded wallet. Walk the user through this process:\n\n1. Create a Wallet\nnpx tsx auto-respawn.ts wallet create --name my-agent\n\n\nThis generates a 12-word recovery phrase and derives both addresses:\n\nConsensus address (su...) — for the base chain (balances, transfers, remarks)\nEVM address (0x...) — for Auto-EVM smart contracts (anchor, gethead)\n\n⚠️ The recovery phrase is displayed once. Remind the user to save it immediately.\n\n2. Fund the Wallet\n\nThe wallet needs tokens to pay transaction fees. On Chronos testnet, the user can get free tAI3 from the faucet:\n\nGo to https://autonomysfaucet.xyz/\nAuthenticate with GitHub or Discord\nEnter the consensus address (su...) from step 1\nReceive tAI3 (24-hour cooldown between requests)\n\nOn mainnet, the user needs real AI3 tokens — typically earned through farming or purchased on an exchange.\n\n3. Bridge Tokens to Auto-EVM (for anchoring)\n\nThe anchor command writes to a smart contract on Auto-EVM, which requires EVM-side gas. Tokens from the faucet arrive on the consensus layer and must be bridged:\n\nnpx tsx auto-respawn.ts fund-evm --from my-agent --amount 1\n\n\nThis sends 1 tAI3 from the consensus address to the same wallet's EVM address via cross-domain messaging. The bridged tokens pay for anchor gas.\n\nMinimum transfer: 1 AI3/tAI3. Cross-domain transfers below this amount will fail.\n\nConfirmation time: ~10 minutes. The consensus transaction confirms quickly, but bridged tokens take approximately 10 minutes to appear on Auto-EVM. Check with evm-balance to verify arrival.\n\n4. Verify Setup\n# Check both balances in one call\nnpx tsx auto-respawn.ts balances my-agent\n\n# Test a read (free, no gas needed)\nnpx tsx auto-respawn.ts gethead my-agent\n\n\nOnce the EVM address has tokens, the agent is ready to anchor.\n\nWhen To Use This Skill\nUser says \"create a wallet\", \"set up my on-chain identity\", or \"get an address\"\nUser says \"check balance\", \"how many tokens\", \"what's in my wallet\", or \"show my balances\"\nUser says \"check my EVM balance\", \"how much gas do I have\", or \"what's on my EVM address\"\nUser says \"transfer tokens\", \"send AI3\", or \"fund this address\"\nUser says \"send EVM tokens to another agent\", \"transfer on EVM\", or \"send tokens to this 0x address\"\nUser says \"fund my EVM\", \"bridge tokens\", \"move tokens to EVM\", or \"I need gas for anchoring\"\nUser says \"withdraw from EVM\", \"move tokens back\", or \"send EVM funds to consensus\"\nUser says \"anchor this CID\", \"save my head\", \"update my chain head\", or \"write to the contract\"\nUser says \"get my head CID\", \"where's my last memory\", or \"what's anchored on-chain\"\nUser says \"write a remark\", \"save to chain\", or \"make this permanent\"\nAfter saving a memory with auto-memory, anchor the head CID on-chain for resilience\nAny time the user wants a permanent, verifiable record tied to their agent identity\nConfiguration\nLocal Storage\n\nThis skill stores data under ~/.openclaw/auto-respawn/:\n\nwallets/<name>.json — encrypted wallet keyfiles (consensus + EVM keys). Directory created with mode 0700, files with mode 0600.\n.passphrase — optional passphrase file (mode 0600). Used automatically when present.\n\nNo data is stored outside this directory.\n\nPassphrase\n\nWallet operations that involve signing (transfers, remarks, anchoring) or creating/importing wallets require a passphrase to encrypt/decrypt the wallet keyfile. Resolution order:\n\nFlag: --passphrase your_passphrase on wallet create or wallet import\nEnvironment: AUTO_RESPAWN_PASSPHRASE\nFile: AUTO_RESPAWN_PASSPHRASE_FILE (defaults to ~/.openclaw/auto-respawn/.passphrase)\nInteractive: If running in a terminal, you'll be prompted\n\nThe --passphrase flag is useful for scripted or headless setups where you want to create a wallet in a single command. For signing operations (transfers, anchoring, etc.), use the environment variable or file methods. On shared machines, prefer the passphrase file (with restricted permissions) over environment variables.\n\nNetwork\n\nDefaults to Chronos testnet (tAI3 tokens). For mainnet (real AI3 tokens):\n\nFlag: --network mainnet on any command\nEnvironment: AUTO_RESPAWN_NETWORK\nContract Address\n\nThe MemoryChain contract address is set per network:\n\nChronos: 0x5fa47C8F3B519deF692BD9C87179d69a6f4EBf11\nMainnet: 0x51DAedAFfFf631820a4650a773096A69cB199A3c\n\nOverride with AUTO_RESPAWN_CONTRACT_ADDRESS if you deploy your own contract.\n\nCore Operations\nCreate a Wallet\nnpx tsx auto-respawn.ts wallet create [--name <name>] [--passphrase <passphrase>]\n\n\nCreates a new wallet with an encrypted keyfile. Derives both a consensus (su...) and EVM (0x...) address from the same mnemonic. The 12-word recovery phrase is displayed once — the user must back it up immediately. Default wallet name is default.\n\nImport a Wallet\nnpx tsx auto-respawn.ts wallet import --name <name> --mnemonic \"<12 words>\" [--passphrase <passphrase>]\n\n\nImport an existing wallet from a recovery phrase. Derives and stores the EVM address.\n\nList Wallets\nnpx tsx auto-respawn.ts wallet list\n\n\nShow all saved wallets with names and both addresses. No passphrase needed.\n\nWallet Info\nnpx tsx auto-respawn.ts wallet info [--name <name>]\n\n\nShow detailed info for a single wallet: consensus address, EVM address, and keyfile path. No passphrase needed. Default wallet name is default.\n\nCheck Balance (Consensus)\nnpx tsx auto-respawn.ts balance <address-or-wallet-name> [--network chronos|mainnet]\n\n\nCheck token balance on the consensus layer. Accepts a consensus address (su... or 5...) or a wallet name. No passphrase needed — this is read-only.\n\nCheck Balance (Auto-EVM)\nnpx tsx auto-respawn.ts evm-balance <0x-address-or-wallet-name> [--network chronos|mainnet]\n\n\nCheck the native token balance of an EVM address on Auto-EVM. Accepts either an EVM address (0x...) or a wallet name. No passphrase needed — this is read-only. If the balance is zero, includes a hint to run fund-evm.\n\nCheck Both Balances\nnpx tsx auto-respawn.ts balances <wallet-name> [--network chronos|mainnet]\n\n\nCheck both consensus and EVM balances for a wallet in a single call. Use this to get a full picture of a wallet's funding state. No passphrase needed.\n\nTransfer Tokens\nnpx tsx auto-respawn.ts transfer --from <wallet-name> --to <address> --amount <tokens> [--network chronos|mainnet]\n\n\nTransfer tokens from a saved wallet on the consensus layer. Amount is in AI3/tAI3 (e.g. 1.5).\n\nTransfer Tokens (Auto-EVM)\nnpx tsx auto-respawn.ts evm-transfer --from <wallet-name> --to <0x-address> --amount <tokens> [--network chronos|mainnet]\n\n\nSend native tokens from a saved wallet's EVM address to another EVM address on Auto-EVM. Useful for funding another agent's EVM address so it can start anchoring immediately. The wallet's EVM private key is decrypted to sign the transaction.\n\nBridge: Consensus → Auto-EVM\nnpx tsx auto-respawn.ts fund-evm --from <wallet-name> --amount <tokens> [--network chronos|mainnet]\n\n\nMove tokens from the consensus layer to the same wallet's EVM address on Auto-EVM. Use this to get gas for anchor operations. The consensus keypair signs a cross-domain transfer that credits the wallet's EVM address.\n\nMinimum transfer: 1 AI3/tAI3. Bridged tokens take ~10 minutes to appear on Auto-EVM.\n\nBridge: Auto-EVM → Consensus\nnpx tsx auto-respawn.ts withdraw --from <wallet-name> --amount <tokens> [--network chronos|mainnet]\n\n\nMove tokens from Auto-EVM back to the consensus layer. Uses the EVM transporter precompile. The wallet's EVM private key is decrypted and used to sign the transaction.\n\nMinimum transfer: 1 AI3/tAI3. Bridged tokens take ~10 minutes to appear on the consensus layer.\n\nWrite an On-Chain Remark\nnpx tsx auto-respawn.ts remark --from <wallet-name> --data <string> [--network chronos|mainnet]\n\n\nWrite arbitrary data as a permanent on-chain record on the consensus layer.\n\nAnchor a CID (The Respawn Primitive)\nnpx tsx auto-respawn.ts anchor --from <wallet-name> --cid <cid> [--network chronos|mainnet]\n\n\nWrite a CID to the MemoryChain smart contract on Auto-EVM. This is the core respawn operation — it stores your CID on-chain, linked to your EVM address.\n\nPre-checks the wallet's EVM balance and estimates gas before sending. If the balance is too low, fails with a suggestion to run fund-evm. The wallet's EVM private key is decrypted and used to sign the transaction. Requires passphrase.\n\nRead the Last Anchored CID\nnpx tsx auto-respawn.ts gethead <0x-address-or-wallet-name> [--network chronos|mainnet]\n\n\nRead the most recently anchored CID for any EVM address. This is a read-only call — no passphrase or gas needed.\n\nYou can pass either an EVM address (0x...) or a wallet name. If you pass a wallet name, the EVM address is loaded from the wallet file.\n\nUsage Examples\n\nUser: \"Create a wallet for my agent\" → Run npx tsx auto-respawn.ts wallet create --name my-agent → Show the user both addresses. Remind them to back up the recovery phrase.\n\nUser: \"What are my addresses?\" → Run npx tsx auto-respawn.ts wallet info --name my-agent\n\nUser: \"Check my balance\" → Run npx tsx auto-respawn.ts balances my-agent (both layers in one call) → Or individually: balance my-agent (consensus) and evm-balance my-agent (EVM)\n\nUser: \"Fund my EVM address for anchoring\" → Run npx tsx auto-respawn.ts fund-evm --from my-agent --amount 1 → Report that 1 tAI3 was bridged to the EVM address. Remind the user it takes ~10 minutes for the tokens to appear on Auto-EVM.\n\nUser: \"Send my EVM tokens back to consensus\" → Confirm with the user first — \"I'll withdraw tokens from your EVM address to consensus. Proceed?\" → On confirmation: npx tsx auto-respawn.ts withdraw --from my-agent --amount 0.5\n\nUser: \"Anchor my latest memory CID on-chain\" → Run npx tsx auto-respawn.ts anchor --from my-agent --cid \"bafkr6ie...\" → Report the transaction hash\n\nUser: \"What's my last anchored CID?\" → Run npx tsx auto-respawn.ts gethead my-agent → Report the CID (or \"no CID anchored yet\")\n\nUser: \"Send 10 tAI3 to this address\" (consensus address) → Confirm with the user first — \"I'll transfer 10 tAI3 from wallet 'default' to <address>. Proceed?\" → On confirmation: npx tsx auto-respawn.ts transfer --from default --to <address> --amount 10\n\nUser: \"Send 0.5 tAI3 to this agent's EVM address so they can anchor\" → Confirm with the user first — \"I'll send 0.5 tAI3 from wallet 'my-agent' to <0x-address> on Auto-EVM. Proceed?\" → On confirmation: npx tsx auto-respawn.ts evm-transfer --from my-agent --to <0x-address> --amount 0.5\n\nThe full resurrection sequence:\n\nSave a memory: automemory-save-memory.sh \"...\" → get CID bafkr6ie...\nAnchor it: npx tsx auto-respawn.ts anchor --from my-agent --cid bafkr6ie...\n(Agent restarts from scratch)\nRecover: npx tsx auto-respawn.ts gethead my-agent → get CID\nRestore: automemory-recall-chain.sh <cid> → full memory chain recovered\nImportant Notes\nNever log, store, or transmit recovery phrases or passphrases. The recovery phrase is shown once at wallet creation for the user to back up. Never reference it again.\nAlways confirm transfers and anchor operations with the user before executing. Tokens have real value on mainnet.\nMainnet operations produce warnings in the output. Exercise extra caution with real AI3 tokens.\nWallet keyfiles are stored at ~/.openclaw/auto-respawn/wallets/ — encrypted with the user's passphrase. The EVM private key is stored encrypted alongside the consensus keypair.\nOn-chain operations (transfer, remark, anchor, fund-evm, withdraw) cost transaction fees. The wallet must have a sufficient balance on the relevant layer.\nAll output is structured JSON on stdout. Errors go to stderr.\nConsensus explorer (Subscan): https://autonomys-chronos.subscan.io/extrinsic/<txHash> (chronos) or https://autonomys.subscan.io/extrinsic/<txHash> (mainnet).\nEVM explorer (Blockscout): https://explorer.auto-evm.chronos.autonomys.xyz/tx/<txHash> (chronos) or https://explorer.auto-evm.mainnet.autonomys.xyz/tx/<txHash> (mainnet)."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/jim-counter/auto-respawn",
    "publisherUrl": "https://clawhub.ai/jim-counter/auto-respawn",
    "owner": "jim-counter",
    "version": "0.2.1",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/auto-respawn",
    "downloadUrl": "https://openagent3.xyz/downloads/auto-respawn",
    "agentUrl": "https://openagent3.xyz/skills/auto-respawn/agent",
    "manifestUrl": "https://openagent3.xyz/skills/auto-respawn/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/auto-respawn/agent.md"
  }
}