OpenQuok Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
Message ThinkRail from Telegram, WhatsApp, or Slack. Add the openquok-core skill so it schedules X 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 X with ThinkRail
Stay visible on X without living in the app. Ask your agent to schedule tweets and threads while you ship product. Message ThinkRail to draft X posts from chat — you approve before publish.
Batch a week of X posts. Control reply settings per tweet. Track engagement with your other channels. ThinkRail queues X drafts at volume — your team approves before publish.
Pipe X drafts from your backend via the public API, CLI, or MCP. Configure thread replies and reply settings per post. Run ThinkRail per client workspace so X 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.
75 / 280
Ship the company launch post — a personal profile can repost after publish.
Thread reply publishes after your chosen delay
Post editor
A strong tweet deserves a conversation. You do not need another tab open on X. Add follow-up replies in the composer with delays. Preview text and media before you schedule. Chain the full thread from one draft.
CLI command options
# Draft + human checklist (X)
openquok posts:create --json ./examples/x-text-only.json
openquok posts:review-todo <post-id> --note "…"
openquok posts:status <post-id> --status draft
openquok posts:status <post-id> -s scheduleInsights
Track likes, replies, reposts, quotes, and impressions from connected X profiles inside OpenQuok analytics. Then schedule more of what already works.
CLI analytics options
# X platform metrics
INTEGRATION_ID=$(openquok integrations:list | jq -r '.[] | select(.identifier=="x") | .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 X-focused skills, and MCP servers — then tailor them to your ThinkRail workflow.
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
Browse every X building block.
comparisons
Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for X from ThinkRail
CLI
X 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=="x") | .id' Discover your X integration UUID
openquok integrations:settings "$X_ID" Get X posting rules and character limits
openquok posts:create --json Schedule a text-only post on X
openquok posts:create --json Schedule a post and quote-less reply chain
openquok posts:create --json {
"scheduledAt": "2026-01-01T12:00:00.000Z",
"status": "scheduled",
"body": "1/2 — setup",
"integrationIds": ["<integration-id>"],
"providerSettingsByIntegrationId": {
"<integration-id>": {
"x": {
"replies": [
{
"id": "reply-1",
"message": "2/2 — payoff",
"delaySeconds": 90,
"media": [{ "id": "<reply-media-id>", "path": "https://cdn.example.com/payoff.jpg" }]
}
]
}
}
}
} Schedule a follow-up reply with images on x.replies
openquok posts:create --json {
"scheduledAt": "2026-01-01T12:00:00.000Z",
"status": "scheduled",
"body": "Main tweet from channel A",
"integrationIds": ["<integration-id-1>"],
"providerSettingsByIntegrationId": {
"<integration-id-1>": {
"x": {
"crossAccountPlugs": [
{
"plugName": "x-repost-post-users",
"enabled": true,
"delayMs": 0,
"integrationIds": ["<integration-id-2>"],
"fields": {}
}
]
}
}
}
} Repost from another X channel after publish (crossAccountPlugs)
openquok plugs:catalog | jq '.plugs[] | select(.identifier=="x")' List global plug types and field names for this provider
openquok plugs:list "$ID" List saved global plug rules on this channel
openquok plugs:upsert "$ID" --func autoRepostPost --fields '[{"name":"likesAmount","value":"100"}]' Auto-repost when a post reaches a likes threshold (global plug)
openquok plugs:upsert "$ID" --func autoPlugPost --fields '[{"name":"likesAmount","value":"100"},{"name":"post","value":"Thanks for the support!"}]' Auto-reply when a post reaches a likes threshold (global plug)
openquok analytics:platform "$X_ID" -d 30 Pull 30-day X 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 X, then schedule every other network from ThinkRail.
Frequently asked questions
What ThinkRail is, how to install openquok-core, scheduling X 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.