Skool scheduler
Classroom posts with a title and a body.
Skool connects with classroom cookies (unofficial). On Create you get a title plus the caption as the body. Media is not supported. Classroom comments can show in Inbox while cookies still work. There are no Skool DMs.
Named AI models, then the composer
Generate the file with Veo, Nanobanana, Kling, Recraft, Grok, Flux, or Seedance, then schedule it to Skool from the same login. You are not exporting from another lab.
One clip, 19 networks
Cross-post the same encode to TikTok, Reels, Shorts, and the rest of Postlaty’s 19 channels. Each network keeps its own caption.
Inbox where the API allows it
Skool inbox: Comments. Reply from Postlaty instead of hopping into the native app for every thread.
Cursor, Claude, ChatGPT via MCP
Connect Skool once. Then an agent on REST or MCP can generate and schedule to this account. Setup lives on each agent page (for example /cursor).
Frequently asked questions
How do I schedule Skool posts with Postlaty?
Sign up, connect Skool (Credentials on Connect), then create in the AI tab or upload a file and schedule from the composer. Starter is $29/month for 10 channels across 19 networks, with a 7-day trial.
Is Skool an official API?
No. Postlaty uses classroom cookies, the same practical path other schedulers use. Expect a title field, a text body, and comments when the session is valid. If cookies expire, reconnect. DMs are not available.
Can Cursor or Claude post to Skool?
Yes. Create an API key in Profile, add the Postlaty MCP server to the agent, connect Skool in the app, then ask it to generate and schedule. Same pipeline as the UI.
Is Postlaty only a Skool tool?
No. Skool is one of 19 networks. The same subscription includes the AI studio, inbox where supported, REST, and MCP.