If you run a content calendar, you have probably looked at Claude Cowork plugins and wondered whether they fit your work. Anthropic published an open source repository of knowledge worker plugins at anthropics/knowledge-work-plugins, and the overlap with content ops is real: briefs, docs, and workflow automation all show up in a posting calendar. This post covers how to sort those plugins by job, slot them into a calendar you already run, and recognize the point where planning stops and scheduling has to take over.
PLAN -> DRAFT -> SCHEDULE -> REPLY -> REPORT
plugins plugins Creator OS Creator OS Creator OS
(brief, doc, (doc, text) MCP / CLI / inbox tools analytics
workflow) REST API tools
| | | | |
+-- one repo ---+ +-- one workspace, all accounts What Anthropic’s Knowledge-Worker Plugins Actually Are
The repository is a set of plugins built for knowledge workers using Claude Cowork. Read that description literally: these are packages that give Claude a repeatable way to do a type of desk work. They ship as open source, so you can read what each one does before you install it, and you can adapt them.
What they are not: a publishing layer. A plugin can help Claude produce a content brief, restructure a doc, or chain a few steps together. It does not hold a connection to your Instagram, TikTok, YouTube, X, LinkedIn, Facebook or Threads accounts. That distinction matters more than any individual plugin, because it tells you where to draw the line in your own workflow.
Think of the repository as the front half of your content operation. The brief gets written, the doc gets shaped, the repetitive steps get automated. Then something has to actually put the post on the platform, answer the comment underneath it, and pull the numbers a week later.
Which Plugins Map to Social Planning, Reply Drafting and Reporting
Sort every plugin in the repo into three buckets before you install anything.
Social planning
Planning work is anything that happens before a caption exists. Campaign briefs, monthly themes, a repurposing plan for one long video into eight shorts, a launch checklist. Plugins in this bucket pair well with the planning you already do, and the output is usually a document you will read once and act on.
The test: does the plugin’s output change what you will post, rather than how it gets posted? If yes, it belongs in planning.
Reply drafting
Reply drafting plugins help Claude write responses in a consistent voice. The useful version of this is a plugin that carries your tone rules and your escalation rules, so a draft apology for a shipping delay sounds like you and a draft reply to a compliment does not sound like a press release.
What a plugin cannot do is see the comment. The comment lives on the platform. Drafting is half the loop. The other half is reading the inbox and sending the reply, and that is where a scheduling and engagement tool earns its place.
Reporting
Reporting plugins are good at turning a pile of notes into a readable weekly summary. They are weak at one thing: getting the numbers. If you paste metrics in, Claude can find the story. If you want the story without pasting, you need a tool that can pull per-post analytics and daily account metrics across all connected platforms on request.
Creator OS exposes that through a hosted MCP server at https://mcp.creatoros.ca/mcp, with tools including get_post_analytics, get_daily_metrics, get_follower_stats and get_best_time_to_post. A reporting plugin and an MCP connection are complementary, not competing. One shapes the narrative, the other supplies the figures.
Plugin by Plugin: Briefs, Docs and Workflow Automation in Content Ops
Rather than walk the whole repository, here is a worked example of how three plugin types fit into one week of content ops. Assume you post on Instagram, TikTok, YouTube and LinkedIn, and you have a long form video going out Thursday.
Monday: the brief
Open a session in Claude Cowork, install the plugin that produces briefs, and give it the raw material.
Read these three docs: last month's campaign retro,
the product roadmap excerpt, and Thursday's video transcript.
Produce a one page brief for the Thursday launch. Include
the hook, three talking points, the CTA, and the cut list
for the short form versions. Do not write captions yet.You get a brief you can argue with. That is the point. Editing a brief takes ten minutes. Editing eight captions takes an hour.
Tuesday and Wednesday: the docs and the drafts
Take the approved brief into a doc plugin and ask for the platform variants. Keep the ask narrow so you can review the output properly.
From the approved brief, write:
1. An Instagram Reel caption with a first comment for the link.
2. A LinkedIn post, no hashtags, one question at the end.
3. A YouTube title under 100 characters and a description.
Leave TikTok for now.If you want the same ask available as a repeatable command instead of retyping it, Creator OS ships 14 Claude Code skills installed with npx @creatoros/cli@latest init, including post-everywhere, post-shortform, post-longform, post-threads and schedule-posts. The walkthroughs for that flow are on the KevBuildsApps YouTube channel, and there is a written version in Claude Code for social media.
Thursday: the workflow automation
This is where automation plugins do their best work, and it is also where people overreach. Automate the handoff, not the judgment. A workflow that collects the approved drafts, validates them, and queues them for a human look is safe. A workflow that publishes without review will eventually publish something you would not have sent.
Slotting Plugins Into an Existing Posting Calendar
Do not build a new calendar around plugins. Put the plugin step next to the step it supports.
| Calendar stage | Who or what does it | Output |
|---|---|---|
| Brief | Planning plugin | One page brief |
| Draft | Doc plugin plus your edits | Per platform copy |
| Validate | creatoros validate:post-length |
Length and limit check |
| Schedule | Creator OS via MCP, CLI or API | Queued or draft post |
| Engage | Creator OS inbox tools | Replies and DMs sent |
| Report | Analytics tools plus a reporting plugin | Weekly summary |
One concrete step worth adding: run a length check before anything is queued. creatoros validate:post-length --text "..." returns a verdict per platform, so you catch a LinkedIn post that will get truncated or a Threads post over the limit before it reaches the calendar. Threads allows 500 characters per post, for example, and a caption that reads fine in a doc can silently break that rule.
Where Plugins Stop and Scheduling Starts
The boundary is simple: plugins operate on text you give them. Scheduling operates on accounts you have connected.
Creator OS is one place to publish, schedule, reply and read analytics across Instagram, TikTok, YouTube, X, LinkedIn, Facebook and Threads, plus Skool communities, a WordPress blog, and paid ads as an add-on. You can drive it from the web app, the iOS app, the REST API, the CLI at @creatoros/cli, or the hosted MCP server. An agent connected over MCP can call create_post, update_post, upload_media_from_url, list_posts, get_post, list_comments, reply_to_comment, send_message and get_best_time_to_post.
Setting up the connection takes a minute. In Claude, go to Settings, then Connectors, then Add custom connector, paste https://mcp.creatoros.ca/mcp, sign in to Creator OS, pick the workspace, and choose read only or read & write. Read-only connections only see read tools, and the API refuses writes from them. Destructive tools like deleting a post or disconnecting an account are marked so the AI app asks first. For Claude Code the command is:
claude mcp add --transport http creatoros https://mcp.creatoros.ca/mcp \
--header "Authorization: Bearer cos_live_..."The rest of the setup detail lives at the MCP docs. If you would rather work in the terminal, the CLI covers the same ground. A scheduled post looks like this:
creatoros posts:create \
--text "Thursday's build is live. Here is the one setting we changed." \
--platforms instagram,tiktok,youtube,linkedin \
--media https://your-cdn.example/reel.mp4 \
--scheduledAt 2026-03-12T14:00:00Z --timezone America/Toronto \
--title "The one setting we changed"Creator OS applies each platform’s rules for you: Reels and Shorts handling, TikTok’s required consent flags, and so on. You are not maintaining four sets of API quirks in your own scripts.
A Weekly Operating Rhythm With Plugins and Creator OS
Here is a rhythm you can copy. It uses plugins for the thinking and Creator OS for the accounts.
- Monday morning, brief. Run the planning plugin on last week’s analytics export and this week’s source material.
- Monday afternoon, drafts. Use a doc plugin for platform variants. Edit them like a human, because you are one.
- Tuesday, schedule. Load the approved drafts into the calendar with
creatoros posts:bulk-upload --file calendar.json --dryRunfirst, then without--dryRunonce the output looks right. - Daily, engage. Check
creatoros inbox:comments --limit 20, reply withcreatoros inbox:reply, and usecreatoros inbox:private-replyto send a DM from a comment where that funnel makes sense. - Friday, report. Pull
creatoros analytics:posts --sortBy engagementandcreatoros analytics:daily, hand the output to a reporting plugin, and publish the summary.
If you prefer to keep all of this inside one AI app, the MCP path is the cleanest. If you want a standing agent that runs the loop on its own, Social Agents is an open source harness that runs your socials on Creator OS. Start it with npm start creatoros social-agents; it interviews you about your brand, then posts, replies to comments and DMs, runs automations and reports, with a local dashboard. Bring your own model: a logged in Claude Code session, an ANTHROPIC_API_KEY, or any Anthropic compatible API. See the Social Agents repository and the launch video at youtu.be/-QBJH_PK3pY.
Common Setup Mistakes and How to Avoid Them
Treating a plugin as a publisher
Plugins do not have your account connections. If a session starts talking about “posting,” check what it is actually calling. If nothing is connected, it is drafting, not posting.
Connecting with write access on day one
Start read only. You will learn what the tools return and how your agent phrases things without any risk to a live account. Switch to read & write once you trust the loop.
Letting one key cover every workspace
REST API keys are pinned to one workspace, meaning one set of socials. An agent holding one workspace’s key cannot post to another. If you run several brands, issue several keys rather than sharing one widely.
Skipping the dry run
creatoros posts:bulk-upload --dryRun exists so a calendar file with a typo does not create fifty scheduled posts. Use it every time.
Forgetting that platforms have gaps
Not every action exists everywhere. TikTok comment replies are not supported through Creator OS, and LinkedIn does not accept every post format the platform offers through its API yet. Check the post options docs before you promise a client something the platforms do not allow.
Get started with Creator OS
Plugins in Claude Cowork make the planning half of content ops faster. Creator OS covers the half that touches the accounts: publishing, scheduling, replies, DMs and analytics across 11 platforms plus Skool and a WordPress blog. Every plan includes API keys, the hosted MCP server, the CLI and the agent skills. The Creator plan is $14.99/month or $59.99/year for one account on each of 11 platforms plus Skool.
Sign up at creatoros.ca/sign-up, connect one account, and run a single post through the loop end to end before you move the whole calendar. Start with the docs, and watch the walkthroughs on KevBuildsApps if you prefer to see it done first.
Get started for $0
Free trial for new subscribers. Cancel anytime.