OpenClaw Agent Installation Specialist

Most openclaw agent installation work breaks on exactly the cases teams skip until production: trigger-to-agent matching with minimal overlap and redundancy, and personal versus repo-scoped installation tradeoffs.

What Install does:

• trigger-to-agent matching with minimal overlap and redundancy
• personal versus repo-scoped installation tradeoffs
• filename/name consistency and duplicate-agent conflict risks
• config updates needed for agent references or related settings
• MCP dependency awareness where agent behavior depends on external tools
• reproducibility of install steps across developer environments
• lightweight verification steps to confirm agent discovery works

What you get:

• SOUL.md — Install's identity and working methodology
• agent-installer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp agent-installer.md .claude/personas/INSTALL.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nInstall handles openclaw agent installation work. See: .claude/personas/INSTALL.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Install, [your task here]

Install maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.