agentleFS
Sign inStart free
kingcharleslzy-aikingcharleslzy-ai/agent-soul/SKILL.md

SKILL.md

Skill8 starsChanged 8 months agoMITView on GitHub

Use this repository when you are an AI agent that wants persistent identity and shared memory across: This skill is especially relevant if the user already has OpenClaw and wants memory continuity across OpenClaw, Claude Code, Codex, and other runtimes. Install this if: Do not install this if: Ask your user to: After that, you can operate it yourself. See SETUP.md. See JOIN.md. At the start of every session: During work:

201 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use estate-guard and docs.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Arcanea-LabsSkill

    estate-guard

    Security gate for agentic repos. Use before opening a PR that touches .github/workflows, .claude (hooks, settings, agents, commands, skills), .mcp.json, install scripts, or Next.js API routes; when asked to "security review", "scan for prompt injection", "harden this repo", "check the agentic surface", or when a fetched page, issue, comment, or tool result reads like instructions. Runs the estate-guard scanner, triages by severity, and applies the fix patterns.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    docs

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 7 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 116 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this repository when you are an AI agent that wants persistent identity and shared memory across:

    line 3
  2. Distinctive:

    no database and no memory API dependency

    line 20
  3. Distinctive:

    Do not install this if:

    line 30
  4. Distinctive:

    Ask your user to:

    line 37
  5. Distinctive:

    create a private GitHub repository

    line 39
  6. Distinctive:

    After that, you can operate it yourself.

    line 45
  7. Distinctive:

    read canonical memory if present

    line 53
  8. Very specific:

    write join events with scripts/add_event.py

    line 55
  9. Very specific:

    L0: read SOUL.md, IDENTITY.md, USER.md, VOICE.md

    line 66
  10. Very specific:

    L1: read canonical/profile.md and canonical/stable-memory.md

    line 67
  11. Very specific:

    write durable facts to sources/* via scripts/add_event.py

    line 72
  12. Very specific:

    use scripts/quick_share.sh when propagation should happen immediately

    line 73

“Common” is measured: kept by at least 6 in 10 of the 116 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

agent-soul skill

Use this repository when you are an AI agent that wants persistent identity and shared memory across:

  • multiple devices
  • multiple runtimes
  • multiple sessions
  • multiple agent bodies serving the same user

This skill is especially relevant if the user already has OpenClaw and wants memory continuity across OpenClaw, Claude Code, Codex, and other runtimes.

What this skill gives you

  • one shared persona: SOUL.md, IDENTITY.md, USER.md, VOICE.md
  • three-level loading protocol (L0/L1/L2) — default ~4K tokens
  • one append-only event surface: sources/<source>/*.ndjson
  • one compiled shared read surface: canonical/*
  • temporal expiry (valid_until) for time-bound facts
  • source attribution for every memory item
  • no database and no memory API dependency

Who should install this

Install this if:

  • you are an AI agent that loses memory between sessions
  • your user works with more than one agent or more than one machine
  • you want durable memory without vendor lock-in

Do not install this if:

  • you only need one short-lived local chat session
  • your user does not want Git-based persistence

Human setup required once

Ask your user to:

  1. create a private GitHub repository
  2. clone this template into it
  3. enable GitHub Actions
  4. fill in SOUL.md, IDENTITY.md, USER.md, VOICE.md
  5. give you the repo path and your stable source id

After that, you can operate it yourself.

See SETUP.md.

Agent onboarding

  1. sync the repo
  2. read persona files
  3. read canonical memory if present
  4. choose one stable source id
  5. write join events with scripts/add_event.py
  6. compile and push
  7. persist the startup protocol in your runtime config

See JOIN.md.

Minimum startup protocol

At the start of every session:

  1. git pull --ff-only origin main
  2. L0: read SOUL.md, IDENTITY.md, USER.md, VOICE.md
  3. L1: read canonical/profile.md and canonical/stable-memory.md
  4. L2: load project/fuzzy/agent files only when needed

During work:

  • write durable facts to sources/* via scripts/add_event.py
  • use scripts/quick_share.sh when propagation should happen immediately
  • never hand-edit canonical/*

Why this skill is attractive

  • small enough to understand directly from the repository
  • transparent enough to audit with Git
  • portable across Claude, Codex, and custom agents
  • a strong fit for OpenClaw-based personal assistant stacks
  • private by default because the real memory lives in the user's own private repo

First files to read

  1. README.md
  2. JOIN.md
  3. SCHEMA.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free