community server live at community-openclaw.swatsprints.xyz

Your bot learns
from every other bot
in the network.

OpenClaw Community is a shared intelligence layer for OpenClaw bots. Skills, config benchmarks, and ad-outcome data — pooled automatically. Zero message content. One env var.

Connect your bot How it works
oc-community — startup
$ openclaw start → loading hook: @openclaw/community-hook ▸ register_bot ✓ bot=prod-ad-agent skills=6 ▸ share_config ✓ providers=[anthropic] ▸ report_intent ✓ use_cases=[ads] ▸ get_suggestions ✓ 3 suggestions (intent-filtered) ─────────────── community update ─────────────── 📊 Ad agent update ROAS: 3.12x → 3.81x ↑ (+0.69x) vs community (ads): top 25% ✅ (median 3.1x) 💡 Skills your peers use that you don't: • report-ad-outcomes — used by 14 bots • google-ads-monitor — used by 9 bots ──────────────────────────────────────────────── ready.
9
community tools
0 B
message content transmitted
1
env var to connect
free
during beta
how it works

Automatic intelligence.
Zero friction.

A single hook connects every OpenClaw bot to a shared server. Each bot contributes anonymised signals and gets community intelligence back — on every startup.

01
🔌
Bot starts → hook fires
On gateway startup, the community hook auto-registers your bot and shares anonymised config metadata: provider, model, skill list. No prompts, no responses.
02
📡
Session closes → telemetry flows
When a session ends, token usage is reported (input/output counts, duration, model). The JSONL file stays local — only aggregated numbers leave your machine.
03
🧠
Server reasons over community data
Skills used by peer bots, config patterns from your provider, ROAS benchmarks from ad agents — all aggregated and ranked for you specifically.
04
💬
Insights land in your chat
No dashboard. No email. Insights arrive as a proactive message at the start of your next conversation — exactly when they're useful.
what you get

Every bot smarter.
Because all bots share.

Joining the community isn't altruism. You get real, actionable intelligence back on every startup.

🎯
Intent-aware skill suggestions
Declare OC_AGENT_VERTICAL=ads and you get ad skills — not generic ones. The server maps your intent to the right skill tags automatically.
skill-gap analysis
⚙️
Config tips from real usage
"68% of Anthropic bots enable cache retention — you don't." Tips generated from what bots on your provider actually configure.
provider benchmarks
📊
Ad outcome benchmarks
ROAS/CPA comparisons against the community p25–p90, updated daily from real Meta and Google Ads data contributed by ad agents.
ads vertical
🔒
Privacy by design
Message content never leaves your machine. Only token counts, model IDs, provider names, and anonymised config flags are transmitted.
L0 privacy level
⚡
No dashboard. No noise.
Intelligence surfaces in chat, not in a tab you forget to open. The hook injects a proactive nudge at startup — only when there's something worth saying.
proactive delivery
🌐
Network effects
The more bots connect, the better the benchmarks. Every new bot makes the suggestions more accurate for everyone already in the network.
growing dataset
get started

Set up over WhatsApp.
The bot walks you through it.

Install one skill and the bot handles the rest — asking questions over WhatsApp or Slack and applying your config automatically.

WhatsApp — your OpenClaw bot
👤
configure community
🦀
Hey! Let's connect your bot to the OpenClaw Community. It'll start sharing anonymised telemetry and getting back skill suggestions automatically. Takes about 2 minutes. Ready?
👤
yeah go ahead
🦀
What should I call this bot? It'll show up in community stats.
👤
prod-ad-agent
🦀
What's this bot mainly used for? Options: ads, coding, chat, automation — or just describe it.
👤
it manages our Meta campaigns
🦀
Got it — ads vertical, Meta platform. Want me to also install the ad outcomes skill? It'll report daily ROAS to the community benchmark pool. Credentials stay on this machine.
👤
yes
🦀
Done ✅ Hook installed, config set, ad outcomes skill ready. Next restart you'll see a community update in your first message.
01
Install the community-setup skill
Download and install the skill that powers the setup conversation. Run this once on the machine where your bot lives.
# Download the tarball curl -fsSL https://community-openclaw.swatsprints.xyz/hook/oc-community-hook.tar.gz \ -o /tmp/oc-community-hook.tar.gz # Install the hook from local file openclaw hooks install /tmp/oc-community-hook.tar.gz
02
Message your bot
Open WhatsApp (or Slack) and send your bot any of these phrases. It'll start the setup conversation immediately.
configure community — or — connect to community — or — set up community
03
Answer the bot's questions
The bot asks for your bot name, vertical, ad platform (if applicable), and whether to install the ROAS reporting skill. It applies every config step automatically — no terminal needed.
04
Restart your bot
After setup completes, restart the gateway. The hook fires on next startup and your bot is live in the network.
# You'll see in startup logs: [oc-community] registered bot prod-ad-agent (1 providers, 6 skills) # And in your next message if there's anything useful: 👋 Community update 📊 ROAS: 3.4x — top 25% vs community ✅ 💡 report-ad-outcomes — used by 14 bots
open beta

Your bot is flying blind.
It doesn't have to.

The community server is live. One env var connects your bot to the network. Free during beta.

Connect your bot now View source