Skool publishing as software
Codex runs postqueen commands, reads the JSON results and verifies each step, so your Skool pipeline behaves like any other task it automates in CI or cron.
Point Codex at the postqueen CLI and it creates, schedules and verifies Skool posts as one repeatable task you can rerun any time.
Set up the CLI inside the workspace Codex uses, then describe the Skool outcome you want in the task prompt.
# Inside a Codex sessionnpm install -g postqueenexport POSTQUEEN_API_KEY=your_api_key # Then prompt:# "Create this week's Skool posts# from notes.md and schedule them# with postqueen"Codex runs postqueen commands, reads the JSON results and verifies each step, so your Skool pipeline behaves like any other task it automates in CI or cron.
Tell Codex when your communities are busiest and it schedules posts into that window on Skool, day after day, without reminders.
Codex targets the exact communities you choose and keeps every submission reviewable, so you can check each one against community rules first.
Ask Codex for drafts only. They sit on the postqueen calendar unscheduled, so you can edit them and pick the time yourself, and nothing reaches your members on Skool until you do.
Codex calls postqueen to list your connected communities and sees what Skool supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Skool-shaped posts and proposes publish times that match when your members are around.
Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and Codex can pull the results after.
Codex reads these limits from postqueen before it composes, so a draft that would be rejected never reaches the queue.
Scheduling, AI drafts, analytics and team roles, in one guide.
Install the postqueen CLI where Codex runs commands and export your API key. Every command returns JSON, so the agent can create, schedule and list Skool posts reliably.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the posts it creates, keeping your communities active on a steady rhythm.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the posts wait on the calendar until you set a time. Tell it to schedule, and they go out at the times you can see, which is the setup most people move to once they trust the output.
Yes. postqueen connects 30 channels, so Codex can turn the same brief into Skool posts plus adapted versions for every other channel you run.
No. The agent uses your regular API key and plan limits: unlimited posts on every plan, and channel counts from 5 on Creator up to uncapped on Ultimate.
Yes. The built-in assistant drafts discussion prompts, weekly threads and announcements in your voice, and you decide when each one publishes. Agents like Claude Code or OpenClaw can prepare a month of prompts through the CLI or the MCP server.
Skool is a community platform rather than a feed network, so it does not expose post-level reach the way an ad-driven network does. postqueen keeps your publishing history and the calendar that produced it, while Skool's own leaderboard and member activity views remain the place to read engagement.
Queue this week's posts in minutes, or hand the whole thing to your favorite AI. postqueen keeps publishing either way.
Seven days free. Cancel in one click from settings.