Overview
OpenClaw by concept teaches the framework through narrative explanation paired with annotated code, organized into three progressive levels. Each level builds directly on the previous: Beginner establishes vocabulary and mental models, Intermediate extends those models into custom workflows, and Advanced addresses production concerns and architectural extensibility.
Learning Path
%% Color Palette: Blue #0173B2, Orange #DE8F05, Teal #029E73, Purple #CC78BC, Brown #CA9161
%% All colors are color-blind friendly and meet WCAG AA contrast standards
graph TD
B["Beginner<br/>18 sections<br/>Concepts 1–18"]:::blue
I["Intermediate<br/>13 sections<br/>Concepts 19–31"]:::orange
A["Advanced<br/>11 sections<br/>Concepts 32–42"]:::teal
B -->|"understand core concepts"| I
I -->|"build custom workflows"| A
B1["What is OpenClaw?"]:::blue
B2["Local-First Architecture"]:::blue
B3["Seven Core Components"]:::blue
B4["Installation and First Run"]:::blue
B5["LLM Provider Configuration"]:::blue
B6["Your First Channel: Telegram"]:::blue
I1["Writing Your First Skill"]:::orange
I2["Selective Skill Injection"]:::orange
I3["Multi-Channel Routing"]:::orange
A1["Custom LLM Provider Integration"]:::teal
A2["Security Hardening"]:::teal
A3["Production Deployment"]:::teal
B --- B1
B --- B2
B --- B3
B --- B4
B --- B5
B --- B6
I --- I1
I --- I2
I --- I3
A --- A1
A --- A2
A --- A3
classDef blue fill:#0173B2,stroke:#000000,color:#FFFFFF,stroke-width:2px
classDef orange fill:#DE8F05,stroke:#000000,color:#FFFFFF,stroke-width:2px
classDef teal fill:#029E73,stroke:#000000,color:#FFFFFF,stroke-width:2px
What Each Level Covers
| Level | Coverage | Sections | Who It Is For |
|---|---|---|---|
| Beginner | 0–40% | 18 | Anyone new to OpenClaw or autonomous agent frameworks |
| Intermediate | 40–75% | 13 | Engineers ready to write custom skills and multi-agent workflows |
| Advanced | 75–95% | 11 | Engineers deploying OpenClaw in production or extending the framework |
Full Section Map
Beginner — 18 Sections
- What is OpenClaw? — Agent framework vs. app, why messaging as UI, local-first meaning
- Local-First Architecture — Why local, privacy implications, offline capability, latency advantages
- The Seven Core Components — Overview of Channel, Gateway, Skills, Runtime, Memory, LLM, Local Execution
- Installation and First Run — npm install or Homebrew, initial config wizard
- LLM Provider Configuration — API key setup for Claude, GPT, DeepSeek; model selection; cost trade-offs
- Your First Channel: Telegram — BotFather, bot token, connecting OpenClaw to Telegram
- The Channel Abstraction — What channels are, why 24+ platforms all look the same to the agent
- Gateway Fundamentals — Local control plane, how it routes messages to the agent runtime
- Understanding AGENTS.md — Purpose, format, what system instructions to put in it
- Understanding SOUL.md — Agent personality, name, tone, persona configuration
- Understanding TOOLS.md — Tool capability declarations, what tools the agent can use
- What is a Skill? — SKILL.md format intro, natural-language instructions, examples section, tools section
- Installing Skills from ClawHub — Searching the registry, install command, verifying installation
- Using Built-in Skills — What ships by default, how to invoke skills in conversation
- The Agent Runtime Loop — LLM → tool call → tool result → LLM cycle, how it terminates
- Memory Basics — Conversation context, what gets remembered within a session
- Companion Apps — macOS menu bar app, iOS/Android apps, sync across devices
- Security Foundations — What permissions OpenClaw requests, prompt injection risk, minimal-permission principle
Intermediate — 13 Sections
- Writing Your First Skill — SKILL.md anatomy in depth: instructions block, examples block, tools block
- Selective Skill Injection — How OpenClaw decides relevance, token budget, injection algorithm
- Multi-Channel Routing — Different channels mapped to different agent personas
- Agent Isolation — Isolated workspace per channel/account, why this matters for privacy
- Memory System Deep Dive — Semantic search over conversation history, embedding storage
- Knowledge Base Configuration — Adding PDF and markdown documents, indexed retrieval
- Custom Tool Definitions in TOOLS.md — Declaring tools with JSON schema, permission scoping
- Multi-Agent Orchestration — Running multiple OpenClaw instances, routing between agents
- Voice Mode — Wake word setup, voice input, TTS output, macOS/iOS only constraints
- Live Canvas and A2UI — Agent-driven visual workspaces, what the A2UI protocol enables
- Debugging Agent Behavior — Trace mode, logging, understanding why the LLM chose a tool
- Skill Composition — Combining multiple skills, resolving conflicts, ordering skills
- ClawHub: Discovering and Sharing Skills — Browsing the registry, packaging, publishing a skill
Advanced — 11 Sections
- Custom LLM Provider Integration — OpenAI-compatible APIs, local Ollama models, provider interface
- Gateway Customization — Custom routes, webhooks, event handling, extending the control plane
- Security Hardening — Prompt injection defenses, sandboxing execution, scoped permissions, audit logging
- Building a Domain-Specific Agent — End-to-end: design, skills, channels, memory for a CRM agent
- Multi-Agent Patterns — Specialist and orchestrator pattern, agent delegation, result aggregation
- Memory Persistence Architecture — Long-term episodic memory, knowledge graph integration
- ClawHub: Publishing Skills at Scale — Versioning, dependency management, testing skill packages
- OpenClaw and Pi Architecture — How Pi (minimal agent harness) influenced OpenClaw's design
- Production Deployment — Self-hosting considerations, reliability, monitoring, cost management
- Performance Optimization — Context window management, skill pruning, token cost reduction
- Contributing to OpenClaw — Codebase architecture (TypeScript core and Swift companion), PR workflow
How Each Section Is Structured
Every section in this track follows a consistent six-part format:
- Concept title and introduction — what the concept is, why it matters, how it connects to what came before (2–3 sentences)
- Diagram — a Mermaid flowchart or architecture diagram when the concept involves multiple components, data flows, or state transitions; omitted for trivial operations
- Narrative explanation — how the concept works, when to use it, trade-offs, best practices, and pitfalls (3–10 paragraphs)
- Annotated code examples — 1–5 examples with dense inline annotations using
// =>notation to document state, output, and reasoning at each step - Key Takeaway — the single most important insight from the section (1–2 sentences)
- Why It Matters — how the concept connects to a real production concern such as cost, reliability, security, or scale (50–100 words)
Last updated May 20, 2026