Post to Skool from ClipSpeed CLI
ClipSpeed CLI can post to your community on Skool through ClipSpeed. Add the ClipSpeed server with one command, sign in, and then ask ClipSpeed CLI to post to your community, pick the time, and apply Skool's settings, without leaving any agent that can run a command. Skool is on the roadmap on ClipSpeed's rail; this page describes how it works and says so.
Keep a human in the loop: ClipSpeed CLI 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 ClipSpeed CLI
The commands below are the plan. They are not published yet, and this page says so. The MCP server is the route that works today. Connect Skool in ClipSpeed, then describe the post. Setup takes about a minute.
# One-time setup (OAuth, no API key)
# Planned, not yet published:
npm i -g clipspeed
clipspeed auth:login # device-code sign-in, or CLIPSPEED_API_KEY
clipspeed channels:list
# Then ask ClipSpeed CLI:
> Post the welcome message in General Monday 9am
ClipSpeed CLI: Preview — nothing booked yet. Skool — title. Book it?Status: coming. Command names may change before release; this page will be regenerated with the final ones.
- Today: use the MCP server from any client that supports it; the URL is https://api.clipspeed.ai/mcp.
- Soon: npm i -g clipspeed, then clipspeed auth:login (device code) or export CLIPSPEED_API_KEY.
- The SKILL.md installs with the package and states the rules: read channels:settings before posting, never skip the approval step, preview a plan before booking.
- Connect Skool in the ClipSpeed app, or ask ClipSpeed CLI for a connect link: it is private, valid for ten minutes, and Skool signs you in itself.
Developer reference: the ClipSpeed CLI MCP page.
What can ClipSpeed CLI do on Skool?
On Skool, ClipSpeed CLI 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 ClipSpeed CLI 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. ClipSpeed CLI 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, ClipSpeed CLI can read back views and engagement where Skool provides them.
How does ClipSpeed CLI post to Skool through ClipSpeed?
You describe what you want in plain language and ClipSpeed CLI makes the ClipSpeed calls. A typical conversation has three beats.
Find your Skool channel
Ask ClipSpeed CLI 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. ClipSpeed CLI 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 ClipSpeed CLI 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 ClipSpeed CLI for any of these and it applies the matching settings.
Welcome post
Lesson recap with a clip
Image
Preview
Example prompts for Skool in ClipSpeed CLI
Type these into any agent that can run a command. ClipSpeed CLI 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 ClipSpeed CLI 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
ClipSpeed CLI 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. ClipSpeed CLI 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. ClipSpeed CLI 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: ClipSpeed CLI 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 ClipSpeed CLI?
The ClipSpeed CLI is a command-line tool, in progress, for agents that install skills and run commands rather than connecting to MCP servers: OpenClaw-family agents, Grok Bot, Paperclip, Perplexity Computer and others. It will mirror the MCP tools (channels, posts, upload, clip) and ship with a SKILL.md so an agent learns the commands and the rules on install.
How ClipSpeed works with ClipSpeed CLI
- Planned commands mirror the MCP tools
- Reads platform rules
- Exact-or-refused booking
- preview before booking
- Key or device-code sign-in
CLI vs MCP server vs npm clipspeed-mcp: ClipSpeed CLI (any machine), MCP server (hosted), clipspeed-mcp (npm) (local stdio). This page is about ClipSpeed CLI; the ClipSpeed CLI guide compares them.
---
name: clipspeed
description: Clip videos, generate images and video, and schedule posts with ClipSpeed
requirements:
env: [CLIPSPEED_API_KEY]
binaries: [clipspeed]
---
# Rules
- Run `clipspeed channels:settings <platform>` before composing a post.
- Always preview a plan before booking; never skip the user's approval.
- A refused slot comes back with the next open one; use it, never guess.
# Commands
- clipspeed channels:list
- clipspeed posts:create --platform x --text "..." --at 2026-11-17T09:00
- clipspeed posts:list --from today --to +7d
- clipspeed clip:create <url> · clipspeed clip:status <projectId># 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 ClipSpeed CLI
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 ClipSpeed CLI guide.
Also works with
Skool and ClipSpeed CLI: frequently asked questions
How do I post to Skool from ClipSpeed CLI?
Today: use the MCP server from any client that supports it; the URL is https://api.clipspeed.ai/mcp. Soon: npm i -g clipspeed, then clipspeed auth:login (device code) or export CLIPSPEED_API_KEY. Connect Skool in ClipSpeed (or ask ClipSpeed CLI for a connect link; it is private and valid for ten minutes), then describe the post in plain language. ClipSpeed CLI 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 ClipSpeed CLI 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 ClipSpeed CLI 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 ClipSpeed CLI 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 ClipSpeed CLI talks to ClipSpeed over OAuth. No Skool developer key, bearer token or password is pasted anywhere.
How many Skool posts a day can ClipSpeed CLI 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 posts go out to Skool while I am away?
Yes. Once booked, ClipSpeed publishes at the scheduled minute whether or not ClipSpeed CLI is open. For unattended runs that decide what to post, use a headless agent such as Claude Code or Codex with the same account.
Is posting to Skool from ClipSpeed CLI different from MCP server?
The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. ClipSpeed CLI: any machine with node; installed by the agent. MCP server: hosted, works today.