# Nanoclaw social media automation

Run Nanoclaw as a Docker container, drop the open source Genviral skill into its mounted skills folder, and install the `genviral` CLI inside the container with one scoped API key. Message Nanoclaw from WhatsApp, Telegram, Slack, Discord, or Gmail to generate slideshows, images, and video, then schedule and publish across 10 connected platforms.

## What Nanoclaw owns

Nanoclaw runs container-isolated agents reachable from ordinary chat apps. Genviral is the only skill it needs to do social.

- Container-isolated runtime: Each Nanoclaw group runs in its own Docker sandbox (MicroVM on macOS and Windows). One isolated environment per client means API keys, skills, and memory never bleed between workspaces.
- Chat-app native interface: Talk to Nanoclaw from WhatsApp, Telegram, Slack, Discord, or Gmail. No dashboard to open and no terminal to switch into — the same chat that approves a draft can also publish it.
- Built-in scheduled jobs: Nanoclaw ships with cron-style recurring tasks: 'every Monday at 8am, draft three LinkedIn posts'. No external runner, no GitHub Action, no separate scheduler to keep alive.
- Auto-loading skills: Drop a folder into the skills directory and Nanoclaw discovers it. The Genviral skill, your house-brand voice notes, and any custom helpers all load side-by-side without re-deploying the container.

## What Genviral executes for Nanoclaw

Genviral is the execution layer Nanoclaw's skill calls into from inside its own container.

- Connected social accounts: TikTok, Instagram, YouTube, Pinterest, LinkedIn, Facebook, X, Bluesky, Mastodon, and Telegram behind one API key — no Meta or TikTok partner approval wait.
- AI media generation: Slideshows, images, and videos rendered through Genviral's AI Studio. No separate model wiring — Nanoclaw calls one endpoint and gets a finished asset.
- Cross-platform scheduling: One queue, every platform. Idempotent posting via `external_id`, retry-safe drafts, and per-account cooldowns Nanoclaw can drive from one endpoint.
- Analytics feedback loop: Genviral feeds last-30-day performance back to Nanoclaw so the next batch rewrites hooks against whichever format actually outperformed.

## Setup in five steps

Each step links to the real surface in the Genviral dashboard. Run them once, then let Nanoclaw take the recurring work from chat.

- Start Nanoclaw in a container. Nanoclaw runs as a Docker container that listens for messages on WhatsApp, Telegram, Slack, Discord, or Gmail. Each group lives in its own sandbox, so credentials and skills never leak between clients.
- Drop the Genviral skill into Nanoclaw's skills folder. Nanoclaw auto-discovers skills from its mounted skills directory. The Genviral skill ships an opinionated SKILL.md, slideshow workflow, defaults file, and a feedback loop tuned for social — no manual wiring required.
- Install the Genviral CLI and scope an API key. The skill shells out to `genviral`. Install the CLI inside the container, then create one API key per workspace Nanoclaw is allowed to drive and drop it into the container env so the skill picks it up on every message.
- Connect your social accounts in Genviral. Connect TikTok, Instagram, YouTube, Pinterest, LinkedIn, Facebook, X, Bluesky, Mastodon, and Telegram once in the dashboard. Nanoclaw never touches OAuth — it just reads the account list and uses the IDs from chat.
- Message Nanoclaw from your chat app. Open WhatsApp, Telegram, Slack, Discord, or Gmail and send Nanoclaw a sample request. It plans the work, calls the Genviral skill, renders the asset, and creates a draft post — all from one message thread.

## Recurring Nanoclaw workflows by platform

Each workflow follows the same loop: Nanoclaw plans from chat, Genviral renders and publishes, analytics feeds the next message.

- TikTok: Daily slideshows from a WhatsApp message. Message Nanoclaw once; it composes a 4-slide carousel, drafts it as a MEDIA_UPLOAD post, and waits for your thumbs-up in the same thread before publishing.
- Pinterest: Recurring infographic pins on cron. Set one recurring task and Nanoclaw pulls a recipe, generates an infographic, and ships the pin to a chosen board — every 8 hours, confirmations in chat.
- YouTube: Shorts from a shared queue. Nanoclaw watches the approved-shorts folder, fills `settings.youtube` from sidecar metadata, and publishes on the cadence you set in your Telegram chat.
- Instagram: Reels from an approved media folder. Point Nanoclaw at a Genviral media-library folder; new uploads get captioned, hashtagged, and queued without ever leaving the approval pipeline.
- LinkedIn: Posts from release notes & drafts. Nanoclaw summarizes the week's engineering output into voice-matched posts; Genviral publishes under the company page on a weekly cron.
- Facebook: Cross-post filler for brand-page trust. Nanoclaw mirrors the day's TikTok onto the Facebook page 30 minutes later, keeping the brand page warm so paid traffic and approvals stay healthy.

## Why Nanoclaw still needs an API layer

You could wire Nanoclaw into every platform's API yourself. In practice that is slow and breaks often.

- Meta and TikTok partner approvals can take months -> Genviral fronts those approvals so Nanoclaw posts on day one
- Every platform has its own auth, post settings, and quirks -> One endpoint per concept; Genviral maps it per platform
- AI assets need separate model providers and plumbing -> Genviral's AI Studio ships slideshows, images, and video in-API
- Scaling to many accounts gets you shadowbanned and locked out -> Hosted, pre-warmed accounts keep posting reliable past the early stage

## What is Nanoclaw?

Nanoclaw is a lightweight, container-based AI agent built on the Claude Agent SDK. It accepts natural-language commands from WhatsApp, Telegram, Slack, Discord, or Gmail and executes them inside an isolated Docker sandbox — one container per group or client, so credentials and state never leak between workspaces.

## How does Nanoclaw post to social media?

Nanoclaw itself doesn't ship with platform connectors. You install the Genviral skill into its skills directory and the `@genviral/cli` package inside the container. Nanoclaw then runs `genviral` shell commands for accounts, slideshows, posts, analytics, and trends — Genviral handles auth, rendering, scheduling, and publishing to every supported network.

## Do I need the Genviral skill, or just the CLI?

Both. Nanoclaw auto-discovers skills from its mounted skills directory; the Genviral skill ships SKILL.md, a slideshow workflow, defaults, and a feedback loop Nanoclaw loads automatically. The CLI is what the skill actually shells out to, so you install it alongside.

## Which platforms can Nanoclaw post to through Genviral?

TikTok, Instagram, YouTube, Pinterest, LinkedIn, Facebook, X, Bluesky, Mastodon, and Telegram. Analytics coverage is strongest for TikTok, Instagram, and YouTube. Nanoclaw publishes from your connected accounts via one API key — no Meta or TikTok partner approval wait.

## Does this need an MCP server?

No. Nanoclaw shells out to `genviral` directly the same way it runs `git` or `jq`. There is no separate MCP server to operate, no extra process to keep alive, and no MCP-specific wire format to maintain. If you already operate an MCP server, the CLI still works alongside it.

## Can Nanoclaw run on a schedule?

Yes — Nanoclaw has built-in cron-style recurring tasks. Tell it 'every Monday at 8am, draft three LinkedIn posts' from chat and it runs without an external runner. For cross-account fan-out at scale, the Hermes Agent integration is also a good fit.

## Is Nanoclaw safe to run for multiple clients?

Container isolation is the point. Each Nanoclaw group runs in its own Docker sandbox (MicroVM on macOS and Windows), so one client's API keys, skills, and memory can't reach another's. Combined with scoped Genviral API keys — one per workspace — agencies can give each client its own end-to-end environment.

---

Canonical HTML: https://www.genviral.io/nanoclaw