OpenQuok Core
Schedule and manage social posts with the openquok CLI — authenticate, upload media, create drafts and scheduled post…
OpenQuok Schedule Dev.to from Manus then you approve
Message Manus from Telegram, WhatsApp, or Slack. Add the openquok-core skill so it schedules Dev.to posts while you review on the calendar or kanban.
The Getting Started Guide The Getting Started Guide The Getting Started Guide
Try for free for 7 days Try for free for 7 days Try for free for 7 days
Install our core skill:
https://github.com/Ratimon/openquok-monorepo/tree/main/agent/skills/openquok-coreDraft 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 Manus project
Chat in Manus,keep skills portable
Ask Manus to draft and schedule like any other task. The openquok-core skill runs openquok in your Cloud Computer or local 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 technical writers with Manus
Who schedules Dev.to with Manus?
Engineers & indie hackers
Ship changelogs and tutorials from the calendar, not the Dev.to editor. Message Manus to draft Dev.to posts from chat — publish now, schedule, or approve on OpenQuok.
Developer relations
Batch docs and release notes with tags, series, and covers. Review on kanban before publish. Manus queues Dev.to drafts at volume — your team can publish now or approve first.
Agencies & technical blogs
Connect client accounts with an API key. Pipe markdown drafts via API or MCP. Run Manus per client workspace so Dev.to drafts stay isolated.
Connect once
authenticate on the Cloud Computerpick your workspacechat from Manus securely
Choose an OpenQuok workspace, connect with OAuth2 — approve in your browser, and credentials stay on the machine that runs openquok. Ask Manus 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.
111 / 100,000
Post Preview
OpenQuok on Dev.to
Jun 16, 9:00 AM
Ship technical posts with tags and series you approve
Series · Shipping notes
Queue this markdown article with title, tags, cover, series, and an optional canonical URL before it goes live.
#webdev#productivity
Post editor
Write markdown articles in Dev.toreview drafts on the kanban boardbefore you approve
Write the body as markdown in the usual editor. Preview formatting. Schedule onto the calendar. Review agent and human drafts on the kanban board before anything goes live on DEV Community.
CLI command options
# Draft + human checklist (Dev.to)
openquok posts:create --json ./examples/devto-article-title-tags.json
openquok posts:review-todo <post-id> --note "…"
openquok posts:status <post-id> --status draft
openquok posts:status <post-id> -s scheduleTargeted channels
Overview
Trends
Compare channels using each network's closest matching metric. Totals add primary series per channel — not a single blended platform metric.
Views
3,771
1 channel
Engagement
138
1 channel
Followers
—
09/25 10/01
- OpenQuok on Dev.to (Page Views)
Page Views
Dev.to OpenQuok on Dev.to
12.6%
3,771
Reactions
Dev.to OpenQuok on Dev.to
8.4%
534
Comments
Dev.to OpenQuok on Dev.to
5.7%
138
Dev.to insights
See what resonates on Dev.to track views and reactionsand iterate
Dev.to analytics—Trends summary totals and per-account page views, reactions, and comments (7, 30, or 90 days). Then schedule more of what already works.
CLI analytics options
# Dev.to platform metrics
INTEGRATION_ID=$(openquok integrations:list | jq -r '.[] | select(.identifier=="devto") | .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 with parallel Manus sessions
Spot a winner in analytics, then spin another project or Automation while a second chat queues the next wave — credentials and channels stay scoped per workspace 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
Dev.to viral formats
Mix Dev.to-focused skills, and MCP servers — then tailor them to your Manus workflow.
comparisons
agent-native scheduling, not another dashboard
Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for Dev.to from Manus
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-off prompts that forget how you schedule each channel
- Autopilot publishing with no human checkpoint
OpenQuok + Manus
- Ask Manus to draft and schedule from the same project chat
- Credentials stay on the Cloud Computer or shell that runs openquok
- Skills load on demand — import once, invoke with / when you need scheduling
- CLI-first openquok-core works beside any other Manus skill or connector
- SKILL.md keeps channel rules and CLI examples in a portable package
- You choose publish-now, schedule, or draft — approve on OpenQuok when you want a review step
CLI
Command reference
Dev.to 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=="devto") | .id'Discover your Dev.to integration UUID
openquok integrations:settings "$DEVTO_ID"Get Dev.to posting rules, title/tag schema, and allow-listed tools
openquok posts:create --json ./examples/devto-article-title-tags.jsonSchedule a markdown article with title and tags
openquok posts:create --json ./examples/devto-series.jsonSchedule an article in a Dev.to series
openquok posts:create --json ./examples/devto-canonical.jsonSyndicate an article with a canonical URL
openquok posts:create --json ./examples/devto-organization.jsonPublish to an organization with cover image settings
openquok integrations:trigger "$DEVTO_ID" tagsList Dev.to tags for autocomplete
openquok integrations:trigger "$DEVTO_ID" organizationsList organizations you can publish as
openquok analytics:platform "$DEVTO_ID" -d 30Pull 30-day Dev.to analytics (page views, reactions, comments)
openquok analytics:post "$POST_ID" -d 7Pull 7-day insights for a published Dev.to article
Where you work
Studio, web, mobile, and Skills
Manus runs across Studio, browser, and mobile apps — import skills once, then invoke openquok-core with / in chat or from Automations:
Manus Studio
Desktop workspace for documents, code, and long-running projects
Web app
Run tasks from manus.im in the browser
Mobile
Continue projects from iOS or Android apps
Skills
Import or upload openquok-core, then invoke it with / in chat
Cloud Computer
Dedicated environment with browser, filesystem, and terminal
Automations
Event-triggered workflows beside scheduled tasks
Connectors (optional)
Connectors
Optional integrations when your project needs external services
Beyond Dev.to: Every Supported Platform for Manus
Start with Dev.to, then schedule every other network from Manus.
- Facebook Schedule Facebook from Manus.
- Threads Schedule Threads from Manus.
- Instagram Schedule Instagram from Manus.
- YouTube Schedule YouTube from Manus.
- TikTok Schedule TikTok from Manus.
- LinkedIn Schedule LinkedIn from Manus.
- X Schedule X from Manus.
- Bluesky Schedule Bluesky from Manus.
- Dev.to Schedule Dev.to from Manus.You're here
Autonomous agents & MCP
Beyond Manus: Every Supported Agent
Open the landing page for another autonomous agent or MCP client. Compare setup steps, supported channels, and scheduling workflows beside Manus.
Autonomous agents
OpenClaw
Schedule Dev.to from OpenClaw with openquok-core skills and CLI examples.
Hermes Agent
Schedule Dev.to from Hermes Agent with openquok-core skills and CLI examples.
Grok Bot
Schedule Dev.to from Grok Bot with openquok-core skills and CLI examples.
Dots
Schedule Dev.to from Dots with openquok-core skills and CLI examples.
Meta Muse
Schedule Dev.to from Meta Muse with openquok-core skills and CLI examples.
ThinkRail
Schedule Dev.to from ThinkRail with openquok-core skills and CLI examples.
You're here
Manus
Schedule Dev.to from Manus with openquok-core skills and CLI examples.
MCP clients
Antigravity CLI
Draft and schedule Dev.to with MCP tools from Antigravity CLI.
ChatGPT
Draft and schedule Dev.to with MCP tools from ChatGPT.
Codex
Draft and schedule Dev.to with MCP tools from Codex.
Cursor
Draft and schedule Dev.to with MCP tools from Cursor.
Claude Code
Draft and schedule Dev.to with MCP tools from Claude Code.
Claude Cowork
Draft and schedule Dev.to with MCP tools from Claude Cowork.
VS Code / Copilot
Draft and schedule Dev.to with MCP tools from VS Code / Copilot.
Devin Desktop
Draft and schedule Dev.to with MCP tools from Devin Desktop.
Amp
Draft and schedule Dev.to with MCP tools from Amp.
Warp
Draft and schedule Dev.to with MCP tools from Warp.
Muse Code
Draft and schedule Dev.to with MCP tools from Muse Code.
Frequently asked questions
Manus + Dev.to,answered
What Manus is, how to install openquok-core, scheduling Dev.to posts, human approval, and Dev.to setup questions.
Manus is an agent platform for turning ideas into deliverables. Manus 2.0 adds Manus Studio, Cascade, optional Cloud Computers, and event-driven Automations — not just chat. See the Manus integration, Manus agent guide, and Manus 2.0 overview at https://manus.im/blog/introducing-manus-2-0.
Manus Studio is the shared desktop workspace for documents, code, sites, and creation tools. Video Editor gives you a timeline for short ads, tutorials, and motion-led video — including Alchemy mode for higher-quality first cuts. Game Dev helps you build, edit, and publish playable games, with Cloud Computers for always-on multiplayer. OpenQuok does not replace those tools — openquok-core schedules social posts after your Studio work is ready.
Manus is the full project platform with Studio, Video Editor, Game Dev, Skills, and Cloud Computers. Cue is a separate early-access app for personal agents with their own email, phone, and computer on phone and desktop. OpenQuok ships openquok-core for Manus Skills today — not a dedicated Cue integration. If you use Cue, schedule through Manus Studio or ask your operator when Cue gains the same Skill path.
OpenQuok connects to Manus through the openquok-core Skill, Studio chat, and the CLI on a Cloud Computer. Cue is a different app from the same vendor family. For social scheduling with human approval, set up Manus on manus.im — see the Manus agent guide.
Automations start Manus work when something happens in a connected service — not only on a clock. Tell Manus what to watch and what to do; include openquok-core when the workflow should draft or schedule social posts. Posts land in your OpenQuok workspace — You can publish now, schedule for later, or save drafts and approve on OpenQuok when you are ready.
Open Skills → + Add → Import from GitHub or Upload a skill. Import the public openquok-core folder, or download SKILL.md and upload it. See the Manus agent guide.
The global CLI and auth files live on the Cloud Computer or local shell where Manus runs openquok — not in ordinary chat. Use OAuth device flow or a programmatic opo_ token on that machine. See OAuth2 for apps and Public API docs for token setup.
Draft and schedule posts, upload media, configure plugs, and pull analytics across your connected channels. See supported channels and CLI post commands; openquok-core returns structured JSON for the agent.
Connect your Dev.to account via the Dev.to setup guide or the Dev.to channel landing. Install openquok-core on Manus with the Manus agent guide. Message your assistant to schedule — Manus uses integration UUIDs from openquok integrations:list to target your Dev.to account. Every post lands as a draft or scheduled item until you approve on the calendar or kanban. Browse Dev.to playbooks and Dev.to building blocks for format ideas.
It depends on you. You can ask Manus 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 Manus to use draft-only or not to publish when you want a review step first.
openquok-core is CLI-first for repeatable Manus Skills on a Cloud Computer. 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. Manus plan limits are on the Manus site. Import openquok-core, authenticate once, and begin scheduling from 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.
Sign up for free, open a workspace, and choose Add Channel → Dev.to. Paste an API key from DEV Settings → Extensions. OpenQuok keeps the key on the server so it can publish for you; list and connect APIs never return it. Treat the key like a password — if it leaks, rotate it in DEV Settings and reconnect. See the connect channels guide. For self-hosted deployments, see the self-host Dev.to setup guide.
Yes. Use our post editor — the body is sent as markdown. Title, tags, cover, organization, series, and canonical URL live in Dev.to settings, not in a separate markdown editor. See editor by platform and Dev.to API settings.
Dev.to allows at most four tags. OpenQuok loads tag suggestions from the connected account when available, or you can type names freely. Title must be at least two characters before you can schedule. See Dev.to API settings and Dev.to CLI examples.
Yes. Attach an optional cover (recommended 1000×420) from the media library, and pick an organization if your account publishes for one. Personal profile is the default when no organization is selected. Design covers in the Dev.to photo editor.
Yes. Enter a free-text series name in Dev.to settings (or pass series in providerSettings). Dev.to creates the series if it does not already exist. See Dev.to API settings.
Yes. Set Canonical URL in Dev.to settings (or pass canonical in providerSettings). OpenQuok sends that URL with the article so Dev.to can point at the original. See Dev.to API settings and Dev.to CLI examples.
Yes. Connect Dev.to in our web dashboard with an API key, then follow MCP setup guides (ask your assistant in chat to list integrations and queue posts), CLI setup guides, the create-post API, or Dev.to CLI examples. Pass title, tags, series, cover, and canonical URL in provider settings.
Yes. Workspace analytics show account-level page views, reactions, and comments over 7, 30, or 90 days, plus per-article insights for published posts. Follow-up comments on Dev.to articles are not supported today. Pull metrics from the analytics CLI.
Yes. Connect Dev.to in our web dashboard with an API key, schedule articles, 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.
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.
Read the Manus setup guide
Step-by-step self-host setup for connecting OpenQuok to Manus — 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.