Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
v2.1.1: Cleaned up general-purpose release - removed all personal references and hardcoded personas, now fully generic SOUL.md injector for any OpenClaw user
What This Skill Does
Reads a workspace SOUL.md file and patches its contents into OpenClaw's compiled core system prompt. Tracks version changes and content hashes to avoid redundant writes. Survives OpenClaw updates that would otherwise overwrite the dist/ directory.
Patching the compiled JS directly means persona changes take effect immediately without forking or maintaining a separate OpenClaw build.
When to use it
- Reapplying persona after a global OpenClaw npm update
- Pushing SOUL.md edits into the active system prompt without restarting
- Verifying the current patch state before a demo or session
- Force-repatching when prompt behavior feels off after an update
- Automating persona sync in a post-install script
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Sync my SOUL.md to the core prompt
- 1Reads SOUL.md from ~/.openclaw/workspace/SOUL.md
- 2Checks .patcher-state.json for current OpenClaw version and last SOUL.md hash
- 3Compares stored hash against current file hash to detect changes
- 4Locates injection point in OpenClaw's compiled JS
- 5Writes patched file and updates .patcher-state.json with new version and hash
Core system prompt updated with current SOUL.md content; state file records the patch
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.