Quick Start
Three commands to get your AI agent managing Skool communities:
# Install the CLI globally npm install -g stickyhive # Set your API key export STICKYHIVE_API_KEY=hm_live_your_api_key_here # List your connected communities stickyhive communities:list
Built for AI Agents
Every command is designed for programmatic use — structured output, predictable flags, and composable operations that AI agents can chain together.
Designed for Autonomous Agents
Structured JSON output, deterministic flags, and composable commands. AI agents can parse responses and chain operations without human intervention.
Community Management
List communities, get details, browse spaces. The starting point for any agent workflow — discover what's available before taking action.
DM Sequences
Build multi-step direct message campaigns with delays and enrollment tracking. Onboard new members, nurture leads, or re-engage inactive users.
Workflow Automation
Create trigger-condition-action automations. Welcome new members, respond to events, assign roles — all running on autopilot.
Scheduled Posting
Create posts with scheduling, polls, pinning, and auto-first-comments. Bulk-schedule across days with even spacing.
Platform-Specific Events
Set up webhooks for real-time notifications on post publishing, member joins, and other community events. Connect to any external system.
How It Works
Discover Communities
The agent runs stickyhive communities:list to discover your connected Skool groups and their spaces.
Create & Schedule
It creates posts, schedules content, and manages your publishing queue using posts:create and posts:bulk-schedule.
Automate Workflows
The agent builds automations with workflows:create and sets up DM sequences that run on autopilot.
Terminal Demo: Multi-Command Workflow
Here's what an AI agent session looks like — discovering communities, scheduling posts, and setting up automation in one flow:
# Step 1: Discover available communities and spaces $ stickyhive communities:list [ { "id": 42, "name": "Growth Hackers", "platform": "skool", "spaces": [...] } ] # Step 2: Check existing scheduled posts $ stickyhive posts:list --status pending --spaceId 5 [ { "id": 101, "title": "Monday Wins", "scheduledFor": "2026-06-02T09:00:00Z" } ] # Step 3: Schedule a new post for the gap on Wednesday $ stickyhive posts:create \ -t "What's your #1 tool for productivity?" \ -c "Drop your answer below..." \ -i 5 \ -s "2026-06-04T09:00:00Z" \ --poll '["Notion","Linear","Obsidian","Other"]' { "id": 102, "status": "scheduled", "scheduledFor": "2026-06-04T09:00:00Z" } # Step 4: Create a welcome workflow for new members $ stickyhive workflows:create -C 42 -n "Auto Welcome" \ --config '{"trigger":{"type":"member.joined"},"actions":[{"type":"send_dm","config":{"message":"Welcome to Growth Hackers! Check out our pinned posts to get started."}}]}' { "id": 7, "name": "Auto Welcome", "active": true } # Step 5: Set up onboarding DM sequence $ stickyhive sequences:create -C 42 -n "New Member Onboarding" \ --steps '[{"type":"dm","delay":"0d","message":"Welcome!"},{"type":"dm","delay":"3d","message":"How are you settling in?"},{"type":"dm","delay":"7d","message":"Here are our top resources..."}]' { "id": 15, "name": "New Member Onboarding", "steps": 3, "active": true }
What is OpenClaw?
OpenClaw is an AI agent runtime that automatically discovers tools via SKILL.md files. When you install the stickyhive CLI, OpenClaw detects it through the SKILL.md manifest — no manual configuration needed.
The SKILL.md file declares what the tool does, what environment variables it needs, and what binaries must be available. OpenClaw reads this, confirms requirements are met, and gives the agent full access to stickyhive commands.
--- name: stickyhive description: Manage communities, schedule posts, automate workflows, and run DM sequences across Skool metadata: openclaw: requirements: env: - STICKYHIVE_API_KEY binaries: - stickyhive ---
Once OpenClaw discovers the SKILL.md, the agent can immediately start running stickyhive commands — listing communities, scheduling posts, creating workflows — all autonomously.
Also Works with Claude Code
Claude Code executes terminal commands directly. Once stickyhive is installed and your API key is set as an environment variable, Claude Code can run any stickyhive command to manage your Skool community.
Just tell Claude Code: "Use stickyhive to schedule 5 engagement posts for next week in my Growth Hackers community" — and it will discover your spaces, create the posts, and schedule them with proper spacing.
# Claude Code discovers communities first $ stickyhive communities:list # Then creates and schedules posts based on your request $ stickyhive posts:create -t "Monday Motivation" -c "What got you excited this week?" -i 5 -s "2026-06-02T09:00:00Z" $ stickyhive posts:create -t "Tool Tuesday" -c "Share your favorite tool..." -i 5 -s "2026-06-03T09:00:00Z" $ stickyhive posts:create -t "Win Wednesday" -c "Drop your biggest win below!" -i 5 -s "2026-06-04T09:00:00Z" $ stickyhive posts:create -t "Thoughtful Thursday" -c "What's one lesson you learned?" -i 5 -s "2026-06-05T09:00:00Z" $ stickyhive posts:create -t "Friday Freeform" -c "Open discussion — anything goes!" -i 5 -s "2026-06-06T09:00:00Z"
Command Reference
Full list of stickyhive CLI commands available to AI agents:
| Category | Command | Description |
|---|---|---|
| Communities | communities:list |
List all connected communities |
communities:get <id> |
Get community details with spaces | |
| Spaces | spaces:list |
List all spaces across communities |
spaces:get <id> |
Get space details | |
| Posts | posts:create |
Create post with title, body, schedule, pin, poll, comment |
posts:list |
List posts filtered by status, draft, spaceId | |
posts:get <id> |
Get post details | |
posts:update <id> |
Update title, content, or settings | |
posts:delete <id> |
Delete a post | |
posts:reschedule <id> |
Move post to a new scheduled time | |
posts:publish <id> |
Publish immediately (bypass schedule) | |
posts:bulk-schedule |
Schedule multiple posts with interval spacing | |
| Workflows | workflows:list |
List all workflows for a community |
workflows:create |
Create trigger-action automation | |
workflows:toggle <id> |
Enable or disable a workflow | |
workflows:run <id> |
Manually trigger a workflow | |
workflows:registry |
Discover available triggers and actions | |
| Sequences | sequences:list |
List DM sequences for a community |
sequences:create |
Create multi-step DM sequence | |
sequences:enroll <id> |
Enroll a member in a sequence | |
sequences:toggle <id> |
Enable or disable a sequence | |
| Webhooks | webhooks:create |
Create webhook for community events |
# Communities stickyhive communities:list stickyhive communities:get <id> # Spaces stickyhive spaces:list stickyhive spaces:get <id> # Posts stickyhive posts:create -t "Title" -c "Body" -i <spaceId> [-s "2026-06-01T09:00:00Z"] [--pin] [--comment "First!"] [--poll '["A","B"]'] stickyhive posts:list [--status pending|published|failed] [--draft] [--spaceId 42] stickyhive posts:get <id> stickyhive posts:update <id> -d '{"title":"New","content":"Body"}' stickyhive posts:delete <id> stickyhive posts:reschedule <id> -s "2026-07-01T09:00:00Z" stickyhive posts:publish <id> stickyhive posts:bulk-schedule --ids "1,2,3" --startTime "2026-06-01T09:00:00Z" --interval 2 # Workflows stickyhive workflows:list -C <communityId> stickyhive workflows:create -C <communityId> -n "Welcome" --config '{"trigger":{"type":"member.joined"},"actions":[{"type":"send_dm","config":{"message":"Welcome!"}}]}' stickyhive workflows:toggle <id> -C <communityId> stickyhive workflows:run <id> -C <communityId> stickyhive workflows:registry [--platform skool] # DM Sequences stickyhive sequences:list -C <communityId> stickyhive sequences:create -C <communityId> -n "Onboarding" [--steps '<JSON>'] stickyhive sequences:enroll <sequenceId> -C <communityId> -m <memberId> stickyhive sequences:toggle <id> -C <communityId> # Webhooks stickyhive webhooks:create -u "https://example.com/hook" -e "post.published,member.joined"
Works with Skool
Skool has no official API or CLI support. StickyHive bridges the gap — connect your Skool community via our Chrome extension, then manage it entirely from the terminal. The CLI gives AI agents the same access you have through the Skool web interface: post creation, scheduling, community browsing, and more.
Give Your AI Agent Access to Skool
Install the CLI and let Claude Code, OpenClaw, or Codex manage your community autonomously.
✓ npm install -g stickyhive
✓ Works with Claude Code, OpenClaw, Codex
✓ Posts, workflows, DM sequences, webhooks
✓ Structured JSON output for agent parsing
✓ SKILL.md auto-discovery for OpenClaw
✓ 14-day free trial
No credit card • Works with any Skool community • CLI access included on all plans
Related Agent Integrations
Connect Claude to Skool
MCP setup for Claude Desktop & Claude Code
Codex + Skool
Use OpenAI Codex to manage Skool communities
Hermes Agent + Skool
Hermes-powered community automation
Perplexity Computer + Skool
Research-powered community management
NanoClaw + Skool
Lightweight agent for quick Skool tasks
Paperclip + Skool
Persistent agent for ongoing community ops
Frequently Asked Questions
What is the stickyhive CLI?
The stickyhive CLI is an npm package (npm install -g stickyhive) that provides command-line access to StickyHive's community management platform. It's designed specifically for AI agents that can execute shell commands — like Claude Code, OpenClaw, and Codex — giving them full control over Skool communities from the terminal.
How do AI agents use the CLI?
AI agents like Claude Code and Codex can execute terminal commands directly. Once stickyhive is installed and the API key is set as an environment variable (STICKYHIVE_API_KEY), the agent can run any stickyhive command. The CLI outputs structured JSON that agents parse to understand results and chain follow-up operations.
What is OpenClaw and how does it discover stickyhive?
OpenClaw is an AI agent runtime that discovers tools via SKILL.md manifest files. When stickyhive is installed, OpenClaw reads its SKILL.md file, checks that the required environment variable (STICKYHIVE_API_KEY) and binary (stickyhive) are available, then gives the agent access to all CLI commands without manual configuration.
Does this work with Claude Code?
Yes. Claude Code can execute terminal commands directly. Once stickyhive is installed globally and your API key is set, you can tell Claude Code to manage your Skool community and it will run the appropriate stickyhive commands — listing spaces, creating posts, scheduling content, and building workflows.
How is this different from the MCP server?
The MCP server connects to AI tools that support the Model Context Protocol (Claude Desktop, Cursor IDE). The CLI is for AI agents that execute shell commands (Claude Code, OpenClaw, Codex). Same underlying capabilities — posts, workflows, sequences — but different interfaces. Use MCP for conversational AI tools, CLI for agentic coding environments.
Can the CLI schedule posts on Skool?
Yes. Use stickyhive posts:create with the -s flag to set a schedule time. You can also use posts:bulk-schedule to schedule multiple posts at regular intervals, posts:reschedule to move posts, and posts:publish to publish immediately.
What platforms are supported?
StickyHive supports Skool, Circle, Mighty Networks, Discord, and Slack. The CLI works across all connected platforms using the same commands. Connect your communities through the StickyHive web dashboard, then manage them all from one CLI tool.
Is my API key secure?
Yes. Your API key is stored as an environment variable (STICKYHIVE_API_KEY) and never written to disk by the CLI. All communication with StickyHive's API uses HTTPS encryption. You can rotate keys at any time from Settings → Developer in the dashboard.