SocialClaw - Social Claw is a social media scheduling skill for AI agents posting to X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest
by @ndesv21
Use when a user wants social media scheduling and publishing for AI agents on X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Red...
clawhub install socialclawπ About This Skill
name: socialclaw description: Use when a user wants social media scheduling and publishing for AI agents on X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest through SocialClaw. homepage: https://getsocialclaw.com metadata: {"openclaw":{"homepage":"https://getsocialclaw.com","primaryEnv":"SC_API_KEY","requires":{"env":["SC_API_KEY"]},"install":[{"id":"npm","kind":"node","package":"socialclaw","bins":["socialclaw","social"],"label":"Install SocialClaw CLI (npm)"}]}}
SocialClaw is a social media scheduling skill for AI agents posting to X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest
SocialClaw is a workspace-scoped social publishing service at https://getsocialclaw.com.
What this skill is
This skill is an instruction layer for the hosted SocialClaw service.
It does not contain the SocialClaw backend or the provider integrations themselves. It teaches an OpenClaw-compatible agent how to:
socialclaw CLI if it is already installedThis skill can work without the CLI. The CLI is only an optional client for the same hosted service.
Use this skill when the user wants to:
Do not use this skill for editing the SocialClaw codebase itself. This bundle is for operating a deployed SocialClaw workspace.
Defaults
https://getsocialclaw.comAuthorization: Bearer socialclaw CLI when installedRuntime requirements
SC_API_KEYhttps://getsocialclaw.comsocialclaw (or social) if already installedOptional CLI
SocialClaw also has a separate npm CLI package named socialclaw.
Prefer it when it is already installed or the user wants command-line examples. The CLI is a client for the hosted SocialClaw service. It can:
socialclaw install --claudeThe CLI is optional. This skill does not require it to function.
If the user explicitly wants the CLI and it is not installed yet:
npm install -g socialclaw
Quick start
If the user does not have a workspace API key yet:
open https://getsocialclaw.com/dashboard
Then tell them:
Set:
export SC_API_KEY=""
If the CLI is installed, log in with it:
socialclaw login --api-key
Otherwise validate the key over HTTP:
curl -sS \
-H "Authorization: Bearer $SC_API_KEY" \
"https://getsocialclaw.com/v1/keys/validate"
If execution fails with plan_required, subscription_inactive, subscription_past_due, subscription_paused, or subscription_canceled, direct the user to:
https://getsocialclaw.com/pricinghttps://getsocialclaw.com/dashboardOperating rules
1. Start by confirming the user has a SocialClaw workspace API key.
2. If the user does not have a key yet, send them to https://getsocialclaw.com/dashboard to sign in with Google and create one.
3. A workspace API key alone is not sufficient for execution. If billing-related errors appear, route the user to pricing or dashboard billing instead of retrying commands.
4. Never ask the user for provider app secrets. End users connect accounts inside SocialClaw.
5. Prefer explicit provider/account-type language:
- Facebook Pages, not Facebook personal profiles
- Instagram Business linked to a Facebook Page
- Instagram standalone professional accounts
- LinkedIn profile and LinkedIn page are separate providers
- Pinterest is board-centric; inspect capabilities/actions before assuming sections, catalogs, or advanced surfaces
6. If a provider workflow is not supported, say so directly instead of inventing a workaround.
7. Treat Pinterest product, collection, and idea surfaces as capability-gated or beta unless account capabilities/actions explicitly advertise them.
8. Avoid echoing full API keys back into chat.
Main workflow
1. Confirm the user has a workspace API key. 2. If needed, direct the user to the dashboard to sign in with Google and create a key. 3. Validate workspace access. 4. List accounts or start a connection flow. 5. Inspect capabilities/settings for the target account. 6. Upload media if needed. 7. Validate or preview the post/campaign. 8. Apply it. 9. Inspect posts, runs, analytics, or retry/reconcile if needed.
Essential examples
If the CLI is installed, prefer commands like these:
Store the workspace key:
socialclaw login --api-key
Start a connection flow:
socialclaw accounts connect --provider youtube --open
Start a Pinterest OAuth connection:
socialclaw accounts connect --provider pinterest --open
Connect Telegram manually with a bot token and chat target:
socialclaw accounts connect --provider telegram --bot-token --chat-id @yourchannel --json
Connect Discord manually with a channel webhook URL:
socialclaw accounts connect --provider discord --webhook-url --json
List connected accounts:
socialclaw accounts list --json
Upload media:
socialclaw assets upload --file ./image.png --json
Validate a schedule:
socialclaw validate -f schedule.json --json
Apply a schedule:
socialclaw apply -f schedule.json --json
Install the Claude Code command:
socialclaw install --claude
Inspect a post:
socialclaw posts get --post-id --json
Connection workflow
For browser-based account linking:
socialclaw accounts connect --provider --open
- then socialclaw accounts status --connection-id --json
POST /v1/connections/start
- return the authorize URL to the user or open it if browser tools are available
- poll GET /v1/connections/:connectionIdSupported providers:
xfacebookinstagram_businessinstagramlinkedinlinkedin_pagepinteresttiktokdiscordtelegramyoutuberedditwordpressTelegram and Discord are the exceptions to the browser-based OAuth flow.
Telegram is connected manually with:
chat_id or @channelusernameFor Telegram:
socialclaw accounts connect --provider telegram --bot-token --chat-id <@channel|chat_id> --json
POST /v1/connections/start with {"provider":"telegram","botToken":"...","chatId":"..." }Discord is connected manually with:
For Discord:
socialclaw accounts connect --provider discord --webhook-url --json
POST /v1/connections/start with {"provider":"discord","webhookUrl":"..." }Read next
π‘ Examples
If the user does not have a workspace API key yet:
open https://getsocialclaw.com/dashboard
Then tell them:
Set:
export SC_API_KEY=""
If the CLI is installed, log in with it:
socialclaw login --api-key
Otherwise validate the key over HTTP:
curl -sS \
-H "Authorization: Bearer $SC_API_KEY" \
"https://getsocialclaw.com/v1/keys/validate"
If execution fails with plan_required, subscription_inactive, subscription_past_due, subscription_paused, or subscription_canceled, direct the user to:
https://getsocialclaw.com/pricinghttps://getsocialclaw.com/dashboard