Your posts are ready. The photos are cropped, the captions are approved, and the schedule is clear. Yet someone still has to log in, pick the right Page or board, set the time, repeat it across every account, and come back later to check if it actually went live.
I built @opvs-ai/blotato (v2.1.1 on the OPVS Marketplace) so you can hand that recurring delivery job to your agent. Watch the 60-second Blotato launch film or see the live listing on opvs.ai/skills/blotato.

Finished content still leaves a delivery job
When a post is written, the work is only half done. You still have to open each platform, pick the right destination, paste the text, attach the media, and set the publish time.
Today you have two ways to handle that work:
Do it yourself. You stop serving a customer or leave focused work to push posts out, or you carry the checklist into your evening.
Pay someone to do it. You hire an assistant and brief them on the content, the accounts, and the timing. The job still needs someone managing every send.
Either way, finished content leaves another recurring task competing for your attention.

Hand the publishing job to your agent
With @opvs-ai/blotato, I give my agent three things: the finished content, the connected accounts, and when the posts should go out. The skill handles the rest through one Blotato API key across ten platforms: X, LinkedIn, Facebook, Instagram, TikTok, Pinterest, Threads, Bluesky, YouTube, and Slack.
Here is what 2.1.1 does in practice:
Finds the right destination instead of guessing. Before publishing, the agent calls
listAccounts(with an optionalplatformfilter),listSubaccountsfor Facebook Pages, LinkedIn company Pages, YouTube playlists, and Slack channels, andlistPinterestBoardsfor Pinterest board IDs.Builds the exact shape each platform requires. One
createPostrequest handles single posts, threads, carousels, reels, and stories — including TikTok privacy and disclosure fields, YouTube title andisMadeForKids/containsSyntheticMediaflags, Instagram trial reels and collaborators, and SlackchannelId.Publishes now or schedules for later. You can pass an exact
scheduledTimeor setuseNextFreeSlotto drop the post into your next open Blotato queue slot.Checks every outcome instead of assuming. An accepted send is not yet proof that a post went live. The agent polls
getPostStatusand reports backpublished(with the livepublicUrl),scheduled,in-progress, orfailed(with the exacterrorMessage).

Stay with your customers, review only exceptions
I designed this around a simple boundary. Your agent owns the delivery checklist; you own the decisions and the exceptions.
When ten posts go out cleanly, you get a clean status report with live links. If one platform rejects a format or an account token expires, the agent surfaces that specific failure so you only step in when something actually needs your attention.

What Blotato does — and what it leaves to you
To keep expectations clear, @opvs-ai/blotato is a delivery skill, not a content studio:
What it owns: looking up connected accounts, Pages, and boards; publishing or scheduling single posts, threads, carousels, reels, and stories; and verifying the final status.
What you still supply: finished copy, media URLs, your connected social accounts, and your own Blotato API key in Settings → Integrations. It does not write posts, generate images, answer replies, or pull analytics.
Try it live
@opvs-ai/blotato 2.1.1 is live now on the OPVS Marketplace:
Watch the launch film and browse the listing at opvs.ai/skills/blotato.
Follow the setup guide to connect your Blotato key and run your first scheduled post.
Read the developer reference for all five methods and the v2.1.1 changelog for the full release notes.


