community upload

OpenClaw Starter Kit

by @obadiaha

obadiaha OpenClaw Starter Kit Production-ready workspace template for OpenClaw AI agent deployments. Structured memory protocol, security-first defaults, and...

OpenClaw Client Starter Kit

By Go Digital | v1.0

This folder contains everything needed to set up a new OpenClaw deployment for a client. Copy the entire folder into the client's workspace directory.

What's Included

Core Files (workspace root)

FilePurposeWhen It's Read
SOUL.mdAgent personality, values, boundariesEvery session
AGENTS.mdOperating instructions, memory protocol, safety rulesEvery session
IDENTITY.mdAgent name, role, emojiEvery session
USER.mdHuman's name, timezone, preferences, projectsEvery session
TOOLS.mdConnected services, API notes, installed skillsAs needed
HEARTBEAT.mdPeriodic check-in tasksOn heartbeat polls
BOOTSTRAP.mdFirst-run conversation guide (delete after setup)First session only
MEMORY.mdLong-term curated memoryEvery main session

Memory Directory (memory/)

FilePurpose
KEY-DECISIONS.mdDecisions that affect future behavior
lessons-learned.mdWhat worked, what failed, patterns
content-ideas.mdIdeas for content creation
archive/Older daily notes (auto-searchable)

Scripts (scripts/)

FilePurpose
install-openclaw.shFull VPS installer (Node.js, OpenClaw, workspace, systemd service)
harden-vps.shSecurity hardening (UFW, SSH lockdown, fail2ban, Docker)

One-line install on a fresh VPS:

curl -fsSL https://raw.githubusercontent.com/obadiaha/openclaw-starter-kit/main/scripts/install-openclaw.sh | sudo bash

Or step by step:

git clone https://github.com/obadiaha/openclaw-starter-kit.git
cd openclaw-starter-kit
sudo bash scripts/install-openclaw.sh

Setup Steps

1. Copy Files

cp -r client-starter-kit/ /path/to/client/workspace/

2. First Boot

The agent will find BOOTSTRAP.md and initiate a getting-to-know-you conversation with the client. They'll decide the agent's name, personality, and preferences together.

3. Post-Bootstrap

After the first conversation, the agent will:

  • Fill in IDENTITY.md with its chosen name and emoji
  • Fill in USER.md with the client's info
  • Customize SOUL.md based on the conversation
  • Delete BOOTSTRAP.md
  • Create initial daily notes in memory/

4. Hardening

Run through the security checklist in client-onboarding-guide.md (separate document).

Customization

For Business Clients

Add to AGENTS.md:

  • Industry-specific instructions
  • Compliance requirements
  • Approved external actions
  • Reporting schedules

For Technical Clients

Add to TOOLS.md:

  • SSH server details
  • GitHub repos
  • Database connections
  • CI/CD pipelines

For Creative Clients

Add to SOUL.md:

  • Brand voice guidelines
  • Content pillars
  • Tone preferences
  • Platform-specific rules

File Relationships

BOOTSTRAP.md (first run only, then deleted)
    ↓ creates
IDENTITY.md ← who the agent is
USER.md     ← who the human is
SOUL.md     ← how the agent behaves
    ↓ governed by
AGENTS.md   ← operating rules + memory protocol
    ↓ uses
MEMORY.md + memory/ ← persistent knowledge
TOOLS.md   ← environment config
HEARTBEAT.md ← periodic tasks

The Memory Protocol

The key differentiator in our setup. Most OpenClaw deployments have no structured memory. Our clients get:

  1. 5-file save protocol - Every significant action saves to 5 files
  2. Auto-triggers - Agent knows WHEN to save (not just "remember things")
  3. Structured storage - Agent knows WHERE to save (daily notes vs long-term vs decisions)
  4. Search-first recall - Uses memory_search before answering from memory
  5. Context management - Auto-saves when context window fills up

This is the protocol that makes the agent actually useful across sessions instead of starting fresh every time.


Maintained by Go Digital. Last updated: February 2026.

Workspace

Current published snapshot. New publishes overwrite this view.

Download .zip
15 FilesUpdated 2026-03-09 00:15:22 UTC1 blocked
Published via backfill-null-source-repo-v1
AGENTS.mdtext · 3.5 KB

Source Repository

Original GitHub repository for this setup.

Community

No comments yet.