Bloom MCP
Onboard your brand once, then generate and edit on-brand images from any MCP client — website or Instagram URL in, ca…
Message ThinkRail from Telegram, WhatsApp, or Slack. Add the openquok-core skill so it schedules Instagram posts while you review on the calendar or kanban.
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.mdOn it — openquok-core
Created drafts with cover image attached.
✓ Queued for Tue 9:00 AM · ref oq-7f3a
Your worktree IDE
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 Instagram Business & Standalone with ThinkRail
Queue feed posts, Reels, and Stories from one calendar. Connect via Business or Standalone login. Message ThinkRail to draft Instagram posts from chat — you approve before publish.
Batch carousels and launch Reels ahead of time. Set post type and collaborators before publish. ThinkRail queues Instagram drafts at volume — your team approves before publish.
Pipe Instagram drafts via dashboard, API, or MCP. Separate client accounts per workspace. Run ThinkRail per client workspace so Instagram drafts stay isolated.
Connect once
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:statusbot
Sample channels
These chips set format and character limits. They are not your accounts.
Workspace tools. Sign in or sign up to use your library, Photo Editor, and signatures.
112 / 2,200

OpenQuok Studio Queue a carousel or single MP4 Reel — tune post type, collaborators, and text follow-up comments before publish.
Link in bio for the full drop — text-only follow-ups publish after your delay.
Post editor
Switch between feed, Reel, and Story in the composer. Attach photos, carousels, or MP4 Reels. Queue text-only follow-up comments with delays. Use the dashboard or provider Settings in the API.
CLI command options
# Draft + human checklist (Instagram)
openquok posts:create --json ./examples/instagram-feed-post.json
openquok posts:review-todo <post-id> --note "…"
openquok posts:status <post-id> --status draft
openquok posts:status <post-id> -s scheduleInsights
Track reach, views, likes, saves, and comments from connected Instagram accounts inside OpenQuok analytics. Then schedule more of what already works.
CLI analytics options
# Instagram platform metrics
INTEGRATION_ID=$(openquok integrations:list | jq -r '.[] | select(.identifier=="instagram-business" or .identifier=="instagram-standalone" or .identifier=="instagram") | .id')
openquok analytics:platform "$INTEGRATION_ID" -d 30
# Per-post insights
openquok analytics:post <post-id> -d 7On it — openquok-core
Created drafts with cover image attached.
✓ Queued for Tue 9:00 AM · ref oq-7f3a
Pulled platform analytics (7d)
Top post: 12.4k impressions, 842 reactions — carousel on product tips.
Facebook Page leads with +24% impressions vs last week.
On it — openquok-core
Created drafts with cover image attached.
✓ Queued for Tue 9:00 AM · ref oq-7f3a
Scale what works
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
Mix Instagram-focused skills, and MCP servers — then tailor them to your ThinkRail workflow.
Onboard your brand once, then generate and edit on-brand images from any MCP client — website or Instagram URL in, ca…
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
Browse every Instagram building block.
comparisons
Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for Instagram from ThinkRail
CLI
Instagram 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=="instagram-business" or .identifier=="instagram-standalone" or .identifier=="instagram") | .id' Discover your Instagram integration UUID
openquok integrations:settings "$IG_ID" Get Instagram posting rules and post_type options
openquok posts:create --json ./examples/instagram-feed-post.json Schedule an Instagram feed image post
openquok posts:create --json ./examples/instagram-carousel.json Publish a multi-image carousel
openquok posts:create --json ./examples/instagram-reel.json Schedule an Instagram Reel from MP4
openquok analytics:platform "$IG_ID" -d 30 Pull 30-day Instagram analytics
Where you work
ThinkRail scopes files, diffs, terminals, and pi chats to the active git worktree — then invoke openquok-core like any other skill:
CLI or desktop build on Apple Silicon
CLI or desktop on arm64 and x64
CLI or desktop build for Windows x64
Each workspace is its own branch and cwd
Tabs, files tree, and live diffs per worktree
PTYs scoped to the active workspace cwd
Optional MCP extensions
Optional MCP tools beside skills — OpenQuok stays CLI-first
Start with Instagram, then schedule every other network from ThinkRail.
Frequently asked questions
What ThinkRail is, how to install openquok-core, scheduling Instagram posts, human approval, and how agents draft from chat.
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.
Step-by-step self-host setup for connecting OpenQuok to ThinkRail — install commands, auth patterns, and configuration snippets.
Connect your agent, review every draft, and schedule posts across channels before anything goes live.