agentleFS
CodeAlive-AICodeAlive-AI/ceo-ai-os/skills/openclaw-guide/SKILL.md

openclaw-guide

Skill9 starsChanged 6 months agoMITView on GitHub

Reference and consulting skill for OpenClaw — a messaging gateway that connects AI agents to multiple communication platforms (Telegram, Discord, Slack, WhatsApp, iMessage, and more). Use when working with OpenClaw configuration, channels, Gateway setup, skills, cron jobs, MCP servers, memory, OAuth, or troubleshooting. Also use when the user asks how to implement a use case on their OpenClaw bot (daily morning brief, research workflows, competitive radar, decision playbook), how to add a new channel, or how to connect the CodeAlive context engine. Triggers on requests like "configure openclaw", "add Discord to my bot", "set up morning brief", "gateway not starting", "connect CodeAlive search", "OAuth re-auth", or any close paraphrase. Companion of install-openclaw-to-yc — install both together.

The file

Files
SKILL.md

OpenClaw Guide

OpenClaw is a messaging gateway that connects AI agents to 24+ communication platforms. This skill is the reference for everything after the bot is installed — channels, use cases, memory, cron, MCP, OAuth, troubleshooting.

Current production version assumed: 2026.5.x (latest 2026.4.x is also fully covered). Official docs: https://docs.openclaw.ai/ · Source: https://github.com/openclaw/openclaw

Setup (install OpenClaw first)

This skill is consultation-only. If the user doesn't have an OpenClaw bot yet, install both skills together and run the companion wizard:

npx skills add CodeAlive-AI/ceo-ai-os@install-openclaw-to-yc -g
npx skills add CodeAlive-AI/ceo-ai-os@openclaw-guide -g

Then tell the agent: "install OpenClaw on Yandex Cloud Kazakhstan". The install-openclaw-to-yc skill takes over and uses this one for any post-install consultation.

For other hosts (local Mac, GCP, AWS, bare metal) the OpenClaw upstream documentation at https://docs.openclaw.ai/start/getting-started is the canonical guide — no CEO AI OS wizard exists for them yet.

How to read this skill

The full content is split across nine reference files. Read only the one that matches the user's current question — bringing all of them into context wastes the budget.

If the user asks about…Read
Agent runtime, bootstrap files, sessions, message flow, chat commands, skillsreferences/01-architecture.md
MEMORY.md, daily notes, dreaming, memory backends, embedding providers, sync safetyreferences/02-memory.md
Cron jobs (add / list / rm), heartbeat, scheduled tasks, timezones, delivery flagsreferences/03-cron-heartbeat.md
MCP servers (Exa, PostHog, Grafana, …), openclaw mcp set, transports, tool namingreferences/04-mcp.md
openclaw.json schema, key CLI commands, paths, auth modes, exec approvals, systemd unitsreferences/05-config-and-cli.md
OAuth re-auth (models auth login bugs, orphan profiles), server-side debugging, channel caveatsreferences/06-troubleshooting.md
Use cases — morning brief, research workflows, competitive radar, decision playbook, email handler, meeting prepreferences/use-cases.md
Channels — Telegram details, adding Discord / Slack / WhatsApp / iMessagereferences/channels.md
CodeAlive search inside the bot — semantic_search, grep_search, chat over indexed reposreferences/codealive-context-engine.md

Critical pitfalls (always cross-check before infrastructure changes)

These are the recurring footguns. Read this table before any planned restart, OAuth re-auth, cron edit, or schema change.

#TitleWhen it bites
1Isolated cron sessions can't deliver to TelegramUse --session main or session:cron-<name>, not isolated
2Telegram adapter silently dies after ~12hWatchdog timer restarts gateway on outbound errors
6Gateway auth handshake timeout on small VMsgateway.auth.mode: none is safe on loopback
7Bootstrap file truncation drops the middleKeep individual files compact; truncation = 70% head + 20% tail
14cron add syntax — --message (not positional), --name (no --id), cron rm (no delete)All cron CLI work
18Cron jobs without explicit --timeout-seconds use 600s defaultAlways set explicitly
19Exec approval blocked when no Telegram approvertools.exec.security: full + ask: off on headless server
20openclaw-monitor.timer kills gateway during slow startupStop timer → restart → wait /health=200 → start timer
21models auth login clobbers other providers + schema gotchaBackup config first; correct path is agents.defaults.models, NOT models.configuredModels
22composio CLI fails with EACCES posix_spawn from gcloud sshRun cd /tmp first or invoke as root
23OAuth re-auth leaves orphan profilesDecode access JWT, compare chatgpt_account_id, prune duplicates

Full numbered list with workarounds lives in the CEO AI OS workspace repo at OPENCLAW_PITFALLS.md. When a new pitfall surfaces, add it there — single source of truth.

Upstream documentation index (quick links)

These are direct URLs into docs.openclaw.ai for occasions when this skill's references don't cover a feature. Prefer this skill's references first — they're tuned for the workshop / personal CEO bot context.

Getting started

Gateway & configuration

Channels

Core concepts

Tools, automation, install

Companion skill (required at install time)

install-openclaw-to-yc (sibling) — the wizard that creates the VM, installs OpenClaw, and seeds the workspace. Install it alongside this skill:

npx skills add CodeAlive-AI/ceo-ai-os@install-openclaw-to-yc -g

The two skills cross-reference: install-openclaw-to-yc runs the bootstrap and hands off to this guide for everything after. This guide assumes the bot is already up and walks the user through configuration, channels, use cases, and operations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.