OpenQuok Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
OPENQUOK Schedule YouTube from ThinkRail then you approve
Message ThinkRail from Telegram, WhatsApp, or Slack. Add the openquok-core skill so it schedules YouTube posts while you review on the calendar or kanban.
The Getting Started Guide The Getting Started Guide The Getting Started Guide
Get Started For Free Get Started For Free Get Started For Free
Install our core skill:
mkdir -p ~/.pi/agent/skills/openquok-core
curl -fsSL "https://raw.githubusercontent.com/Ratimon/openquok-monorepo/main/agent/skills/openquok-core/SKILL.md" \
-o ~/.pi/agent/skills/openquok-core/SKILL.mdDraft 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 drafts. You approve on the calendar before anything publishes.
Built for YouTube channels with ThinkRail
Who schedules YouTube with ThinkRail?
Creators & educators
Queue uploads, Shorts, and tutorials on a calendar. Set privacy and tags before publish. Message ThinkRail to draft YouTube posts from chat — you approve before publish.
Marketing teams
Batch demos, launch videos, and Shorts. Review drafts and thumbnails in one workflow. ThinkRail queues YouTube drafts at volume — your team approves before publish.
Agencies & developers
Manage client channels in separate workspaces. Schedule via dashboard, API, or MCP. Run ThinkRail per client workspace so YouTube drafts stay isolated.
Faceless channels
Batch voiceover and footage on a calendar. Pipe finished videos via API without YouTube Studio. Run ThinkRail per client workspace so YouTube 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 Back to global
Workspace tools. Sign in or sign up to use your library, Photo Editor, and signatures.
122 / 5,000
Post Preview
OpenQuok walkthrough — schedule MP4 uploads from one calendar
OpenQuok Channel
Jun 12, 9:00 AM
Product walkthrough — schedule this MP4 upload with title, privacy, tags, and an optional custom thumbnail before publish.
Post editor
Attach MP4 uploadswrite descriptionsqueue videos and Shorts
Attach a single MP4 — long-form or Short. Write the video description as your post body. Preview the upload. Schedule onto the calendar. Review drafts on the kanban board before anything goes live.
CLI command options
# Draft + human checklist (YouTube)
openquok posts:create --json ./examples/youtube-video-title-privacy.json
openquok posts:review-todo <post-id> --note "…"
openquok posts:status <post-id> --status draft
openquok posts:status <post-id> -s scheduleTargeted channels
Overview
Views
14.2%
9,827
Watch time (minutes)
11.4%
1,431
Avg view duration
4.8%
1,054
Avg view percentage
3.6%
341
Subscribers gained
9.2%
220
Likes
7.5%
739
Subscribers lost
2.1%
35
Insights
See what resonates on your channel track views and watch timeand iterate
Track views, watch time, average view duration, subscribers gained, and likes from connected YouTube channels inside OpenQuok analytics. Then schedule more of what already works.
CLI analytics options
# YouTube platform metrics
INTEGRATION_ID=$(openquok integrations:list | jq -r '.[] | select(.identifier=="youtube") | .id')
openquok analytics:platform "$INTEGRATION_ID" -d 30
# Per-post insights
openquok analytics:post <post-id> -d 7Draft 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
What performed best on my channels over the last 7 days? Break down impressions and engagement.
Pulled platform analytics (7d)
Top post: 12.4k impressions, 842 reactions — carousel on product tips.
Facebook Page leads with +24% impressions vs last week.
Compare that post on TikTok vs Instagram Reels.
TikTok: 48k views, 2.1k likes. IG Reel: 31k plays, 312 saves. TikTok wins reach; IG leads on saves.
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
Scale what works
when a format hits, scale by adding worktrees and parallel chats
Spot a winner in analytics, then cut another worktree for the next client or brand while a second pi session queues the next wave — credentials, channels, and agent context stay isolated as you scale.
Parallel CLI sessions
# Workspace A — launch (client brand)
openquok posts:create -c "…" -s "…" -t draft -i "<uuid>"
openquok posts:status <post-id> -s schedule
# Workspace B — another client (isolated credentials)
openquok posts:list --status draft
# Same workspace — metrics in parallel
openquok analytics:platform <integration-uuid> -d 7
openquok analytics:post <post-id> -d 30Playbooks & Building Blocks Directories
YouTube viral formats
Mix YouTube-focused skills, and MCP servers — then tailor them to your ThinkRail workflow.
comparisons
agent-native scheduling, not another dashboard
Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for YouTube 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
- Every post lands as draft or scheduled — you approve before anything goes live
CLI
Command reference
YouTube 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=="youtube") | .id'Discover your YouTube channel integration UUID
openquok integrations:settings "$YT_ID"Get YouTube upload rules and privacy options
openquok posts:create --json ./examples/youtube-video-title-privacy.jsonSchedule a video upload with title and privacy
openquok posts:create --json ./examples/youtube-with-thumbnail.jsonUpload with a custom thumbnail image
openquok analytics:platform "$YT_ID" -d 30Pull 30-day channel analytics
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:
macOS
CLI or desktop build on Apple Silicon
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 YouTube: Every Supported Platform for ThinkRail
Start with YouTube, 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.You're here
- TikTok Schedule TikTok from ThinkRail.
- LinkedIn Schedule LinkedIn from ThinkRail.
- X Schedule X from ThinkRail.
- Dev.to Schedule Dev.to from ThinkRail.
Frequently asked questions
ThinkRail + YouTube,answered
What ThinkRail is, how to install openquok-core, scheduling YouTube posts, human approval, and how agents draft from chat.
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 YouTube posts, upload images and video, apply per-platform settings, and pull platform and post analytics for your connected YouTube account. The openquok-core skill documents integrations:list, posts:create, posts:status, analytics:platform, upload, and more — every command returns structured JSON for the agent to parse. See ThinkRail + YouTube and the YouTube humanizer tool for channel-specific workflows.
Connect your YouTube account via the YouTube setup guide or the YouTube 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 YouTube account. Every post lands as a draft or scheduled item until you approve on the calendar or kanban. Browse YouTube playbooks and YouTube building blocks for format ideas.
Posts created through the CLI land in your OpenQuok workspace as drafts or scheduled items — nothing goes live on autopilot. You review on the calendar or kanban, move posts through draft and review, and approve what should publish. ThinkRail handles volume; you handle quality.
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.
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.