iOS
Message Muse from iPhone or iPad
We are finishing the Skool integration for Meta Muse. Check back soon for platform-specific workflows, examples, and setup guides.
bot
Queued on your OpenQuok calendar:
Post ref: oq-7f3a · review before publish
10:23 AMYour everyday agent
Ask Muse to list connected channels, draft platform-specific copy, and queue schedules through OpenQuok. You can publish now, schedule for later, or save drafts and approve on OpenQuok when you are ready.
Built for community builders with Meta Muse
Keep groups warm with a steady calendar. Approve every post before it hits the feed. Message Meta Muse to draft Skool posts from chat — publish now, schedule, or approve on OpenQuok.
Batch announcements and prompts for multiple groups. Reuse drafts from agents without manual copy-paste. Meta Muse queues Skool drafts at volume — your team can publish now or approve first.
Connect client Skool accounts from the dashboard with the extension. Pipe drafts via API or MCP after connect. Run Meta Muse per client workspace so Skool drafts stay isolated.
Facebook, Instagram, and Threads are first-class for Meta Muse. You can still schedule every other supported network from the same OpenQuok workspace.
Connect once
Use Muse secure credential storage for your OpenQuok API key. Choose a workspace, validate connected channels, and draft from mobile or web without opening another scheduling tab.
Public API authentication
# Programmatic token (Authorization header)
export OPENQUOK_API_KEY=opo_your_programmatic_token
# Custom connector: give Muse the OpenAPI URL
# https://www.openquok.com/api/v1/openapi.jsonbot
Sample channels
These chips set format and character limits. They are not your accounts.
Groups load from your Skool account after you connect the channel.
Group settings
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 (Secure VM)
# 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
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.jsonSample 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.
84 / 5,000
Follow-up comment publishes after your chosen delay.
comparisons
Most social scheduler SaaS keeps you in a browser tab. OpenQuok is built for Skool from Meta Muse
CLI
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 chat
Meta Muse meets you on the devices you already use. OpenQuok connects through custom connectors, the public API, CLI in the Secure VM, or hosted MCP when your environment supports it:
Message Muse from iPhone or iPad
Use Muse on Android phones and tablets
Chat in the browser at meta.ai
Reach Muse from WhatsApp when Meta enables it for your account
Muse runs tasks in an isolated environment with a terminal and filesystem
Store API keys in Muse credential prompts — not in ordinary chat
OpenQuok surfaces
Muse can wire OpenQuok from your public OpenAPI document
REST endpoints for accounts, drafts, schedules, and publishing
Shell commands inside the Secure VM when you install the skill
Use OpenQuok MCP when your Muse environment exposes MCP configuration
Start with Skool, then schedule every other network from Meta Muse.
Autonomous agents & MCP
Open another autonomous agent or MCP client landing page. Compare setup steps, Meta-first channels, and scheduling workflows beside Meta Muse.
Autonomous agents
Preview Skool workflows for OpenClaw — coming soon.
Preview Skool workflows for Hermes Agent — coming soon.
Preview Skool workflows for Grok Bot — coming soon.
Preview Skool workflows for Dots — coming soon.
Preview Skool workflows for Meta Muse — coming soon.
Preview Skool workflows for ThinkRail — coming soon.
Preview Skool workflows for Manus — coming soon.
MCP clients
Preview Skool workflows for Muse Code — coming soon.
Preview Skool workflows for Antigravity CLI — coming soon.
Preview Skool workflows for ChatGPT — coming soon.
Preview Skool workflows for Codex — coming soon.
Preview Skool workflows for Cursor — coming soon.
Preview Skool workflows for Claude Code — coming soon.
Preview Skool workflows for Claude Cowork — coming soon.
Preview Skool workflows for VS Code / Copilot — coming soon.
Preview Skool workflows for Devin Desktop — coming soon.
Preview Skool workflows for Amp — coming soon.
Preview Skool workflows for Warp — coming soon.
Preview Skool workflows for Grok Build — coming soon.
Frequently asked questions
What Meta Muse is, how to install openquok-core, scheduling Skool posts, human approval, and Skool setup questions.
Muse Secure VM is a dedicated cloud computer for one person's Muse. It holds connected app data and credentials in isolated storage. Muse asks before sensitive actions like email or purchases. OpenQuok fits the same pattern: schedule posts as drafts, then you approve on OpenQuok before anything goes live.
Yes. Muse can continue long tasks after you close the app and return when it needs input or when something changes. Pair that with OpenQuok so Muse queues social drafts while you focus elsewhere — publishing still waits for your calendar or kanban approval.
Not as a pre-reviewed directory connector on day one. Meta says you can ask Muse to create a custom connector when a service exposes an API. OpenQuok publishes a public OpenAPI document and REST API so Muse can wire scheduling without a separate adapter.
It depends on you. You can ask Muse 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 Muse to use draft-only or not to publish when you want a review step first.
Muse stores connector secrets in its secure credential store. When you use the CLI path, auth files live inside the Secure VM — not on your phone chat history. Rotate tokens from OpenQuok Developers → Access if you revoke access.
Step-by-step self-host setup for connecting OpenQuok to Meta Muse — install commands, auth patterns, and configuration snippets.
Connect your agent, review every draft, and schedule posts across channels before anything goes live.