Skool All-in-One API

Full read AND write access to Skool communities. Use when user asks to manage Skool members (approve, reject, list pending), read or create posts, reply to c...

This skill runs an external Apify actor (cristiantala~skool-all-in-one-api) to manage Skool on your behalf. Consequences to consider before installing: - APIFY_TOKEN: This token lets the skill start actors under your Apify account. Use a dedicated, limited token and revoke it if you stop using the skill. - Skool credentials: The documented login flow sends your Skool email/password to the remote actor (or stores cookies returned by that actor). Only provide these if you trust the actor owner and Apify; prefer giving cookies you control or avoid supplying your password when possible. - Third‑party code: The actor runs on apify.com under someone else's account. Inspect the actor's source on Apify (if available) or contact the actor author to confirm behavior. Treat this like granting a remote service browser access to your Skool session. - Binaries mismatch: The skill declares node + mcpc but examples use curl. You may not need to install mcpc for the curl-based flows; verify what your chosen workflow actually requires. If you proceed, limit risk by creating a scoped APIFY token, avoid reusing your primary Skool password, and test with a non-critical Skool account or group first. If you need help verifying the actor code or alternative approaches that avoid sending passwords to a third party, ask for that review.

Type: OpenClaw Skill Name: skool-all-in-one-api Version: 1.0.0 The skill provides an interface to manage Skool communities via a third-party Apify actor (cristiantala~skool-all-in-one-api). It requires the AI agent to handle sensitive credentials, including the user's Skool email and password, and execute shell commands (curl, grep, export) to interact with the Apify API. While these capabilities are aligned with the stated purpose of community automation, the practice of passing raw credentials through shell environments and to an external actor represents a high-risk pattern without built-in sanitization or secure credential management.