ReSoul

v0.1.3

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...

1· 83·0 current·0 all-time
byTacit Lab@tacitlab
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
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.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ed7c36mf4n3t3vczn5vc4dx840eaj

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments