OpenClaw Starter Kit
Turn your AI assistant from a stateless chatbot into a proactive, memory-rich agent that learns your patterns, tracks your work, and gets better every day.
Quickstart • What's Inside • Memory • Skills • Crons • Philosophy
This kit distills months of real-world iteration into a ready-to-use workspace. It's opinionated — because the defaults matter more than the options.
🧠 The Problem
Out of the box, AI agents are goldfish. Every conversation starts from scratch. They don't remember your preferences, can't track your open threads, won't check on things proactively, and repeat the same mistakes you've already corrected.
This starter kit fixes that with:
- Three-layer memory — facts, daily events, and learned patterns that persist across sessions
- Self-correcting behavior — corrections you make are permanently stored and loaded every session
- Proactive analysis — your agent checks things on its own (system health, stale threads, upcoming meetings)
- 19 pre-built skills — from GitHub repo analysis to morning digests to Twitter research
- 10 cron job templates — scheduled tasks that make your agent feel alive
⚡ 5-Minute Quickstart
# 1. Clone this repo
git clone https://github.com/wiziswiz/openclaw-starter-kit.git
cd openclaw-starter-kit
# 2. Run the bootstrap script
chmod +x setup.sh
./setup.sh
# 3. Fill in your identity
# The script will tell you which files to edit
# 4. Start (or restart) OpenClaw
openclaw gateway restart
That's it. Your agent now has a memory system, proactive heartbeats, thread tracking, and security-audited skill installation.
📦 What's in the Box
openclaw-starter-kit/
│
├── 🏠 workspace/ ← Your agent's brain
│ ├── AGENTS.md # Core rules: memory, search discipline, security
│ ├── SOUL.md # Persona + ACTIVE RULES (self-correcting behavior)
│ ├── IDENTITY.md # Agent name, personality, vibe
│ ├── USER.md # Your name, timezone, preferences
│ ├── HEARTBEAT.md # What to check proactively
│ ├── PATTERNS.md # Tacit knowledge (grows over time)
│ ├── TOOLS.md # Notes about your local tools
│ ├── pending-threads.json # Open loop tracker
│ ├── memory/ # Daily event logs
│ └── life/areas/ # Knowledge graph
│ ├── people/ # → Person entities
│ ├── companies/ # → Company entities
│ └── projects/ # → Project entities
│
├── 🛠️ skills/ ← 19 pre-built skills
│ ├── repo-analyzer/ # GitHub repo trust scoring & due diligence
│ ├── spawn-agent/ # Sub-agent orchestration
│ ├── fact-extraction/ # Memory fact extraction & management
│ ├── morning-digest/ # Daily morning briefing
│ ├── company-research/ # Structured BD research briefs
│ ├── x-research/ # Twitter/X research & search (free)
│ ├── x-research-api/ # Twitter/X research via paid API
│ ├── adversarial-review/ # Cross-model adversarial plan review
│ ├── consensus-researcher/ # Multi-source weighted consensus research
│ ├── google/ # Gmail, Calendar, Drive integration
│ ├── health-tracking/ # Wearable health data (WHOOP, Oura, etc.)
│ ├── healthcheck/ # System security hardening
│ ├── post-update-health-check/ # Post-update regression verification
│ ├── baseline-ui/ # UI quality baseline enforcement
│ ├── source-library/ # Auto-file & cross-reference shared URLs
│ ├── fixing-accessibility/ # WCAG accessibility fixes
│ ├── fixing-metadata/ # SEO & Open Graph metadata
│ ├── fixing-motion-performance/ # Animation performance optimization
│ ├── vercel-react-best-practices/ # 57 React/Next.js performance rules
│ └── web-design-guidelines/ # Web interface compliance review
│
├── ⏰ crons/ ← 10 scheduled job templates
│ └── starter-crons.json # Morning digest, nightly review, etc.
│
├── 📚 docs/ ← Guides
│ ├── MEMORY-SYSTEM.md # How the 3-layer memory works
│ ├── SKILLS-GUIDE.md # Creating and using skills
│ ├── CRON-GUIDE.md # Setting up proactive crons
│ └── PHILOSOPHY.md # The 10 principles behind great agents
│
└── 💡 examples/ ← Reference configs
├── example-patterns.md # Common tacit knowledge patterns
├── example-heartbeat.md # Heartbeat variants (dev/founder/researcher)
└── example-cron-setup.md # Step-by-step cron setup commands
🧠 The Memory System
Most AI agents forget everything between sessions. This kit gives your agent three layers of persistent memory:
┌─────────────────────────────────────────────────────┐
│ LAYER 1: Knowledge Graph │
│ │
│ life/areas/people/alice/summary.md │
│ life/areas/companies/acme/items.json │
│ life/areas/projects/my-app/summary.md │
│ │
│ → Entity-based facts with typed lifecycle │
│ → "Who is Alice?" → instant structured answer │
└─────────────────────────────────────────────────────┘
│
┌─────────────────────────────────────────────────────┐
│ LAYER 2: Daily Notes │
│ │
│ memory/2026-03-07.md │
│ memory/2026-03-06.md │
│ memory/2026-03-05.md │
│ │
│ → What happened today (raw event log) │
│ → Written continuously, not batched │
│ → "What did we do last Tuesday?" → date search │
└─────────────────────────────────────────────────────┘
│
┌─────────────────────────────────────────────────────┐
│ LAYER 3: Tacit Knowledge │
│ │
│ PATTERNS.md │
│ │
│ → Patterns about how YOU work │
│ → "User works late, don't suggest breaks" │
│ → "Test config on 1 system before batch rollout" │
│ → Grows organically from corrections │
└─────────────────────────────────────────────────────┘
Key insight: Manual memory writes > auto-capture. Deliberate saves are higher quality than automated logging. The agent decides what's worth remembering, not a parser.
→ Full details in docs/MEMORY-SYSTEM.md
🔄 The Self-Correction Loop
This is the single most impactful pattern in the kit:
You correct your agent
│
▼
Agent adds correction to SOUL.md ACTIVE RULES
│
▼
SOUL.md is loaded EVERY session
│
▼
Correction persists forever ✨
│
▼
PATTERNS.md captures the "why" for deeper understanding
Example: You tell your agent "don't use markdown tables on Telegram, they render as garbage." The agent:
- Immediately adds to SOUL.md:
NO TABLES ON TELEGRAM — bullets only - Adds to PATTERNS.md: the reasoning and context
- Never makes that mistake again
The difference between a good agent and a great one is how it handles corrections.
🛠️ Skills Library
Skills are specialized instruction files that teach your agent how to handle specific tasks. Install by copying to ~/.openclaw/skills/.
Research & Analysis
| Skill | What it does |
|---|---|
repo-analyzer | Trust-score any GitHub repo (security, code quality, contributor patterns) |
company-research | Structured research briefs for outreach or due diligence |
x-research | Search Twitter/X for real-time perspectives and expert opinions |
x-research-api | Paid X/Twitter API research (higher engagement results). Companion to x-research — use when you need tweets with 1K+ likes vs free version's ~23 likes. |
consensus-researcher | Multi-source research (Reddit, HN, Amazon, YouTube, expert sites) with weighted consensus scoring. Great for product/market research. |
adversarial-review | Cross-model adversarial plan review — two models alternate writer/reviewer until convergence. Use before any major build or implementation. |
Productivity
| Skill | What it does |
|---|---|
morning-digest | Daily briefing: calendar, threads, weather, action items |
spawn-agent | Deploy sub-agents for parallel or long-running tasks |
fact-extraction | Extract and organize facts from conversations into memory |
google | Gmail search/send, Calendar events, Drive file access |
source-library | Auto-file shared URLs with structured summaries, cross-referencing, confidence decay, and conflict detection. Your agent's second brain for everything you read. |
Health & Wellness
| Skill | What it does |
|---|---|
health-tracking | Wearable integration (WHOOP, Oura, Apple Health, Garmin) — recovery scores, sleep trends, fitness streaks |
💡 Your agent can pull your daily recovery score and weave it into your morning digest. Green day? Stack the hard meetings. Red day? Go easy. See
skills/health-tracking/SKILL.mdfor setup.
System & Security
| Skill | What it does |
|---|---|
healthcheck | Security hardening audit (firewall, SSH, updates, exposure) |
post-update-health-check | Verify nothing broke after an OpenClaw update |
Development Quality (6 skills)
| Skill | What it does |
|---|---|
baseline-ui | Enforce consistent, accessible UI patterns |
fixing-accessibility | WCAG-compliant keyboard, screen reader, focus fixes |
fixing-metadata | SEO tags, Open Graph, canonical URLs, structured data |
fixing-motion-performance | Fix janky animations and rendering bottlenecks |
vercel-react-best-practices | 57 prioritized React/Next.js performance rules from Vercel |
web-design-guidelines | Web Interface Guidelines compliance review |
🔄 Keeping Skills Updated
Third-party skills can receive upstream updates. A weekly cron checks for new commits automatically and pings you if anything's worth pulling.
To manually check or pull updates for a skill:
cd ~/.openclaw/skills/<skill-name>
git fetch && git log HEAD..origin/main --oneline
git pull # if updates look safe
For SME (Structured Memory Engine), updates require a rebase — see ~/Projects/Structured-Memory-Engine/README.md for the merge guide.
⏰ Proactive Crons
Cron jobs are what make your agent feel alive — it does things without being asked.
The kit includes 10 starter cron templates (crons/starter-crons.json):
| Cron | Schedule | What it does |
|---|---|---|
| 🌅 Morning Digest | 7:30 AM daily | Calendar, threads, weather, action items |
| 🔍 Nightly Self-Review | 1:00 AM daily | Grade today's performance, find improvement areas |
| 🛡️ Config Watchdog | Every 15 min | Detect silent config changes or drift |
| 💾 Git Backup | 3:00 AM daily | Auto-commit and push workspace changes |
| 📞 Meeting Prep | Every 30 min (business hours) | Research upcoming call participants |
| 💪 Health Summary | 7:30 AM daily | Pull wearable recovery/sleep, flag low days |
| 🧠 Weekly Synthesis | Sunday 10 AM | Consolidate the week's facts and patterns |
| 📋 Thread Cleanup | 7:00 PM daily | Surface stale open threads needing follow-up |
| 📝 Fact Extraction | 9:00 PM daily | Extract durable facts from today's conversations |
| 🧹 Session Cleanup | Sunday 4 AM | Prune old cron/sub-agent session files (they accumulate forever and bloat memory) |
→ Step-by-step setup in examples/example-cron-setup.md
🏗️ Workspace Files Explained
AGENTS.md — The Rulebook
Your agent's operating manual. Contains:
- Search Before Speaking — never claim ignorance without grepping first
- Three-Layer Memory System — how to store and retrieve information
- Continuous Memory Writes — write immediately, don't wait for batch flushes
- Security Audit Protocol — mandatory review before installing any new skill
- Tool Failure Recovery — try 3 approaches before reporting failure
- Correction Protocol — how to handle behavior corrections
SOUL.md — Persona + Active Rules
Two sections:
- Persona — your agent's personality (confident, concise, playful, whatever you want)
- Active Rules — the 5-10 most important behavior corrections, loaded every session
HEARTBEAT.md — Proactive Checklist
What your agent checks on heartbeat polls:
- System health (OpenClaw updates, cron errors)
- Open threads older than 48 hours
- Upcoming calendar events needing research
- Patterns suggesting new skills to create
See examples/example-heartbeat.md for variants tailored to developers, founders, and researchers.
PATTERNS.md — Living Knowledge
Starts empty. Grows as your agent learns:
- Debugging patterns ("always check HTTP method before calling")
- Deployment lessons ("test on 1 system before batch rollout")
- Your preferences ("user works late, don't suggest breaks")
- Tool quirks ("this API returns 429 after 3 calls, back off")
See examples/example-patterns.md for common starter patterns.
🧭 Philosophy
Ten principles that separate great agent setups from mediocre ones:
- Manual memory beats auto-capture. Quality > quantity.
- Search before speaking.
grepcosts 1 tool call. Guessing costs 3+. - Corrections go to SOUL.md. It's the only file loaded every session.
- Evening cleanup produces artifacts. Quiet time = drafts, research, thread updates.
- Benchmark before implementing. Evaluate first, build second.
- Isolate before fixing. Confirm which system is broken before changing anything.
- Test on one before rolling out. One cron, one config, one system.
- Deliver, don't prepare. Internal prep ≠ completion. User-facing delivery = done.
- Write immediately. Don't wait for batch flushes. Facts decay in RAM.
- Build skills from repetition. 3+ times = create a skill.
→ Full breakdown with examples in docs/PHILOSOPHY.md
🚀 Getting Started
After running setup.sh:
- Edit
~/clawd/IDENTITY.md— Give your agent a name and personality - Edit
~/clawd/USER.md— Tell your agent who you are - Edit
~/clawd/SOUL.md— Customize the persona (or keep the default) - Start talking — Your agent will begin building memory from day one
- Correct freely — Every correction makes it permanently smarter
- Set up crons — See
examples/example-cron-setup.mdfor the essentials
Optional Power-Ups
- Install skills → Copy from
skills/to~/.openclaw/skills/ - Enable Google integration → Follow
skills/google/SKILL.mdsetup - Add Obsidian sync → Dual-write to an Obsidian vault for graph visualization
- Create custom skills → See
docs/SKILLS-GUIDE.md
🤝 Contributing
Found a pattern that makes your agent better? A skill that's universally useful? Open a PR.
The best contributions are battle-tested patterns — things you've run for weeks and proven work.
📝 License
MIT — use it, fork it, make it yours.
Built from months of real-world iteration. Every pattern earned, not invented.
No comments yet.