Overview#
@webtaken/openclaw-myskool is a native OpenClaw plugin, listed on ClawHub. It calls the same Data API as everything else, with your API key, and adds two things the MCP server doesn't:
- A bundled skill that teaches the agent the Skool rules: hex group ids, mandatory post categories, plain-text content, and showing you the exact text before any post, comment, delete or DM.
- Opt-in per tool. The 6 read tools work right away; writes and DMs stay off until you allow them in OpenClaw.
- The retention skills: urgent radar, answer desk, pulse, churn signals and more, ready for
openclaw cronalerts on WhatsApp or Telegram.
Prefer MCP? OpenClaw also connects to the MCP server directly, with OAuth or a key: see OpenClaw on the MCP page. Use one or the other, not both.
Install#
Needs OpenClaw 2026.5.17 or newer. Restart the gateway once you've finished the next two steps.
openclaw plugins install clawhub:@webtaken/openclaw-myskool
openclaw plugins enable myskool
Add your API key#
Mint a key in API Keys. Tick the write and DM scopes only if you want those tools: scopes are fixed when the key is minted. Then give it to OpenClaw:
# ~/.openclaw/.env (chmod 600) — the gateway loads it on start
MYSKOOL_API_KEY=sk_live_xxxxxxxxxxxx
# or store it in the plugin config instead
openclaw config set plugins.entries.myskool.config.apiKey "sk_live_xxxxxxxxxxxx"
The .env file is the safer option: the key stays out of your config file. To pin a Skool account when you have several, set plugins.entries.myskool.config.connection to the connection id.
Allow the tools#
OpenClaw only shows plugin tools to the agent once the tool policy allows them. Recent releases add the read tools to the default profiles on their own; older ones (2026.6.x) don't, and writes and DMs are always opt-in. Allowing them explicitly works on every version:
# every MySkool tool (writes and DMs still confirm the text with you first)
openclaw config set tools.alsoAllow '["myskool"]' --strict-json
# or reads only
openclaw config set tools.alsoAllow '["myskool_list_groups","myskool_get_group","myskool_list_posts","myskool_list_comments"]' --strict-json
openclaw gateway restart
Restart, then start a new session
/new. If your config already has a tools.allow list, add the tool names there instead: allow and alsoAllowcan't be set in the same scope.Tools#
The same tools as the MCP server, prefixed with myskool_. A tool also needs the matching scope on your key.
| Tool | Scope | Default |
|---|---|---|
myskool_list_groups | groups:read | on |
myskool_get_group | groups:read | on |
myskool_whoami | groups:read | on |
myskool_list_posts | posts:read | on |
myskool_get_post | posts:read | on |
myskool_list_comments | comments:read | on |
myskool_create_post | posts:write | opt-in |
myskool_create_comment | comments:write | opt-in |
myskool_delete_post | posts:write | opt-in |
myskool_delete_comment | comments:write | opt-in |
myskool_list_dms | dms:read | opt-in |
myskool_get_dm | dms:read | opt-in |
myskool_send_dm | dms:write | opt-in |
Try it#
- “List my Skool groups.”
- “What's unread in my community? Summarize the top 5 posts.”
- “Show the comments on the newest post and draft replies for the unanswered ones.”
- “Who is waiting on a DM reply from me?”
Feed reads drive a headless browser on our side, a few seconds per page. Sent DMs can't be deleted, so the agent confirms the wording with you first.
Troubleshooting#
| Symptom | Fix |
|---|---|
| The agent says the myskool_* tools aren't available, or calls the API another way | The tool policy is filtering them. Run the allow command, restart the gateway and open a new session. |
| MySkool API key missing | Add MYSKOOL_API_KEY to ~/.openclaw/.env (or set plugins.entries.myskool.config.apiKey) and restart the gateway. |
unauthorized | The key is wrong, revoked or rotated. Mint a new one in API Keys. |
forbidden | The key lacks the scope for that tool. Write and DM scopes are chosen when the key is minted, so mint a new key with them ticked. |
payment_required | The plan is inactive. Activate it in Billing. |
rate_limited / quota_exceeded | Same limits as the API: 60 requests per minute per key, 30,000 per month. See Rate limits. |