Post to Skool from nanoclaw
nanoclaw can post to your community on Skool through ClipSpeed. Add the ClipSpeed server with one config block, sign in, and then ask nanoclaw to post to your community, pick the time, and apply Skool's settings, without leaving a small self-hosted agent you message from WhatsApp or Telegram. Skool is on the roadmap on ClipSpeed's rail; this page describes how it works and says so.
Keep a human in the loop: nanoclaw shows the plan and asks before anything is public. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn.
Also try
How to post Skool from nanoclaw
nanoclaw has no browser for OAuth, so it uses a ClipSpeed API key in a header. Generate the key, add the server, restart. Connect Skool in ClipSpeed, then describe the post. Setup takes about a minute.
# One-time setup: nanoclaw MCP config
{
"mcpServers": {
"clipspeed": {
"url": "https://api.clipspeed.ai/mcp",
"headers": { "Authorization": "Bearer csai_live_..." }
}
}
}
# Then ask nanoclaw:
> Post the welcome message in General Monday 9am
nanoclaw: Preview — nothing booked yet. Skool — title. Book it?nanoclaw sits in the compatible tier: same protocol as the verified clients, not yet driven end to end by ClipSpeed.
- Generate a key in ClipSpeed under Account → API & Integrations.
- Add the clipspeed server with the URL and Authorization header to nanoclaw's MCP configuration.
- Restart nanoclaw and message it: list my ClipSpeed channels.
- Connect Skool in the ClipSpeed app, or ask nanoclaw for a connect link: it is private, valid for ten minutes, and Skool signs you in itself.
Developer reference: the nanoclaw MCP page.
What can nanoclaw do on Skool?
On Skool, nanoclaw can post titled community posts with media to a category. Every booking runs through the same rules as the ClipSpeed app.
Text, Image and Video posts
Skool takes text, image and video through ClipSpeed. Video: linked by URL. Image: JPG or PNG.
10,000 characters, checked at booking
Skool's own arithmetic. Too long is refused with the real count, never trimmed at send time. Titles are required and cap at 200.
Exact time or refused
Name the minute and nanoclaw books it, or you are told why not and offered the next open slot. A booked Skool post is never moved behind your back.
Preview before anything posts
preview: true runs the whole booking and writes nothing. nanoclaw shows the plan, with each slot and the day's remaining cap, and books only on your yes.
Clips cut in the same chat
Submit a video or stream link, get captioned 9:16 clips with a viral score, and post the best as native video on Skool. No download, no re-upload.
Pacing and numbers
Planned: Text posts on Skool are at least 60 minutes apart, up to 5 a day. After a post goes out, nanoclaw can read back views and engagement where Skool provides them.
How does nanoclaw post to Skool through ClipSpeed?
You describe what you want in plain language and nanoclaw makes the ClipSpeed calls. A typical conversation has three beats.
Find your Skool channel
Ask nanoclaw whether Skool is connected. It calls list_channels and reads platform_settings, so it also knows what Skool accepts and the limits before you write a word.
Compose within the rules
Describe the post. nanoclaw drafts within Skool's limits; mention a clip or a file and it attaches it.
Schedule or publish
Name a time, or say now. The slot is booked exactly or refused with the next open one, and the reply carries the id you can cancel or edit by.
Skool settings reference
These are the schedule_post fields that apply to Skool. Mention any of them in plain language and nanoclaw sets them; the server checks them at booking. Fields marked planned land with the Skool release.
| Field | Type | Required | What it does on Skool |
|---|---|---|---|
platforms | string[] | Yes | Include "skool". Up to ten platforms per call; each books its own slot. |
title | string | Yes | The post title. |
text | string | Yes | The body. |
category | string | Planned | The community category. |
media_url | string | No | An image, or a video link. |
scheduled_at | ISO 8601 | No | Exact or refused with the next open slot. |
preview | boolean | No | Plan only. |
Common Skool configurations
Ask nanoclaw for any of these and it applies the matching settings.
Welcome post
Lesson recap with a clip
Image
Preview
Example prompts for Skool in nanoclaw
Type these into a small self-hosted agent you message from WhatsApp or Telegram, or pass one to routine in a script. nanoclaw calls ClipSpeed and confirms before publishing.
Post Skool with a scheduled time
Post the welcome message in General Monday 9am. Keep the text under 10,000 characters. Preview first.
Cut the clips, then post the best
Clip this link, keep the top three by viral score, and schedule them to Skool at 11am, 3pm and 7pm tomorrow with titles written from each hook. Show me the plan before booking.
Check and adjust the Skool calendar
What is scheduled on Skool this week? Cancel tomorrow's post and tell me the next open Skool slot on Friday.
Skool limits and gotchas to know
Skool enforces a few rules that nanoclaw and ClipSpeed respect automatically, but knowing them helps you phrase requests.
- A title is required; posts go to a category.
- Skool's API access is limited; the release depends on it.
- Skool is on ClipSpeed's roadmap, not the next rail. Bookings are refused plainly until it posts.
- Video is linked rather than uploaded.
- Pacing is conservative: five posts a day.
| Rule | Skool |
|---|---|
| Accepts | Text, Image, Video |
| Text limit | 10,000 characters |
| Title | 200 characters, required |
| Links in the caption | Kept with a preview |
| Pacing | Planned: Text posts on Skool are at least 60 minutes apart, up to 5 a day. |
| Formats | Image: JPG or PNG. Video: linked by URL. Aspect: any |
| Status | On the roadmap; described here, not yet bookable |
What Postiz-style schedulers cannot do
Cut the clips first
nanoclaw does not need finished video to start. Hand it a YouTube link, a podcast, a stream VOD or a local export. ClipSpeed finds the moments, cuts them to 9:16 with word-by-word captions, scores each one 0 to 100 for shareability, and returns them in the same conversation. nanoclaw picks by score, writes the caption from the transcript, and books the clips on Skool. Three tool calls, one approval, no download and no re-upload.
- Clips arrive with a title written from the hook, a transcript and a viral score, so the agent can choose and caption without watching the footage.
- Live streams can be clipped while they are still on air; the agent books the highlights for the next morning before the stream ends.
- Every clip is already hosted, so
schedule_posttakes its id directly. Nothing moves through your laptop.
submit_to_clipspeedPaste the link. ClipSpeed starts the job and returns a project id.check_clipsPoll with the project id. Back come the finished 9:16 clips with titles, transcripts, viral scores and preview links.schedule_postPass the clip id, the platforms, a caption and a time. nanoclaw shows the plan with preview: true, you say yes, it books.generate_image or generate_videoDescribe the shot. ClipSpeed runs it on the model that fits (Seedance, Kling, Veo, Nano Banana Pro, GPT Image and others) and quotes the credits first.wait_for_generationReturns the hosted result link and a preview the agent can show you.schedule_post with media_urlThe result link goes straight into the booking on Skool. The caption, the time and the file are approved together.The other half nobody else has
Generate the image or video, then post it
A product shot for Instagram, a 16:9 announcement graphic for X, a six-second opener before a clip: nanoclaw can make an image or a short video with ClipSpeed's image and video models and book the result in the same reply. There is no separate design tool, no export, no upload page. The generated file is hosted, so media_url is the only thing the booking needs.
- The price in credits is quoted before anything renders, within the per-generation and daily caps you set in Settings.
- Results are previewed in the conversation, so you approve the picture and the post at once.
- Images post as JPG, PNG or WebP up to 25 MB; video posts as MP4, MOV or WebM up to 1 GB.
What is nanoclaw?
nanoclaw is a minimal open-source personal agent in the OpenClaw family: it runs on your own machine, takes instructions from WhatsApp or Telegram, and can call MCP servers. With ClipSpeed configured with an API key, a message to your agent can clip a video and schedule posts.
How ClipSpeed works with nanoclaw
- Connects over HTTP with a Bearer key
- Reads platform rules
- Exact-or-refused booking
preview: truefor plans it messages you- Same tools everywhere
nanoclaw vs OpenClaw vs Hermes Agent: nanoclaw (your machine; whatsapp, telegram), OpenClaw (your machine; many channels), Hermes Agent (your server). This page is about nanoclaw; the nanoclaw guide compares them.
{
"mcpServers": {
"clipspeed": {
"url": "https://api.clipspeed.ai/mcp",
"headers": { "Authorization": "Bearer ${CLIPSPEED_API_KEY}" }
}
}
}# What the agent reads at connect time (tool descriptions, abridged)
list_channels Connected platforms, what each accepts, limits, your time zone
connect_channel A private 10-minute link to connect one platform
platform_settings Limits, title rules, link handling, pacing per platform
schedule_post clip_id | text | media_url → platforms[], scheduled_at, preview
list_scheduled_posts Scheduled, sending, posted, failed — with post links
update_scheduled_post Edit copy while still scheduled (the time never moves)
cancel_scheduled_post Cancel; undoable 72 h in the app
post_analytics Views, likes, comments, shares where the platform gives them
submit_to_clipspeed Start clipping a video or stream link → projectId
check_clips Finished 9:16 clips with titles, transcripts, viral scores
generate_image / generate_video / wait_for_generation
# Skool: text/image/video · text 10,000 · title 200 requiredPost to Skool and other platforms from nanoclaw
One request can book the same content to Skool and other channels, each keeping its own settings and its own slot. Every platform below has its own nanoclaw guide.
Also works with
Skool and nanoclaw: frequently asked questions
How do I post to Skool from nanoclaw?
Generate a key in ClipSpeed under Account → API & Integrations. Add the clipspeed server with the URL and Authorization header to nanoclaw's MCP configuration. Connect Skool in ClipSpeed (or ask nanoclaw for a connect link; it is private and valid for ten minutes), then describe the post in plain language. nanoclaw reads the Skool rules, drafts within them, shows the plan and books on your yes. Skool is on the roadmap; until the badge changes, the booking is refused with a plain message.
What can nanoclaw post to Skool through ClipSpeed?
Post titled community posts with media to a category. Skool takes text, image and video posts. Text is limited to 10,000 characters. A title is required and is capped at 200 characters.
Which Skool settings can nanoclaw control?
The fields in the settings reference above: title, text, category, media_url, scheduled_at, preview. Mention any of them in plain language ("unlisted", "tomorrow at 9", "preview first") and nanoclaw sets the matching field before it books.
Do I need a Skool API key or developer account?
No. You connect Skool to ClipSpeed once through Skool's own sign-in, and nanoclaw talks to ClipSpeed over OAuth. No Skool developer key, bearer token or password is pasted anywhere.
How many Skool posts a day can nanoclaw schedule?
Planned: Text posts on Skool are at least 60 minutes apart, up to 5 a day. When a time is taken, the booking is refused with the next open slot rather than moved. Ask for preview to see a day's plan and the remaining cap before anything is booked.
Can nanoclaw post to Skool from a script or a cron job?
Yes. nanoclaw's headless mode (routine) runs one prompt and exits, and the ClipSpeed server registered on that machine does the booking. On a runner with no browser, authenticate with a ClipSpeed API key header. Keep preview on so the run reports a plan before it books.
Is posting to Skool from nanoclaw different from OpenClaw?
The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. nanoclaw: your machine; whatsapp or telegram. OpenClaw: your machine; many channels, more integrations.