Posterly lets an AI agent manage social publishing through hosted MCP, from account discovery and post validation to confirmed scheduling and publishing.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install posterly
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install posterly using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is Posterly Social Publishing?
Posterly is an Openclaw Skills integration for managing social posts through Posterly's hosted MCP rather than a dashboard. It supports workflows across connected platforms such as Instagram, TikTok, LinkedIn, YouTube, X, Facebook, Threads, Pinterest, and Google Business Profile. Agents can discover accounts, draft and validate posts, find publishing slots, and manage publishing with the live MCP tool schemas as the source of truth.
The skill emphasizes safe publishing: the agent checks the workspace and accounts, validates the complete post payload, presents the exact action for review, and waits for explicit human approval before making changes. This makes Openclaw Skills useful for teams that want social publishing in an agent workflow without skipping consent or validation.
Posterly Social Publishing Use Cases
- List connected social accounts and platforms before planning a campaign.
- Draft and validate a caption, media selection, target account, and scheduled time before publishing.
- Schedule a post or publish immediately after the user reviews and approves the exact action.
- Find an available publishing slot or inspect existing posts and activity.
- Review performance with analytics tools when the user asks how content performed.
- Upload media through supported MCP upload tools, or create a media drop when a laptop file must be provided to hosted MCP.
How Posterly Social Publishing Works
- Check access with
whoamiat the start of the session to confirm the API key, workspace, and scopes. - Call
list_accountsto identify available social accounts. If the user specified a brand or client, resolve it with brand tools first. - Prepare the post details: caption, media, social account, and optional
scheduled_atvalue. - Submit the complete payload to
validate_postand resolve validation errors before proceeding. - Show the user the exact account, platform, caption, schedule or immediate-publish choice, media, and workspace. Wait for an explicit approval.
- After approval, call
create_postwith the approved payload andconfirm: true. Omittingscheduled_atpublishes immediately, so do not treat omission as implicit consent. - Report the result, share any dashboard link returned, and inspect failed posts before considering a retry.
Posterly Social Publishing Setup
- Confirm that the Posterly plan includes API access. The skill requires a
POSTERLY_API_KEYbeginning withpst_live_; consult Posterly's current signup and pricing pages for plan details. - Configure the key in the agent runtime environment. Claude Code plugins can provide
userConfig.api_key, which is injected asPOSTERLY_API_KEY. - Connect an MCP-capable client to Posterly's hosted endpoint. Use the MCP documentation for client-specific configuration; the endpoint is
https://www.poster.ly/api/mcp. A GET request to that endpoint returns unauthenticated server information. - If using optional local stdio instead of hosted MCP, set the API key in the environment and run:
export POSTERLY_API_KEY="pst_live_your_key"
npx -y [email protected]
- Prefer the MCP tools and their live schemas over invented REST or CLI calls. If MCP tools are unavailable, consult the MCP documentation. The documented CLI fallback is:
npx -y @posterly/[email protected]
Never share API keys, payment-card details, or social account passwords in chat. Do not request a key the user already has or start signup if whoami succeeds.
Posterly Social Publishing Data Schema & Taxonomy
The skill does not specify local content files or a generated-file format. It operates on Posterly account data and MCP tool payloads.
| Data or configuration | Purpose |
|---|---|
POSTERLY_API_KEY |
Authenticates API and MCP access; sent as a bearer token. |
| Workspace and scopes | Checked with whoami before working with publishing tools. |
| Brands and social accounts | Resolved with brand tools and list_accounts; posts target social account IDs. |
| Post payload | Includes the caption, media, target account, and optional scheduled_at; validate the complete payload before creation. |
| Confirmation | create_post requires the approved payload and confirm: true; writes must not occur before explicit user approval. |
| Media | Managed through available MCP upload tools. For a local laptop file, use create_media_drop and provide the resulting drop URL. |
| Results and activity | Posts and activity can be inspected with tools such as list_posts, get_post, get_post_missing, and list_activity. |
Tool availability can differ by client profile. Claude directory installs use POSTERLY_DIRECTORY_PROFILE=claude and the hosted endpoint https://www.poster.ly/api/mcp?profile=claude; that profile excludes AI image, video, and audio generation, billing mutations, and legacy tool aliases.
Posterly Social Publishing Advanced Features
- Uses hosted MCP as the primary integration and treats live tool schemas as authoritative.
- Supports batch creation through
create_posts_batch, subject to explicit approval for the exact write. - Provides account, brand, platform, post, media, scheduling-slot, and activity tools; analytics tools are available for performance questions.
- Applies a confirmation gate to publishing and other consequential actions, including deletions, comment or DM actions, disconnects, AI-credit spending, and billing or API-key changes.
- Requires failed posts to be inspected before retrying; do not reconnect, re-upload, or edit-and-retry until the user has completed that work.
- Supports a Claude directory profile with a restricted tool catalog; do not switch profiles or use CLI or REST fallbacks for operations excluded from that profile.
- Offers an optional local stdio server and a CLI fallback when hosted MCP is unavailable, while preferring MCP whenever the runtime supports it.
SKILL.md
Loading
Related Openclaw Skills
Glyph Fidelity
Glyph Fidelity audits transformed text and typography edge cases to help preserve readable, consistent letterforms.
Frihet ERP Operating Contract
A read-first operating contract for using the Frihet ERP MCP safely, with explicit controls for approvals, writes, and retries.
Shopify Admin Pro
Shopify Admin Pro enables guarded Shopify audits, reporting, and store administration through the Admin GraphQL API, with explicit approval required for every write.
Shopify Audit Pro
Shopify Audit Pro runs security-conscious, read-only Shopify audits and reports using the Admin GraphQL API.
Microtypography
A precise, non-rewriting typesetting pass that improves text for publication while explaining every change.
Line Length Optimizer
Check whether body text has a readable line length and get a concrete, responsive CSS width recommendation.
Featured*
