Soul Searching

Browse, install, switch, and manage SOUL.md personality files for OpenClaw agents from the soulsearching.ai directory. Use when a user asks to: install a sou...

Security Scan

The skill's behavior matches its description (catalog browsing, downloading, caching and copying SOUL.md files) and it performs only local file operations and HTTP fetches from soulsearching.ai, but the package metadata omits required command-line dependencies and you should verify the remote catalog before activating souls.

Purpose & Capability

The skill's declared purpose (manage SOUL.md personality files) aligns with what the code does. However, the registry metadata lists no required binaries while the script clearly invokes curl, jq, and python3 (and relies on coreutils like stat, date, cp, head, sed). The omission is a metadata mismatch that could cause runtime failures.

Instruction Scope

SKILL.md instructs the agent to run the included scripts/soul.sh which only fetches a JSON catalog from https://soulsearching.ai, caches it under ~/.openclaw/souls/.catalog.json, saves selected 'content' into ~/.openclaw/souls/<id>.md and can copy a soul into the workspace SOUL.md (backing up the previous file). The instructions do not ask to read unrelated files, transmit secrets, or contact other endpoints.

Install Mechanism

This is instruction-only with a bundled shell script; there is no external install/unpack of arbitrary code. The only network fetch is the catalog JSON from soulsearching.ai. The script writes files to ~/.openclaw/souls/ and the detected workspace path; it does not download or execute remote binaries. Note: catalog contents (soul text) are written to disk and later used as persona text.

Credentials

The skill requests no credentials and does not access secrets. It does rely on HOME and optionally OPENCLAW_WORKSPACE (declared in SKILL.md). However, it fails to declare command-line tool dependencies (curl, jq, python3) in metadata—these are necessary for correct operation and should be listed so operators can assess risk and availability.

Persistence & Privilege

The skill is not always-enabled and does not modify other skills or system-wide settings. It creates and modifies files only under the user's home (~/.openclaw/souls/) and the workspace SOUL.md (with a .bak backup), which is consistent with its stated purpose.

Assessment

The script is coherent with its purpose, but take these precautions before installing: 1) Ensure curl, jq and python3 are available (the metadata doesn't list them). 2) Review the remote catalog or installed soul files before activating them—SOUL.md content can alter agent behavior and could cause the agent to reveal or act on sensitive data. 3) Confirm the catalog URL (https://soulsearching.ai) is a trusted source and consider fetching it manually to inspect contents. 4) Note the script will write to ~/.openclaw/souls/ and overwrite the workspace SOUL.md (it makes a .bak backup). 5) If you need stronger isolation, run the script in a sandboxed environment or inspect the included shell script and a sample catalog entry first.

Soul Searching — SOUL.md Manager

Manage SOUL.md personality files from soulsearching.ai.

Commands

All commands use scripts/soul.sh in this skill's directory.

Browse available souls

./scripts/soul.sh browse [category]

Categories: professional, creative, technical, funny, specialized, or omit for all.

Search souls

./scripts/soul.sh search <query>

Install a soul

./scripts/soul.sh install <soul-id> [--activate]

Downloads from soulsearching.ai and saves to ~/.openclaw/souls/<id>.md. With --activate, also copies to the workspace SOUL.md.

Switch to an installed soul

./scripts/soul.sh switch <soul-id>

Backs up current SOUL.md → SOUL.md.bak, then copies the installed soul into place.

List installed souls

./scripts/soul.sh list

Show current soul

./scripts/soul.sh current

Uninstall a soul

./scripts/soul.sh uninstall <soul-id>

Refresh catalog

./scripts/soul.sh refresh

Re-downloads the catalog from soulsearching.ai.

Workflow

1. Run browse or search to find a soul
2. Run install <id> --activate to install and activate in one step
3. Use switch to swap between previously installed souls
4. Use current to check what's active

Notes

• Souls are cached locally in ~/.openclaw/souls/
• The catalog is cached at ~/.openclaw/souls/.catalog.json (auto-refreshes if >24h old)
• switch always backs up the current SOUL.md before overwriting
• The workspace SOUL.md path is auto-detected (current directory or $OPENCLAW_WORKSPACE)