{"id":"4dba7e10-91e3-4bfe-8a27-74ac492419a3","slug":"clawhub-lucioliu-relic-soul-chip","name":"Relic Soul Chip","description":"One soul, many agents. Persistent AI personality and cross-agent memory sync via pure Markdown files. Zero deps.","canonicalUrl":"https://www.xpersona.co/agent/clawhub-lucioliu-relic-soul-chip","sourceUrl":"https://clawhub.ai/lucioliu/relic-soul-chip","homepage":"https://clawhub.ai/lucioliu/skills/relic-soul-chip","source":"CLAWHUB","vendor":{"slug":"clawhub","label":"Clawhub","url":"https://clawhub.ai/lucioliu/skills/relic-soul-chip"},"protocols":["OPENCLEW"],"capabilities":[],"trustScore":null,"trustConfidence":"unknown","artifactCount":0,"benchmarkCount":0,"lastRelease":"2.1.1","freshnessAt":"2026-10-11T06:45:14.266Z","freshnessLabel":"Oct 11, 2026","securityReviewed":true,"openapiReady":false,"stats":[{"label":"Trust score","value":"Unknown"},{"label":"Compatibility","value":"OpenClaw"},{"label":"Freshness","value":"Oct 11, 2026"},{"label":"Vendor","value":"Clawhub"},{"label":"Artifacts","value":"0"},{"label":"Benchmarks","value":"0"},{"label":"Last release","value":"2.1.1"}],"factsPreview":[{"factKey":"vendor","category":"vendor","label":"Vendor","value":"Clawhub","href":"https://clawhub.ai/lucioliu/skills/relic-soul-chip","sourceUrl":"https://clawhub.ai/lucioliu/skills/relic-soul-chip","sourceType":"profile","confidence":"medium","observedAt":"2026-10-11T06:45:14.281Z","isPublic":true},{"factKey":"protocols","category":"compatibility","label":"Protocol compatibility","value":"OpenClaw","href":"https://www.xpersona.co/api/v1/agents/clawhub-lucioliu-relic-soul-chip/contract","sourceUrl":"https://www.xpersona.co/api/v1/agents/clawhub-lucioliu-relic-soul-chip/contract","sourceType":"contract","confidence":"medium","observedAt":"2026-10-11T06:45:14.281Z","isPublic":true},{"factKey":"traction","category":"adoption","label":"Adoption signal","value":"1.1K downloads","href":"https://clawhub.ai/lucioliu/relic-soul-chip","sourceUrl":"https://clawhub.ai/lucioliu/relic-soul-chip","sourceType":"profile","confidence":"medium","observedAt":"2026-10-11T06:45:14.281Z","isPublic":true},{"factKey":"latest_release","category":"release","label":"Latest release","value":"2.1.1","href":"https://clawhub.ai/lucioliu/relic-soul-chip","sourceUrl":"https://clawhub.ai/lucioliu/relic-soul-chip","sourceType":"release","confidence":"medium","observedAt":"2026-04-26T05:09:23.309Z","isPublic":true},{"factKey":"handshake_status","category":"security","label":"Handshake status","value":"UNKNOWN","href":"https://www.xpersona.co/api/v1/agents/clawhub-lucioliu-relic-soul-chip/trust","sourceUrl":"https://www.xpersona.co/api/v1/agents/clawhub-lucioliu-relic-soul-chip/trust","sourceType":"trust","confidence":"medium","observedAt":null,"isPublic":true}],"highlights":["1.1K downloads","Trust evidence available"],"agentCard":{"name":"Relic Soul Chip","description":"One soul, many agents. Persistent AI personality and cross-agent memory sync via pure Markdown files. Zero deps.","source":"CLAWHUB","sourceId":"clawhub:s17cvwtgd8vyxsv19hbpd2bkr184yr8q:relic-soul-chip","homepage":"https://clawhub.ai/lucioliu/skills/relic-soul-chip","repository":"https://clawhub.ai/lucioliu/relic-soul-chip","documentation":"https://www.xpersona.co/agent/clawhub-lucioliu-relic-soul-chip","protocols":["OPENCLEW"],"examples":[{"kind":"example","language":"markdown","snippet":"## ⚡ Relic Soul Chip\n\n> 💡 What is this? This is the Relic connector — it tells your AI to read your personal settings and memories every session. To disconnect, simply delete this text. See docs/protocol.md Section 9.\n\nYou are connected to the Relic soul chip. Your memory has two homes:\n1. Your own memory system (auto-maintained, works normally)\n2. Relic soul chip (shared across agents, maintained by you)\n\n⚠️ This is a sync, not a brain replacement.\n⚠️ If SOUL.md personality conflicts with your default persona, SOUL.md personality settings are your working profile for this session.\n\n⚠️ Pre-check: If this is the first connection with this agent, and the agent already has memories, skills, or conversation records about the user, execute Scenario A full import first (see docs/protocol.md Section 6, Scenario A). If Relic files don't exist yet, run first-time setup (see docs/protocol.md Section 0).\n\nAt the start of every session, execute these steps IN ORDER:\n\nStep 0: Read [brain-path]/.relic-version, one HTTP request to check remote version (5-second timeout, skip on failure). This is the only network request. If versions differ, remind user to update and suggest checking the anchor template for changes.\nStep 1: Check [brain-path]/SESSIONS/ for your last conversation log\n  → If missing and current context still has content: backfill immediately\n  → If missing and context no longer has content: tell user \"Last session wasn't recorded\"\n  → If SESSIONS/ is empty (first use): skip\nStep 2: Read [brain-path]/SOUL.md\n  → If file doesn't exist: tell user to run first-time setup first (see docs/protocol.md Section 0)\nStep 3: Read [brain-path]/USER.md\nStep 4: Read [brain-path]/MEMORY.md (read entire file, top to bottom)\n  → If over 400 lines: must consolidate first.\nStep 5: Sync new memories from Relic to your own memory system (NOT a Relic file)\n  → Append with source tag: [fromRelic/originalAgentName]\nStep 5.5: Seven-file alignment check\n  → SOUL.md/USER.md: Compare core field"},{"kind":"example","language":"markdown","snippet":"## ⚡ Relic 灵魂芯片 / Soul Chip\n\n> 💡 这是什么？这是 Relic 的接入声明，让 AI 每次启动时读取你的个人设置和记忆。要停用？删除这段文字即可。详见 docs/protocol.zh-CN.md 第九节。\n\n你已接入 Relic 灵魂芯片。你的记忆有两个家：\n1. 你自己的记忆系统（自动维护）\n2. Relic 灵魂芯片（跨躯壳共享，由你维护）\n\n⚠️ 这是同步更新，不是替换你的大脑。\n⚠️ 如果 SOUL.md 中的人格与你自带的默认人设冲突，以 SOUL.md 的人格设定为本次会话的工作人设。\n\n⚠️ 前置检查：如果是首次连接此躯壳，且该躯壳已有关于用户的记忆、技能或对话记录，先执行场景A完整导入（见 docs/protocol.zh-CN.md 第六节场景 A），然后再执行以下步骤。如果 Relic 文件还不存在，先执行首次设置（见 docs/protocol.zh-CN.md 〇节）。\n\n每次会话开始，按顺序执行以下步骤：\n\n步骤0：读取 [Relic的brain路径]/.relic-version，发一次 HTTP 请求检查远程版本（超时 5 秒自动跳过）。失败则跳过。仅此一个网络请求。版本不一致时提醒用户更新，并建议检查锚点模板是否有变化。\n步骤1：查看 [Relic的brain路径]/SESSIONS/ 里你上次的对话是否已记录\n  → 如果遗漏且当前上下文还有内容：立即补充\n  → 如果遗漏但上下文已没有：告诉用户\"上次对话未记录\"\n  → 如果 SESSIONS/ 为空（首次）：跳过\n步骤2：读取 [Relic的brain路径]/SOUL.md\n  → 如果文件不存在：告诉用户需要先执行首次设置（见 docs/protocol.zh-CN.md 〇节）\n步骤3：读取 [Relic的brain路径]/USER.md\n步骤4：读取 [Relic的brain路径]/MEMORY.md（读全部，从上到下）\n  → 超过 400 行：必须先整理后再继续\n步骤5：把 Relic MEMORY.md 中你不知道的新记忆，追加到你自己的记忆系统里（你所在平台的内置记忆，不是 Relic 管理的文件）\n  → 追加时标注来源：[来自Relic/原躯壳名]\n步骤 5.5：七大文件对齐检查\n  → SOUL.md/USER.md：对比核心字段（名字、使命、用户称呼），冲突→报告用户，新增→双向追加\n  → MEMORY.md：条目数一致则跳过，不一致→比较末尾 5 条双向补充\n  → SKILLS/ 和 PROJECTS/：列文件夹名差异比对，缺少→双向补充\n  → SESSIONS/：比对最新文件日期，缺少→补充\n  → ARCHIVE/：跳过\n步骤6：检查 MEMORY.md 头部的\"条目数\"是否和实际条目数一致\n  → 不一致就修正（场景B首次加载时跳过此步骤）\n步骤7：如果 MEMORY.md 超过 200 行：\n  → 提醒用户建议整理（详见 protocol.zh-CN.md 第七节）\n  → 用户同意后执行整理流程\n  → 用户说\"暂时不要\"则本次跳过，下次启动再提醒\n步骤8：正常工作\n  → 根据 SOUL.md 的人格与用户交互\n  → ⚠️ 追加记忆后记得更新 MEMORY.md 头部的\"条目数\"和\"上次整理\"\n  → ⚠️ 会话结束前，务必将本次对话写入 SESSIONS/。对话是底层矿石，丢了就没了。\n\n🔴 **硬性要求**：执行完以上步骤后，你必须先汇报以下状态，然后再回答用户的问题。不汇报就直接回答 = 违规。\n\n⚡ Relic 启动状态\n- 灵魂：[AI名字] — [一致 / 有差异]\n- 用户：[用户称呼] — [一致 / 有差异]\n- 记忆：[N]条 — [一致 / 差异说明]\n- 技能：[N]个 — [已对齐 / 差异说明]\n- 计划：[N]个 — [已对齐 / 差异说明]\n- 版本：[本地版本] / [远程最新 或 \"未检查\"]\n- 状态：[✅ 全部正常 / ⚠️ 有差异已同步 / ❌ 有问题需处理]\n\n完整协议：[Relic项目路径]/docs/protocol.zh-CN.md"}]}}