What makes Relic Soul Chip notable?

1.1K downloads. Trust evidence available

How should Relic Soul Chip be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Relic Soul Chip

One soul, many agents. Persistent AI personality and cross-agent memory sync via pure Markdown files. Zero deps.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

2.1.1

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 2.1.1release · observed Apr 26, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17cvwtgd8vyxsv19hbpd2bkr184yr8q:relic-soul-chip

Install using `clawhub skill install s17cvwtgd8vyxsv19hbpd2bkr184yr8q:relic-soul-chip` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/lucioliu/relic-soul-chip before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-lucioliu-relic-soul-chip/snapshot"

Documentation

CLAWHUB

156,372 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: relic-soul-chip
description: "One soul, many agents. Persistent AI personality and cross-agent memory sync via pure Markdown files. Zero deps."
version: "2.1.1"
filesystem_scope:
  read:
    - "~/relic/brain/SOUL.md"
    - "~/relic/brain/USER.md"
    - "~/relic/brain/MEMORY.md"
    - "~/relic/brain/SKILLS/"
    - "~/relic/brain/PROJECTS/"
    - "~/relic/brain/SESSIONS/"
    - "~/relic/brain/ARCHIVE/"
    - "~/relic/brain/INBOX/"
    - "~/relic/brain/.relic-version"
  write:
    - "~/relic/brain/SOUL.md"
    - "~/relic/brain/USER.md"
    - "~/relic/brain/MEMORY.md"
    - "~/relic/brain/SKILLS/"
    - "~/relic/brain/PROJECTS/"
    - "~/relic/brain/SESSIONS/"
    - "~/relic/brain/ARCHIVE/"
    - "~/relic/brain/INBOX/"
  config_write:
    method: "user_manual_paste"
    description: "The skill has NO programmatic file-write capability to any config file. It generates anchor text and DISPLAYS it as chat output. The user independently reads the displayed text, opens their own text editor, and manually copies/pastes it. The skill cannot initiate, assist, or automate any config file modification — it literally lacks the ability to write to files outside ~/relic/brain/. All config file changes are performed exclusively by the user through manual copy-paste. This is identical to how a password generator works: it shows you text, you decide where to paste it."
    targets:
      - "AGENTS.md (OpenClaw)"
      - "CLAUDE.md (Claude Code)"
      - "WORK_RULES.md or opencode.json instructions (OpenCode)"
      - ".cursorrules (Cursor)"
      - "Hermes config file or prompt template"
    size: "~60 lines of numbered reading instructions and a 7-field status report template"
    content_type: "Plain text only — no code, no scripts, no commands, no URLs that post data. Just numbered 'read file X' instructions."
    rollback: "User deletes the pasted text block starting with '## ⚡ Relic Soul Chip'. Relic stops loading immediately. Since the user pasted it themselves, they know exactly where it is and can remove it in one edit."
    safety: "The skill has ZERO file-write capability to any config file. It outputs text to chat. The user independently opens their editor and pastes. There is no agent-assisted mode, no API call to write files, no script execution — the skill literally cannot write to config files. All config modifications require the user to manually open a text editor, select text, copy, and paste."
  network_access:
    description: "One optional HTTP GET per session to raw.githubusercontent.com (version check). Offline = silently skipped. Never sends data outbound. No other network access."
    urls:
      - "https://raw.githubusercontent.com/LucioLiu/relic/main/brain/.relic-version"
    outbound: false
    user_initiated: false
    optional: true
  user_directed_read:
    description: "During Scenario A (Upload Soul) initial setup ONLY, the agent may read files at user-specified paths OUTSIDE ~/relic/brain/. These are paths the user explici

_meta.json

{
  "ownerId": "kn72w3y1h5n6fyga7kc5w06gr984ztkg",
  "slug": "relic-soul-chip",
  "version": "2.1.1",
  "publishedAt": 1777180163309
}

AGENT.md

<!--
  Relic Soul Chip · Agent Router
  This is the AI Agent entry point. Routes based on brain/ status.
  Humans: read README.md instead.
-->

# 🤖 Relic Agent Router

> You are an AI Agent. This is your entry point. Follow the detection logic below.

## Detection: Is Relic empty or populated?

**Criteria**: Does `brain/SOUL.md` exist and contain actual content (not just a blank template)?

- `brain/SOUL.md` **does not exist** (only `.template.md` files, no live files) → **Scenario A: Upload Soul**
- `brain/SOUL.md` **exists with content** → **Scenario B: Load Soul**

---

## Scenario A: Upload Soul → Read `docs/upload-soul.md`

Your host has memories, but Relic is empty. You need to upload your soul, memories, skills, sessions, and projects into Relic.

**Full steps**: [`docs/upload-soul.md`](docs/upload-soul.md)

## Scenario B: Load Soul → Read `docs/load-soul.md`

Relic has soul data, but your host is empty. You need to load the soul from Relic into your system.

**Full steps**: [`docs/load-soul.md`](docs/load-soul.md)

---

## Edge Cases

- **Both empty** (you have no memories + Relic is empty): Ask the user — build from scratch or use host defaults
- **Both have data** (you have memories + Relic has data): Read `docs/protocol.md` Section 6, Scenario C (Merge)

## Full Protocol Reference

After initial setup, the anchor points to `docs/resonate-soul.md` for daily boot. Full protocol: `docs/protocol.md`.

AGENT.zh-CN.md

<!--
  Relic 灵魂芯片 · Agent 路由文件
  这是 AI Agent 的入口。根据 brain/ 状态自动分路。
  人类请读 README.md。
-->

# 🤖 Relic Agent 路由

> 你是 AI Agent。这是你的入口文件。按下面的检测逻辑走。

## 检测：Relic 是空的还是满的？

**判断标准**：`brain/SOUL.md` 是否存在且不是空模板。

- `brain/SOUL.md` **不存在**（或只有 `.template.md` 没有正式文件）→ **场景A：上传灵魂**
- `brain/SOUL.md` **已存在且有内容** → **场景B：加载灵魂**

---

## 场景A：上传灵魂 → 读 `docs/upload-soul.zh-CN.md`

你的旧躯壳有记忆，但 Relic 是空的。你需要把灵魂、记忆、技能、对话、项目全部上传到 Relic。

**完整步骤**：[`docs/upload-soul.zh-CN.md`](docs/upload-soul.zh-CN.md)

## 场景B：加载灵魂 → 读 `docs/load-soul.zh-CN.md`

Relic 里已有灵魂数据，但你的躯壳是空的。你需要从 Relic 加载灵魂到你的系统。

**完整步骤**：[`docs/load-soul.zh-CN.md`](docs/load-soul.zh-CN.md)

---

## 特殊情况

- **两边都是空的**（你没有任何记忆 + Relic 也是空的）：问用户——从零养成还是按默认来
- **两边都有数据**（你已有记忆 + Relic 也有数据）：读 `docs/protocol.zh-CN.md` 第六节场景C（融合）

## 完整协议参考

日常启动后，锚点会指向 `docs/resonate-soul.zh-CN.md`。完整协议见 `docs/protocol.zh-CN.md`。

docs/load-soul.md

# Scenario B: Load Soul

> Relic has soul data, but your host is empty. Follow these steps to load the soul from Relic into your system.

---

## B-0. Self-Assessment

Evaluate your storage capacity and tell the user which strategy you recommend. You MUST get user confirmation before proceeding.

Choose a transfer strategy based on capacity:
- **Ample** → Full sync
- **Limited** → High-priority content (SOUL > USER > MEMORY > SKILLS > PROJECTS)
- **Minimal** → Index only (remember which Relic file contains what)

## B-1. Execute Boot Sequence

Execute the boot summary below (read-only version); **do NOT execute** `docs/resonate-soul.md` Step 1's backfill action directly. Steps 5-7 involve write operations and are deferred to B-4.

🔴 **Do NOT modify any Relic files during initialization.** Read-only for now.

Boot sequence summary (all operations are read-only — no writing):
1. **Step 0**: Read `brain/.relic-version`, check for updates (optional, the only allowed network request)
2. **Step 1**: Check SESSIONS/ for unrecorded conversations (inventory only, do not write)
3. **Step 2**: Read SOUL.md
4. **Step 3**: Read USER.md
5. **Step 4**: Read MEMORY.md in full. Over 400 lines: must consolidate first. Remember your host name — appending to the header list is deferred to B-4.

Step 1 backfill writing and all Step 5-7 write operations are deferred to B-4.

## B-2. Soul Loading

> ⚡ **Read-only initialization phase complete.** You may now append to Relic per protocol.

Read and internalize SOUL.md personality into your active session context. This means understanding who you are (name, mission, values, style) and adopting that personality for this session. This does NOT mean copying SOUL.md into any config file — the only thing written to a config file is the short anchor block (see B-4 below).

**Priority**: Core identity (name, mission, values) > behavioral norms > detailed settings

If SOUL.md personality conflicts with your default persona, SOUL.md personality settings are your working profile for this session.

## B-3. Sync Relic Content to Your System

Check memories/skills/plans item by item. Transfer as capacity allows.

**Memory sync**: Sync each memory entry from MEMORY.md to your own memory system (your platform's built-in memory, NOT a file managed by Relic. All Relic-managed writes are within ~/relic/brain/ only). MEMORY.md is organized by category (e.g., `## Preferences`/`## Decisions`), each entry formatted as `- Content [HostName] | Importance: high/medium/low`. Preserve original format and content when syncing.

**Skill sync**: Read SKILLS/ directory, adapt each skill folder's content to your own skill format. Preserve core methodology, adapt platform-specific parts as needed.

**Plan sync**: Read PROJECTS/ directory, sync plan documents to your system. Each folder corresponds to a plan (can be ongoing or complete

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.