OpenClaw

Social media studio ships as an OpenClaw skill bundled inside the @social-media-scheduler/cli npm package — install the CLI once and OpenClaw automatically discovers the skill.

Install

Install OpenClaw on your machine

Follow the OpenClaw install guide. Requires Node.js 22+.

npm install -g openclaw@latest
openclaw onboard --install-daemon

Install the Social media studio CLI (which ships the skill)

npm install -g @social-media-scheduler/cli

The @social-media-scheduler/cli package includes:

The so-me CLI binary
SKILL.md — the OpenClaw skill body
tools.md — auto-generated catalog of all 205 tools
examples/ — three worked transcripts (schedule-post.md, reply-dm.md, weekly-report.md)

Authenticate

Create an API key at so-me.studio/settings?tab=api, then export it:

export SOMESTUDIO_API_KEY=sk_live_...

OpenClaw checks eligibility automatically. Verify with:

openclaw skills list --eligible | grep so-me-studio

Once paired, you can chat with the agent from Discord, Slack, WhatsApp, Telegram, or any of 22 supported messengers.

Or via ClawHub

The skill is published on ClawHub. Install with either of the canonical commands:

# OpenClaw-native (recommended)
openclaw skills install yasin047/so-me-studio

# ClawHub package-manager path
npx clawhub@latest install so-me-studio

Both pull the same skill bundle. The underlying mechanism is @social-media-scheduler/cli on npm — ClawHub indexes the published npm package. Skill page: clawhub.ai/yasin047/so-me-studio

What you can ask

After install, prompt the agent in plain English:

Prompt	What happens
”What social accounts do I have connected?”	Calls `accounts:list`, summarizes by platform.
”Schedule a tweet saying hello at 5pm tomorrow.”	Computes the ISO timestamp, calls `posts:create`.
”Reply to that DM with my saved ‘pricing’ template.”	Looks up the saved reply, calls `inbox:reply`.
”How did my Twitter posts perform last week?”	Calls `analytics:platform` with `--days 7`.
”Generate a Friday product-launch caption for LinkedIn and schedule it.”	Calls `ai:generate-and-schedule` end-to-end.

The agent has access to all 205 Social media studio MCP tools — every action available in the dashboard is available here.

Chat from any messenger

OpenClaw supports 22 messaging channels — DM the agent from whichever you already use. Once paired, every channel uses the same agent and the same so-me-studio skill, so you get the same answers from Discord, WhatsApp, or Slack.

First-time prerequisite

Before any channel can be added, OpenClaw needs initial config at ~/.openclaw/openclaw.json:

openclaw onboard          # interactive — recommended
# or:  openclaw setup --non-interactive --accept-risk

Skipping this step makes openclaw gateway fail with Missing config. Run openclaw setup or set gateway.mode=local.

The pattern (works for any channel)

# 1. Get a credential from the platform you want to use
# 2. Wire it into OpenClaw
openclaw config set channels.<slug>.<field> <value>
openclaw config set channels.<slug>.enabled true --strict-json

# 3. Register the channel + run the gateway
openclaw channels add --channel <slug>
openclaw gateway

The gateway command starts a local daemon that listens on every enabled channel and routes messages to your installed skills.

Top 7 — full setup

1. Create a Discord application

Go to discord.com/developers/applications → New Application
Bot tab → Add Bot → click “Copy” under TOKEN (keep it secret)
Bot tab → INTENT SETTINGS → enable Message Content Intent ⚠️ required
(Optional, for server use) OAuth2 → URL Generator → scope bot, permissions Send Messages, Read Message History, Embed Links, Attach Files → open the URL to invite the bot to a server. For DM-only use, skip this step.

2. Wire the token into OpenClaw

export DISCORD_BOT_TOKEN="your_bot_token_here"

openclaw config set channels.discord.token \
  --ref-provider default --ref-source env --ref-id DISCORD_BOT_TOKEN
openclaw config set channels.discord.enabled true --strict-json

3. Register the channel

openclaw channels add --channel discord

The wizard prompts for an account identifier — use your Discord user ID or username.4. Run the gateway + smoke test

openclaw gateway

Then in Discord, DM your bot:

“List my connected social accounts”

The first message triggers a pairing code printed in the OpenClaw terminal. Approve with openclaw admin pair-code <code>.

1. Create a Slack app

Go to api.slack.com/apps → Create New App → From scratch → choose your workspace
OAuth & Permissions → add these Bot Token Scopes:
- app_mentions:read, chat:write, channels:read, groups:read, im:read
- channels:history, groups:history, im:history, mpim:history
- files:read, files:write
Socket Mode tab → enable it (recommended — no public webhook URL needed)
Basic Information → generate an App-Level Token with scope connections:write (xapp-…)
Install to Workspace → copy the Bot User OAuth Token (xoxb-…)

2. Wire the tokens into OpenClaw

export SLACK_BOT_TOKEN="xoxb-..."
export SLACK_APP_TOKEN="xapp-..."

openclaw config set channels.slack.botToken "$SLACK_BOT_TOKEN"
openclaw config set channels.slack.appToken "$SLACK_APP_TOKEN"
openclaw config set channels.slack.mode "socket"
openclaw config set channels.slack.enabled true --strict-json

3. Register the channel

openclaw channels add --channel slack

4. Run the gateway + smoke test

openclaw gateway

DM your Slack bot:

“List my connected social accounts”

Approve the pairing code (same flow as Discord).

WhatsApp uses Baileys for QR-code pairing — you don’t need a Meta Business API account, just a phone with WhatsApp installed.1. Enable the channel

openclaw config set channels.whatsapp.enabled true --strict-json

2. Register + scan the QR code

openclaw channels add --channel whatsapp

OpenClaw prints a QR code in the terminal. On your phone:

Open WhatsApp → Settings → Linked Devices → Link a Device
Scan the QR code shown in your terminal

Once paired, your account is the OpenClaw bridge — DMs to yourself or contacts you message will be routed to the agent.3. Run the gateway + smoke test

openclaw gateway

DM yourself or have a friend DM you:

“List my connected social accounts”

The first message triggers a pairing-code prompt in the terminal. Approve with openclaw admin pair-code <code>.

WhatsApp’s Baileys integration runs against a real account — treat it like a personal phone session. Don’t share your terminal session and don’t run multiple OpenClaw instances against the same WhatsApp account.

Telegram is the fastest channel to set up — just one bot token, no scopes, no intents.1. Create a bot with @BotFather

Open Telegram, message @BotFather
Send /newbot, follow the prompts (name + username)
Copy the bot token BotFather sends you (looks like 1234567890:ABC...)

2. Wire the token

export TELEGRAM_BOT_TOKEN="1234567890:ABC..."

openclaw config set channels.telegram.token \
  --ref-provider default --ref-source env --ref-id TELEGRAM_BOT_TOKEN
openclaw config set channels.telegram.enabled true --strict-json

3. Register the channel

openclaw channels add --channel telegram

4. Run the gateway + smoke test

openclaw gateway

Find your bot in Telegram (search by the username you set), tap Start, then send:

“List my connected social accounts”

Approve the pairing code in the terminal.

iMessage support requires a Mac running BlueBubbles Server — Apple doesn’t expose iMessage on other platforms, so the only way is to bridge through a Mac you control.1. Install BlueBubbles Server on your Mac

Download from bluebubbles.app and follow the installer
Sign in with the Apple ID associated with iMessage on that Mac
In BlueBubbles Server settings, copy the server URL (e.g. http://192.168.1.20:1234) and the password

2. Wire BlueBubbles into OpenClaw

export BLUEBUBBLES_SERVER_URL="http://192.168.1.20:1234"
export BLUEBUBBLES_PASSWORD="your-bluebubbles-password"

openclaw config set channels.bluebubbles.serverUrl "$BLUEBUBBLES_SERVER_URL"
openclaw config set channels.bluebubbles.password "$BLUEBUBBLES_PASSWORD"
openclaw config set channels.bluebubbles.enabled true --strict-json

3. Register the channel

openclaw channels add --channel bluebubbles

4. Run the gateway + smoke test

openclaw gateway

iMessage yourself or another contact:

“List my connected social accounts”

Approve the pairing code in the terminal.

The Mac running BlueBubbles must stay awake and signed in for iMessage routing to work. The legacy imessage channel slug is deprecated — use bluebubbles.

Microsoft Teams uses the Bot Framework — register your bot once, then connect Teams as a channel.1. Register an Azure Bot resource

In the Azure Portal, create a new Azure Bot resource
Note the Microsoft App ID and create a new client secret under Certificates & secrets
Under Channels, add Microsoft Teams as an enabled channel
Under Configuration, set the messaging endpoint — for OpenClaw’s gateway, use the public URL of your tunneled local instance (e.g. via ngrok: https://abc.ngrok.io/teams/messages)

2. Wire credentials into OpenClaw

export MSTEAMS_APP_ID="<your-app-id>"
export MSTEAMS_APP_PASSWORD="<your-client-secret>"

openclaw config set channels.msteams.appId "$MSTEAMS_APP_ID"
openclaw config set channels.msteams.appPassword "$MSTEAMS_APP_PASSWORD"
openclaw config set channels.msteams.enabled true --strict-json

3. Register + run

openclaw channels add --channel msteams
openclaw gateway

4. Add the bot to a Teams chatFrom your Teams client, search for your bot by name and start a 1:1 chat. Send:

“List my connected social accounts”

Approve the pairing code in the terminal.

Microsoft Teams requires a publicly reachable HTTPS endpoint. For development, use ngrok or Cloudflare Tunnel; for production, host the gateway behind a stable URL.

Google Chat uses an HTTP webhook — no OAuth, just a webhook URL.1. Create a Google Chat app

In the Google Cloud Console, enable the Google Chat API
Go to Google Chat API → Configuration, set:
- App name + avatar
- Connection settings → HTTP endpoint → paste your OpenClaw gateway’s public URL (e.g. https://abc.ngrok.io/googlechat/messages)
- Visibility → make available to your organisation or specific users

2. Wire the webhook secret into OpenClaw

export GOOGLECHAT_WEBHOOK_SECRET="<your-shared-secret>"

openclaw config set channels.googlechat.webhookSecret "$GOOGLECHAT_WEBHOOK_SECRET"
openclaw config set channels.googlechat.enabled true --strict-json

3. Register + run

openclaw channels add --channel googlechat
openclaw gateway

4. DM the bot from Google ChatIn Google Chat, find your app under Apps and start a direct message:

“List my connected social accounts”

Approve the pairing code in the terminal.

Why no WebChat? Older OpenClaw tutorials referenced a webchat channel — it isn’t a real user-facing channel in the current CLI (it’s an internal routing constant). openclaw channels add --channel webchat returns unknown channel id: webchat. For a fast, no-account-needed test, use Telegram above (~1 minute via @BotFather).

15 more channels (+ 1 coming-soon)

Long-tail channels (one-line setup pointers)

Channel	Slug	Setup
Feishu / Lark	`feishu`	WebSocket bot — docs
LINE	`line`	Messaging API bot credentials — docs
Matrix	`matrix`	Homeserver URL + access token — docs
Mattermost	`mattermost`	Bot API + WebSocket — docs
Nextcloud Talk	`nextcloud-talk`	Self-hosted Nextcloud — docs
Signal	`signal`	`signal-cli` pairing — docs
Twitch	`twitch`	IRC bridge — docs
Zalo	`zalo`	Bot API — docs
Zalo Personal	`zalouser`	QR login — docs
Tlon	`tlon`	Urbit-based account — docs
QQ	`qqbot`	Tencent QQ Bot API — docs
Nostr	`nostr`	NIP-04 DMs — docs
IRC	`irc`	Server address + pairing — docs
Synology Chat	`synology-chat`	NAS webhook — docs
iMessage (legacy)	`imessage`	Deprecated — use `bluebubbles` instead
WeChat	`wechat`	🚧 Not in current CLI — listed in OpenClaw’s README but `openclaw channels add --channel wechat` returns `Unknown channel`. Track support at the OpenClaw repo.

What you can ask after pairing

The same prompts work on every channel:

“What social accounts do I have connected?”
“Schedule a tweet ‘launching today’ for tomorrow at 9am UTC.”
“Generate a Friday product-launch caption for LinkedIn and schedule it for 5pm.”
“How did my Twitter posts perform last week?”
“Reply to that DM with my saved ‘pricing’ template.”

See the full prompt list under What you can ask.

Universal troubleshooting

Missing config on openclaw gateway: you skipped the prerequisite — run openclaw onboard (or openclaw setup --non-interactive --accept-risk) before adding any channel.
Bot doesn’t respond at all: make sure openclaw gateway is running. It’s the daemon that listens on every channel — if it’s not running, no messages get through.
First message stuck: OpenClaw requires pairing on first use. The first DM triggers a code printed in the terminal; approve with openclaw admin pair-code <code>.
Discord-specific: Message Content Intent must be enabled on the developer portal, otherwise the bot can’t read DMs.
Slack-specific: missing OAuth scopes (im:history, im:read, chat:write); reinstall the app to your workspace after adding scopes.
Skill not eligible: openclaw skills list --eligible should include so-me-studio. If not, SOMESTUDIO_API_KEY isn’t visible to the gateway shell — export it in the same terminal where you run openclaw gateway.
Multiple channels not all working: each channel has its own enabled flag; check status with openclaw channels status.
MS Teams or Google Chat unreachable: these require a public HTTPS endpoint for OpenClaw’s gateway. Use ngrok or Cloudflare Tunnel during development.

How it works

┌──────────────────┐
│  OpenClaw agent  │
└────────┬─────────┘
         │ reads SKILL.md from @social-media-scheduler/cli's npm install
         ▼
┌──────────────────┐
│  SKILL.md +      │
│  tools.md +      │
│  examples/       │
└────────┬─────────┘
         │ invokes
         ▼
┌──────────────────┐         ┌────────────────────────┐
│  CLI (so-me)     │ ──────► │  api.so-me.studio/v1   │
└──────────────────┘         └────────────────────────┘

The skill body (SKILL.md) is a system-prompt extension that teaches the agent how to use the so-me CLI. The CLI returns structured JSON for every operation, so the agent can parse, reason, and chain calls.

Hard rules baked into the skill

Never invent account / post / conversation IDs — always look them up first.
scheduledAt is ISO 8601 UTC and strictly in the future.
Multi-step jobs (e.g. AI image → post) are chained sequentially.
Never reveal API keys or webhook secrets, even when asked.

Updates

When new tools ship in Social media studio, the SKILL.md and tools.md are regenerated and @social-media-scheduler/cli is republished. Users re-run npm install -g @social-media-scheduler/cli to pick up the latest.

Source

The skill source lives in the Social media studio monorepo at apps/cli/SKILL.md. PRs welcome.

Other agents?

If you use a different agent runtime:

Hermes 4 — see the Hermes integration, which uses the same MCP backend via npm install -g @so-me/hermes-agent.
Claude Desktop / Cursor / OpenCode — point them at our MCP server directly. No skill or runtime needed.

Anything else (LangGraph, CrewAI, OpenAI Assistants, Anthropic API) — generate a tool definition file in their preferred format:

so-me agent export-tools --format openai --out tools.openai.json
so-me agent export-tools --format anthropic --out tools.anthropic.json
so-me agent export-tools --format mcp --out tools.mcp.json

MCP Server

Other Agents

Install

Or via ClawHub

What you can ask

Chat from any messenger

First-time prerequisite

The pattern (works for any channel)

Top 7 — full setup

15 more channels (+ 1 coming-soon)

What you can ask after pairing

Universal troubleshooting

How it works

Hard rules baked into the skill

Updates

Source

Other agents?

​Install

​Or via ClawHub

​What you can ask

​Chat from any messenger

​First-time prerequisite

​The pattern (works for any channel)

​Top 7 — full setup

​15 more channels (+ 1 coming-soon)

​What you can ask after pairing

​Universal troubleshooting

​How it works

​Hard rules baked into the skill

​Updates

​Source

​Other agents?

Install

Or via ClawHub

What you can ask

Chat from any messenger

First-time prerequisite

The pattern (works for any channel)

Top 7 — full setup

15 more channels (+ 1 coming-soon)

What you can ask after pairing

Universal troubleshooting

How it works

Hard rules baked into the skill

Updates

Source

Other agents?