agent-init
Initialize and configure OpenClaw agent workspace MD files (AGENTS.md, SOUL.md, IDENTITY.md, USER.md, TOOLS.md, BOOTSTRAP.md, HEARTBEAT.md). Use when: setting up a new agent, customizing agent personality/behavior, configuring agent workspace, or checking/fixing agent environment (Python/uv). Provides interactive interview workflow before generating files. Supports both container and external (host) OpenClaw instances.
npx skills add majiayu000/claude-skill-registry --skill agent-init-dvcrn-openclaw-skills-mark --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Agent Init Initialize OpenClaw agent workspace with tailored MD files through an interactive interview. ## Workflow ### Phase 1: Interview (MANDATORY — do not skip) Before generating ANY files, gather context through conversation. Ask in batches of 2-3 questions: **Batch 1 — Identity & Purpose:** - What is this agent's primary purpose? (e.g., coding assistant, research, DevOps, personal assistant) - What name and emoji? Any personality traits? **Batch 2 — User Profile:** - Who will use this agent? (name, timezone, preferences) - Communication style preference? (formal/casual, verbose/terse, language) **Batch 3 — Environment:** - Is this a container instance or external (host) instance? - What tools/languages does the agent need? (Python, Node, etc.) - Any specific workflows or periodic tasks? **Batch 4 — Boundaries:** - Any topics or actions the agent should avoid? - Privacy requirements beyond defaults? Only proceed to Phase 2 after user confirms the interview is complete. ### Phase 2: Environment Check Run `scripts/check-env.sh` to detect Python/uv status: ```bash bash <skill-path>/scripts/check-env.sh ``` If uv is missing and user wants Python support: ```bash bash <skill-path
- Workflow
- Phase 1: Interview (MANDATORY — do not skip)
- Phase 2: Environment Check
- Phase 3: Generate Files
- Phase 4: Write Files
- Phase 5: Verify
- Reference Files
- Rules
bash <skill-path>/scripts/check-env.sh
bash <skill-path>/scripts/check-env.sh --install
docker exec <containerId> bash -c "which uv && uv --version || echo 'uv: NOT FOUND'"
Workspace files live at {workspacePath}/workspace/ (or workspace-{profile}/)
cat > {workspacePath}/workspace/SOUL.md << 'ENDOFFILE'
docker exec -i <containerId> sh -c 'cat > /home/node/.openclaw/workspace/SOUL.md' << 'ENDOFFILE'
External
ls -la {workspacePath}/workspace/*.md
Container
docker exec <containerId> ls -la /home/node/.openclaw/workspace/*.mdWhat does the agent-init skill do?
Initialize and configure OpenClaw agent workspace MD files (AGENTS.md, SOUL.md, IDENTITY.md, USER.md, TOOLS.md, BOOTSTRAP.md, HEARTBEAT.md). Use when: setting up a new agent, customizing agent personality/behavior, configuring agent workspace, or checking/fixing agent environment (Python/uv). Provides interactive interview workflow before generating files. Supports both container and external (host) OpenClaw instances.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill agent-init-dvcrn-openclaw-skills-mark --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.