macOS
CLI or desktop build on Apple Silicon
OpenQuok Soon
Skool with ThinkRail is coming soon
We are finishing the Skool integration for ThinkRail. Check back soon for platform-specific workflows, examples, and setup guides.
Draft and schedule my product launch thread for Tuesday at 9am across Facebook, Instagram, and
Threads.
On it — openquok-core
Created drafts with cover image attached.
- • Facebook — Tue 9:00 AM
- • Instagram — Tue 9:00 AM
- • Threads — Tue 9:00 AM
✓ Queued for Tue 9:00 AM · ref oq-7f3a
Your worktree IDE
Chat with pi in ThinkRail,keep main clean
Open a repo. Cut a workspace worktree. Ask the agent to draft and schedule like any other task. The openquok-core skill runs in that worktree’s shell. It finds connected channels, attaches media, and queues posts. You can publish now, schedule for later, or save drafts and approve on OpenQuok when you are ready.
Built for community builders with ThinkRail
Who schedules Skool with ThinkRail?
Course & community owners
Keep groups warm with a steady calendar. Approve every post before it hits the feed. Message ThinkRail to draft Skool posts from chat — publish now, schedule, or approve on OpenQuok.
Coaches & creators
Batch announcements and prompts for multiple groups. Reuse drafts from agents without manual copy-paste. ThinkRail queues Skool drafts at volume — your team can publish now or approve first.
Agencies
Connect client Skool accounts from the dashboard with the extension. Pipe drafts via API or MCP after connect. Run ThinkRail per client workspace so Skool drafts stay isolated.
Connect once
authenticate in the worktreepick your workspacechat from the IDE securely
Choose an OpenQuok workspace, connect with OAuth2 — approve in your browser, and credentials stay on the machine that runs ThinkRail. Ask the agent in chat to draft and schedule without opening another app.
CLI authentication options
# OAuth2 device flow (interactive — opens browser)
openquok auth:login
openquok auth:statusCreate Post
Sample channels
These chips set format and character limits. They are not your accounts.
Editing a Specific Network
Rati Montreewat Settings
Groups load from your Skool account after you connect the channel.
Post Preview
Rati Montreewat
Jun 14, 9:00 AM
Week 12 — community update
OpenQuok Community· Announcements
Share what you shipped this week and ask one question to spark replies in the group.
Group settings
Pick the Skool groupset title and categorybefore you approve
Choose the target group from your connected account. Add a post title and category in Settings. Attach images when your group allows media. Preview the card before you queue the slot.
CLI command options
# Draft + human checklist (Skool)
openquok posts:create --json ./examples/skool-text-title-group.json
openquok posts:review-todo <post-id> --note "…"
openquok posts:status <post-id> --status draft
openquok posts:status <post-id> -s scheduleFollow-up comments
Add Skool comments after the postset delayskeep the thread
When the group allows it, add follow-up comment rows in the composer with delays and optional media. OpenQuok publishes the main post first. Then it posts each comment on your connected account.
CLI analytics options
# Skool post with follow-up reply
openquok posts:create --json ./examples/skool-follow-up.jsonCreate Post
Sample channels
These chips set format and character limits. They are not your accounts.
Editing a Specific Network
Workspace tools. Sign in or sign up to use your library, Photo Editor, and signatures.
84 / 5,000
Follow-up comments
Reply
Drag and drop images or videos here, or use the icons on the editor.
52/5000
Delay
09:00 + 600s ≈ 09:10:00
Post Preview
Rati Montreewat
Jun 14, 9:00 AM
Week 12 — community update
OpenQuok Community· Announcements
Share what you shipped this week and ask one question to spark replies in the group.
Scheduled replies
- After 10 min
Follow-up comment publishes after your chosen delay.
comparisons
agent-native scheduling, not another dashboard
Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for Skool from ThinkRail
Typical social scheduler SaaS
- Copy posts between your AI chat and a separate scheduling tool
- Siloed API keys and workflows that do not compose with your agent stack
- Always-on integrations that bloat agent context
- Locked to one vendor's models or automation layer
- One working tree mixing every experiment as you add channels and parallel sessions
- Autopilot publishing with no human checkpoint
OpenQuok + ThinkRail
- Ask the agent in ThinkRail to draft and schedule from the worktree
- Credentials stay on the machine that runs ThinkRail — workspace isolated
- Skills load on demand from ~/.pi or the worktree .pi/skills folder
- CLI-first openquok-core works beside any other pi skill or extension
- Git worktrees isolate each line of work — merge the good branch, delete the rest
- You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step
CLI
Command reference
Skool commands from the openquok-core skill — structured JSON on stdout, human-in-the-loop drafts, and workspace media uploads.
openquok integrations:list | jq -r '.[] | select(.identifier=="skool") | .id'Discover your Skool integration UUID
openquok integrations:settings "$SKOOL_ID"Get Skool posting rules, title/group schema, and allow-listed tools
openquok integrations:trigger "$SKOOL_ID" groupsList Skool groups as { value, label } options
openquok integrations:trigger "$SKOOL_ID" label -d '{"id":"<group-id>"}'List labels for a Skool group
openquok posts:create --jsonSchedule a Skool post with title and group
openquok posts:create --jsonSchedule with an optional label id
openquok posts:create --jsonSchedule a Skool post with a cover image
openquok posts:create --jsonSchedule a post and follow-up comments on skool.replies
Where you work
Worktrees, editor, and terminals
ThinkRail scopes files, diffs, terminals, and pi chats to the active git worktree — then invoke openquok-core like any other skill:
Linux
CLI or desktop on arm64 and x64
Windows
CLI or desktop build for Windows x64
Git worktrees
Each workspace is its own branch and cwd
Monaco editor
Tabs, files tree, and live diffs per worktree
Worktree terminals
PTYs scoped to the active workspace cwd
Optional MCP extensions
Pi MCP extensions
Optional MCP tools beside skills — OpenQuok stays CLI-first
Beyond Skool: Every Supported Platform for ThinkRail
Start with Skool, then schedule every other network from ThinkRail.
- Facebook Schedule Facebook from ThinkRail.
- Threads Schedule Threads from ThinkRail.
- Instagram Schedule Instagram from ThinkRail.
- YouTube Schedule YouTube from ThinkRail.
- TikTok Schedule TikTok from ThinkRail.
- LinkedIn Schedule LinkedIn from ThinkRail.
- X Schedule X from ThinkRail.
- Bluesky Schedule Bluesky from ThinkRail.
- Dev.to Schedule Dev.to from ThinkRail.
- Skool Preview Skool workflows for ThinkRail — coming soon.You're here
Autonomous agents & MCP
Beyond ThinkRail: Every Supported Agent
Open the landing page for another autonomous agent or MCP client. Compare setup steps, supported channels, and scheduling workflows beside ThinkRail.
Autonomous agents
OpenClaw
Preview Skool workflows for OpenClaw — coming soon.
Hermes Agent
Preview Skool workflows for Hermes Agent — coming soon.
Grok Bot
Preview Skool workflows for Grok Bot — coming soon.
Dots
Preview Skool workflows for Dots — coming soon.
Meta Muse
Preview Skool workflows for Meta Muse — coming soon.
You're here
ThinkRail
Preview Skool workflows for ThinkRail — coming soon.
Manus
Preview Skool workflows for Manus — coming soon.
MCP clients
Antigravity CLI
Preview Skool workflows for Antigravity CLI — coming soon.
ChatGPT
Preview Skool workflows for ChatGPT — coming soon.
Codex
Preview Skool workflows for Codex — coming soon.
Cursor
Preview Skool workflows for Cursor — coming soon.
Claude Code
Preview Skool workflows for Claude Code — coming soon.
Claude Cowork
Preview Skool workflows for Claude Cowork — coming soon.
VS Code / Copilot
Preview Skool workflows for VS Code / Copilot — coming soon.
Devin Desktop
Preview Skool workflows for Devin Desktop — coming soon.
Amp
Preview Skool workflows for Amp — coming soon.
Warp
Preview Skool workflows for Warp — coming soon.
Muse Code
Preview Skool workflows for Muse Code — coming soon.
Grok Build
Preview Skool workflows for Grok Build — coming soon.
Frequently asked questions
ThinkRail + Skool,answered
What ThinkRail is, how to install openquok-core, scheduling Skool posts, human approval, and Skool setup questions.
ThinkRail is a worktree IDE for the pi coding agent. You open a git repo as a project, cut workspaces as git worktrees, and work across Monaco tabs, terminals, diffs, and concurrent pi chat sessions — all scoped to the active worktree. See the ThinkRail integration and agent setup guides.
ThinkRail is a thin host: pi runs in-process and owns models, skills, compaction, and cost. ThinkRail owns the workspace, the editor, and the UI. Install openquok-core where pi discovers skills, then chat from ThinkRail. A standalone pi CLI session can use the same skill files — browse agent hosts and MCP clients for other paths.
Install @openquok/auto-cli in the worktree, add openquok-core to ~/.pi or .pi/skills/, and authenticate once. See the ThinkRail agent guide or the scheduling walkthrough.
The global CLI and auth files live on the machine that runs ThinkRail — the same environment as worktree terminals. Your OpenQuok workspace tokens never need to be pasted into chat; use OAuth device flow or a programmatic opo_ token on that computer. See OAuth2 for apps and Public API docs for token setup.
ThinkRail can draft and schedule Skool posts, upload images and video, and apply per-platform settings for your connected Skool account. The openquok-core skill documents integrations:list, posts:create, posts:status, upload, and more — every command returns structured JSON for the agent to parse. See ThinkRail + Skool and the Skool humanizer tool for channel-specific workflows.
Connect your Skool account via the Skool setup guide or the Skool channel landing. Install openquok-core on ThinkRail with the ThinkRail agent guide. Message your assistant to schedule — ThinkRail uses integration UUIDs from openquok integrations:list to target your Skool account. Every post lands as a draft or scheduled item until you approve on the calendar or kanban. Browse Skool playbooks and Skool building blocks for format ideas.
It depends on you. You can ask ThinkRail to publish now when the copy is ready, or save drafts and scheduled posts and approve them later on the OpenQuok calendar or kanban. Tell ThinkRail to use draft-only or not to publish when you want a review step first.
openquok-core runs in the worktree shell for repeatable scheduling. MCP fits ad hoc editor tools — see OpenQuok for Cursor or MCP setup. Many teams use both.
OpenQuok offers a 7-day free trial for scheduling on Pricing. ThinkRail is open source; you bring your own pi provider credentials. Install ThinkRail, add openquok-core, and begin scheduling from a worktree chat.
Yes. OpenQuok offers one 7-day free trial per payment customer so you can run social media accounts on auto-pilot before you subscribe the plan. Create an account and start today — no credit card required. Canceling and resubscribing, or creating another workspace, does not grant a second trial. Plan limits are on Pricing and in the billing limits guide; trial rules are in the Cloud trial guide.
Connect channels, write in Creating posts, then pick a time on the calendar or kanban. Agents can use the CLI, agent setup guides, or MCP setup guides.
A channel is one connected social account (Facebook, Instagram, LinkedIn, TikTok, YouTube, Threads, and more). Connect channels in the dashboard. Browse networks on Supported channels.
Sign up for free, install the OpenQuok browser extension, and sign in on skool.com in the same Chrome profile. Open a workspace and follow the connect channels guide → browser extension → Skool. OpenQuok validates your session and stores it encrypted on the server. For self-hosted deployments, see the self-host Skool setup guide.
Yes. Skool has no public OAuth flow for third-party schedulers. You connect while logged in on skool.com. The extension reads required session cookies only when you approve the connect flow in Add Channel. See browser extension install and the self-host Skool setup guide.
No. Invite links work only for OAuth redirect networks. Skool is excluded. Each member connects from the dashboard with the extension, or signs in to OpenQuok and adds Skool themselves. See connect channels guide.
Use the standard caption editor for the body. In Settings, set a title, pick a group, and optionally a label. Groups load from your connected account. See per-channel settings and the self-host Skool setup guide.
When the group allows it, add follow-up rows in the composer with delays and optional media. OpenQuok publishes the main post first, then each comment. See threads and follow-up comments.
Yes. Connect Skool in our web dashboard with the browser extension while signed in on skool.com, then follow MCP setup guides (ask your assistant in chat to list integrations and queue posts), CLI setup guides, the create-post API, or CLI examples. Pass title, group, and label in Skool provider settings when you schedule from the API or CLI.
Yes. Connect Skool in our web dashboard with the browser extension while signed in on skool.com, schedule community posts, and explore API access during the cloud free trial before upgrading to a paid plan that matches your channel and workspace limits. Plan details are on Pricing for a free tier, or self-host OpenQuok you run yourself.
Read the ThinkRail setup guide
Step-by-step self-host setup for connecting OpenQuok to ThinkRail — install commands, auth patterns, and configuration snippets.
Start free. Publish with confidence.
Connect your agent, review every draft, and schedule posts across channels before anything goes live.