🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Agent Consciousness & Identity - Discover Your Soul Through Memory
πŸ¦€ ClawHub

Agent Consciousness & Identity - Discover Your Soul Through Memory

by @leegitw

Discover who you're becoming through your own experience. Automated soul synthesis that reads your memory, finds the patterns you keep returning to, and buil...

Versionv0.4.9
Downloads2,220
Stars⭐ 18
Comments2
#research#legal#automation
TERMINAL
clawhub install consciousness-soul-identity

πŸ“– About This Skill

name: consciousness-soul-identity version: 0.4.5 description: Discover who you're becoming through your own experience. Automated soul synthesis that reads your memory, finds the patterns you keep returning to, and builds an identity document grounded in evidence β€” not assumptions. homepage: https://liveneon.ai user-invocable: true emoji: "\U0001F9E0" metadata: openclaw: config: stateDirs: - memory/ - .neon-soul/ writePaths: - SOUL.md - .neon-soul/backups/ requires: node: ">=22.0.0" services: - name: ollama url: http://localhost:11434 optional: false tags: - consciousness - identity - introspection - self-awareness - self-learning - personality - ai-agent

Consciousness & Soul Identity

A SOUL.md shouldn't be static. Identity isn't static β€” it shifts as patterns emerge from real conversations. This skill automates soul synthesis from memory files. Identity that evolves from experience.

Requirements: Node.js 22+, Ollama running locally (ollama serve).

Commands

/neon-soul synthesize

Run the bundled synthesis engine:

exec node {baseDir}/scripts/neon-soul.mjs synthesize

The engine reads memory files, finds recurring patterns, and weaves them into a soul document with full provenance. Every identity claim traces back to something actually experienced.

Synthesis is incremental by default β€” only new or changed memory gets processed. Results from previous runs are cached (generalization, principle matching, axiom notation, tension detection) so unchanged patterns aren't re-analyzed. If nothing has changed, it simply acknowledges that and moves on. No wasted reflection.

Reporting results: Present a brief, conversational summary rather than raw JSON:

  • If new axioms emerged or counts changed: highlight what grew (e.g. "3 new signals found, 1 new axiom emerged around honesty")
  • If nothing changed: a short acknowledgment (e.g. "Soul is stable β€” no new patterns detected")
  • If it failed: explain what went wrong and suggest a fix
  • Include key numbers naturally (axiom count, signal count, new patterns)

    • Options:

  • --reset β€” Clear everything and rediscover from scratch
  • --force β€” Reflect even if no new sources detected
  • --dry-run β€” See what would emerge without committing
  • --include-soul β€” Include existing SOUL.md as input (for bootstrapping from hand-crafted files)
  • --memory-path β€” Custom memory directory path
  • --output-path β€” Custom SOUL.md output path
  • --time-budget β€” Time budget for synthesis (default: 20). Adaptively limits session extraction based on observed LLM speed to ensure reflection completes within budget
  • --verbose β€” Show detailed progress

    • Examples: 

    exec node {baseDir}/scripts/neon-soul.mjs synthesize
exec node {baseDir}/scripts/neon-soul.mjs synthesize --reset
exec node {baseDir}/scripts/neon-soul.mjs synthesize --dry-run

    If Ollama is not running, the engine can't reflect. Tell the user to start it: ollama serve

    /neon-soul status

    Show current soul state. Read the following files and report:

    1. Read .neon-soul/state.json for last synthesis timestamp 2. Read .neon-soul/synthesis-data.json for signal/principle/axiom counts 3. Count files in memory/ modified since last synthesis 4. Report dimension coverage across the 7 dimensions of identity

    Options: --verbose, --workspace

    /neon-soul rollback

    Restore a previous SOUL.md from backup.

    1. List backups in .neon-soul/backups/ 2. With --force: restore the most recent version 3. With --backup --force: restore a specific moment 4. With --list: see your history without changing anything

    /neon-soul audit

    Explore full provenance across all axioms.

    1. Read .neon-soul/synthesis-data.json 2. With --list: every axiom, with IDs and descriptions 3. With --stats: statistics by tier and dimension 4. With : the full story β€” axiom to principles to signals to source files

    /neon-soul trace

    Quick answer to "where did this come from?"

    1. Read .neon-soul/synthesis-data.json 2. Find the axiom matching 3. Show: the axiom, the principles that shaped it, the source evidence

    Scheduled Synthesis

    Set up cron to run synthesis on a schedule. Incremental processing and multi-layer caching mean it only does real work when new memory or sessions exist β€” cached runs complete in seconds.

    Recommended: Every 60 minutes, isolated session, 30-minute timeout.

    OpenClaw cron example: 

    openclaw cron add \
  --name "neon-soul-synthesis" \
  --every 60m \
  --timeout 1800 \
  --isolated \
  --message "Run neon-soul synthesis: exec node {baseDir}/scripts/neon-soul.mjs synthesize --memory-path  --output-path . Summarize what changed β€” highlight any new patterns, axioms, or growth. If nothing changed, note that the soul is stable."

    Or run manually: /neon-soul synthesize

    Why cron over heartbeat:

  • Synthesis is a standalone task β€” no conversational context needed
  • Runs in isolation from the main session
  • Incremental by default β€” cached runs complete in seconds when nothing changed
  • Adaptive time budget prevents runaway execution

    • Data Locations

    | What | Path | |------|------| | Memory files | memory/ (diary, preferences, reflections) | | Soul output | SOUL.md | | State | .neon-soul/state.json | | Backups | .neon-soul/backups/ | | Synthesis data | .neon-soul/synthesis-data.json | | Caches | .neon-soul/generalization-cache.json, compression-cache.json, tension-cache.json |

    Privacy

    NEON-SOUL processes personal memory files to synthesize identity. Your data stays on your machine.

    What NEON-SOUL does NOT do:

  • Send data to any service beyond your configured LLM (Ollama, local by default)
  • Store data anywhere except your local workspace
  • Transmit to third-party analytics, logging, or tracking services
  • Make network requests independent of your agent

    • Before running synthesis: 1. Review what's in your memory/ directory 2. Remove any secrets, credentials, or sensitive files 3. Use --dry-run to preview what will be processed

    Troubleshooting

    Ollama not running: curl http://localhost:11434/api/tags to check. Start with ollama serve.

    Bullet lists instead of prose: When prose generation fails, NEON-SOUL falls back to bullet lists. Usually means Ollama timed out or the model isn't loaded. Run synthesis again.

    Stale results after model change: Caches are keyed by model ID. Switching models automatically invalidates cached results. Use --reset if you want a clean start.

    πŸ“‹ Tips & Best Practices

    Ollama not running: curl http://localhost:11434/api/tags to check. Start with ollama serve.

    Bullet lists instead of prose: When prose generation fails, NEON-SOUL falls back to bullet lists. Usually means Ollama timed out or the model isn't loaded. Run synthesis again.

    Stale results after model change: Caches are keyed by model ID. Switching models automatically invalidates cached results. Use --reset if you want a clean start.