Openclaw Startup

v1.0.3

First-run setup wizard for new OpenClaw agents. Interviews the user to generate a tailored SOUL.md, scaffolds memory architecture, installs recommended crons...

0· 106·0 current·0 all-time
byDon Zurbrick@zurbrick
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
Name/description match the provided files and scripts: templates, interview guide, memory scaffolding, cron recommendations, and post-setup verification. Required binaries (bash, mkdir, date) are appropriate for the tasks.
Instruction Scope
SKILL.md confines actions to interviewing the user, generating templates, creating a workspace, and optionally installing crons via the openclaw CLI. It explicitly requires user approval before writing. The included scripts create files and verify them; they do not read or transmit unrelated system secrets or call external endpoints.
Install Mechanism
No install spec — instruction-only with two local scripts. Scripts are included in the skill bundle (no remote downloads or third-party package installs). This minimizes install-time risk.
Credentials
The skill declares no required environment variables or credentials. The scripts optionally respect OPENCLAW_WORKSPACE if set; otherwise they write to a default $HOME/.openclaw/workspace. No unrelated credentials or secrets are requested.
Persistence & Privilege
always is false and the skill is user-invocable. The scripts create files and initialize a local git repo in the workspace (normal for scaffolding). The skill does not modify other skills' configs or request permanent platform-wide presence.
Assessment
This skill appears coherent and does what it says: it will ask the interview questions, generate SOUL/USER/IDENTITY/AGENTS files, create a workspace (default: $HOME/.openclaw/workspace or OPENCLAW_WORKSPACE), initialize a git repo, and optionally register crons via the openclaw CLI. Before running: (1) Confirm the workspace path it will write to — avoid pointing it at sensitive directories; (2) Review the generated SOUL.md/USER.md/IDENTITY.md when the agent shows them and only approve writes you expect; (3) Be aware the install script will run git init and create a local commit (it sets a local git identity if none exists); (4) Cron installation is only performed if you approve and if the openclaw CLI is available — review cron payloads/timings carefully; (5) The verify script performs local secret-pattern scanning and runs openclaw commands if available — it does not exfiltrate data, but review its output if it flags possible secrets. If you want extra assurance, run the included scripts yourself from a shell (inspect them first) rather than letting the agent run them autonomously.

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

latestvk974qz66sesbnv5pzveytg6g0183gbkeonboardingvk97bef2vz03qaftrp3716jb0ed83ex92setupvk97bef2vz03qaftrp3716jb0ed83ex92wizardvk97bef2vz03qaftrp3716jb0ed83ex92

License

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

Runtime requirements

🚀 Clawdis
Binsbash, mkdir, date

Comments