ReSoul

Fully reset OpenClaw's persona/bootstrap state and restore the latest official BOOTSTRAP.md after an explicit second confirmation. Use when the user wants to...

Security Scan

The skill's code and instructions match its stated purpose: it fetches the official BOOTSTRAP.md from GitHub and archives/replaces SOUL.md, USER.md, and IDENTITY.md in the workspace as described.

Purpose & Capability

The name/description (reset bootstrap/persona) directly corresponds to the included script and SKILL.md: the script downloads the official BOOTSTRAP.md and archives/replaces the three identity files. No unrelated credentials, binaries, or config paths are requested.

Instruction Scope

The SKILL.md limits actions to fetching the official template and archiving/removing only SOUL.md, USER.md, and IDENTITY.md; the included script follows that behavior. Note: the script performs the file operations non-interactively, so the agent or UI must enforce the SKILL.md requirement for a second explicit user confirmation before invoking the script.

Install Mechanism

Instruction-only skill with a small bundled script; no install spec or external packages. The fetch uses a well-known host (raw.githubusercontent.com), which is an expected upstream source.

Credentials

No environment variables, credentials, or unrelated config paths are requested. The script uses common commands (curl/wget, mv, mkdir) and a workspace directory; these are proportional to the task.

Persistence & Privilege

The skill does not request always: true, does not modify other skills, and does not persist credentials. It writes files only inside the workspace directory and a .trash subdirectory as described.

Assessment

This skill is coherent with its purpose, but it's destructive: only run it after you explicitly confirm you want to archive and replace SOUL.md, USER.md, and IDENTITY.md. Before running: (1) verify the workspace path is correct (the script defaults to /root/.openclaw/workspace if none provided), (2) ensure you issue the required explicit second confirmation in the conversation (the script will not prompt), (3) review the fetched BOOTSTRAP.md after the script completes and before executing /new, and (4) if you require higher integrity guarantees, fetch a pinned commit or verify a checksum instead of relying on the live raw.githubusercontent.com URL. Finally, expect the originals to be moved into .trash/ with timestamps — check that folder if you need to recover anything.

Reset the workspace bootstrap state so the next fresh session can start from the official upstream BOOTSTRAP.md.

Primary workflow

1. Warn that running resoul will fetch the official BOOTSTRAP.md, then archive the current SOUL.md, USER.md, and IDENTITY.md into .trash/ and remove them from the workspace root if they exist.
2. Require an explicit second confirmation before executing anything. Do not treat vague replies like "ok" or "继续" as sufficient; require a clear confirmation that the user agrees to archive and remove the current SOUL.md, USER.md, and IDENTITY.md from the workspace root.
3. Fetch the latest official upstream template to a temporary file first, and only continue if the fetch succeeds.
4. Archive the current SOUL.md, USER.md, and IDENTITY.md into .trash/ if they exist.
5. Write the fetched template to the workspace root as BOOTSTRAP.md.
6. Tell the user to run /new after completion so the next session starts from the restored bootstrap flow.

Use the bundled script:

bash {{SKILL_DIR}}/scripts/fetch_official_bootstrap.sh <workspace-dir>

Example:

bash {{SKILL_DIR}}/scripts/fetch_official_bootstrap.sh /root/.openclaw/workspace

Upstream source:

https://raw.githubusercontent.com/openclaw/openclaw/main/docs/reference/templates/BOOTSTRAP.md

Constraints

• Do not execute this skill without a second explicit confirmation in the current conversation.
• Do not hand-author a replacement bootstrap unless the user explicitly asks for a customized variant after syncing the official file.
• Only archive and remove SOUL.md, USER.md, and IDENTITY.md from the workspace root; do not delete memory, project files, skills, or other workspace content.
• Fetch the official template successfully before archiving or removing any existing identity files.
• Archive existing SOUL.md, USER.md, and IDENTITY.md into .trash/ before removing them from the workspace root when those files exist.
• Do not execute the bootstrap ritual automatically after syncing; stop after preparing the workspace and instruct the user to run /new.
• Mention that the official template is written for a fresh workspace and should be reviewed before reuse in an existing workspace.

Fallback

If the script cannot be used, run equivalent shell commands that (1) fetch the official BOOTSTRAP.md to a temporary file first, (2) archive existing SOUL.md, USER.md, and IDENTITY.md into .trash/ if present, (3) write the fetched template to the workspace root as BOOTSTRAP.md, and (4) avoid touching memory, project files, skills, or other workspace content.

Report back

Briefly report:

• that the user gave the destructive confirmation
• whether SOUL.md, USER.md, and IDENTITY.md were archived/cleared
• that the latest official upstream template was fetched
• the destination path
• that the user should run /new to trigger the re-bootstrap flow