Using Claude Cowork to run social media like a conversation
Claude Cowork turns Author Automations Social into a chat interface — describe what you need, Claude does it. Zero clicks, zero screens. Here's what a real session looks like.
Claude Cowork is the non-coder's version of a Claude plugin. It lives inside the Claude desktop app (or Claude.ai in your browser). You don't open a terminal. You don't type slash-commands. You just chat.
When our plugin is installed, Claude Cowork can schedule posts, build campaigns, shorten links, generate images, and read your calendar — all from a conversation. Here's what using it actually looks like day-to-day.
The setup (two minutes, one-time)
- Download Claude Cowork (
claude.ai/downloador openclaude.aiin your browser) - In Cowork, go to Plugins
- Search for "Author Automations Social" or paste
@author-automations/social - Click Install
- When prompted, sign in with your Author Automations account
- Done. The plugin is active.
From then on, every conversation with Claude has access to your author account. Claude can see your books library, your connected platforms, your calendar, your brand voice guides.
What "running social media like a conversation" actually feels like
Here's a real transcript from the Monday morning of a launch week. I'll annotate what's happening under the hood.
Monday 9:00 AM — What's on deck this week?
Me: "Hey Claude, quick review: what do I have scheduled for Salt & Sky this week and what's still missing?"
Claude:
Let me check.
Scheduled this week for Salt & Sky (launching Sunday):
- Mon — Cover art carousel on Instagram, 2pm CT
- Tue — Quote teaser on Threads, 10am CT
- Thu — Pre-order reminder carousel, Instagram + Threads, 3pm CT
- Sun (launch day) — Launch announcement across all three platforms, 9am CT
Nothing scheduled for Wednesday, Friday, or Saturday. Given you're within a week of launch, that's probably too quiet.
Want me to draft a character reveal for Wednesday, a setting teaser for Friday, and a launch-eve "it's almost here" post for Saturday?
What happened: Claude queried the calendar via the plugin, formatted the schedule, noticed gaps, and proposed filling them. All without me clicking anything.
Monday 9:02 AM — Yes, fill the gaps
Me: "Yes. For the character reveal, lean into the lighthouse keeper specifically — make her grumpy. For the setting teaser, do coastal-Maine atmosphere. For Saturday, make it personal — something from me to readers."
Claude:
Got it. Let me draft all three.
[30 seconds of generation]
Wednesday — Character reveal (Instagram + Threads)
Rose doesn't do small talk. She doesn't do enthusiastic greetings. She doesn't do men in expensive jackets showing up on her doorstep with a survey and a clipboard.
Guess what she's going to do.
Pre-order: storylink.to/salt-sky
Friday — Setting teaser (Instagram + Threads)
[...]
Saturday — Launch-eve personal (Instagram + Threads)
[...]
Want me to schedule them at your usual slots, or should I wait for you to review?
What happened: Claude generated three captions using my brand voice guides, drafted platform-specific versions for each, and asked for permission before scheduling. It didn't assume.
Monday 9:04 AM — Review then schedule
Me: "Wednesday's is perfect. Friday's second sentence feels off, rewrite that. Saturday's is great. Schedule Wed and Sat; show me Friday again after the rewrite."
Claude:
Scheduling Wednesday and Saturday now.
[...confirmation...]
Friday rewrite:
[new version]
What happened: Partial scheduling — two posts went to the calendar, one stayed in draft for a re-review. Zero confusion because the conversation naturally tracks which is which.
Monday 9:06 AM — Make the QR code
Me: "Also I need a QR code for storylink.to/salt-sky to put on bookmarks for the conference this weekend. Can you grab me one?"
Claude:
Done. I've pulled the QR for storylink.to/salt-sky — downloading now to your Downloads folder as
salt-sky-qr.png, 1200x1200 PNG with transparent background, print-ready at 2-inch size.
What happened: Claude used the plugin's QR endpoint, downloaded the result to the user's local filesystem. Two seconds.
When Claude Cowork is better than the dashboard
Bulk review. "Show me all my posts scheduled next week and flag anything that feels weak." Dashboard makes you click through each; Cowork does it in one conversation.
Exploratory planning. "What if I did a TikTok-only campaign for book 3 instead of cross-platform? What would that look like?" Dashboard doesn't support hypothetical campaigns; Cowork can draft one as a thought experiment.
Mid-launch pivots. "My Instagram account is being weird tonight. Pause everything Instagram through tomorrow morning. Write me an apology post to run on Threads explaining." Dashboard-with-UI would take fifteen clicks; Cowork is two sentences.
Multi-pen-name orchestration. "Switch to my thriller pen name. What's the status of the Ghost Tide launch there?" Dashboard requires menu navigation; Cowork just switches contexts.
When the dashboard is better
Visual layout work. Carousels where you're designing slide positions. Calendar drag-and-drop scheduling. Seeing a month at a glance.
One-off tweaks. Fixing a typo in one post is usually faster by opening the post in the dashboard and editing.
Anything involving uploading a file. Cowork can pull from generated AI output, but for your own photos/video, uploading through the dashboard is still easier.
What Claude Cowork doesn't do
- Post on its own. Everything requires you to say "yes, schedule that" explicitly. Claude drafts and proposes; it doesn't publish.
- Run campaigns without you. If you don't respond to the conversation, Claude waits. It won't autonomously fill your calendar overnight.
- Make pricing decisions. Claude won't sign up for services, change your plan, or modify billing.
- Touch your book drafts. The plugin has no read or write access to your manuscript files. It only sees your social account data.
Safety defaults that matter
The plugin is designed to prefer asking over assuming. For every action that has a visible effect (scheduling, posting, regenerating, deleting), Claude will:
- State what it's about to do
- Wait for explicit confirmation
- Take the action only after you say yes
If you want a more trusting mode (let Claude schedule without asking on every post), you can tell Claude "go ahead and schedule automatically for this session — I'll review in the calendar after" and it will honor that until the session ends.
The integration with Claude Code
If you're a Claude Code user (the terminal version), the same
plugin works there via /plugin install aasocial. Same
capabilities, different interface. Some users prefer Claude Code
because it keeps social media in the same workspace as their
other coding/writing. Use whichever you prefer.
What to do next
- If you've never installed Claude Cowork, download it at claude.ai/download and install the plugin.
- For the dashboard-side of the same workflow, From automation to conversation is the foundations post.
- If you're running the plugin for the first time, start with "What's on my calendar this week?" — a simple read-only query that shows Claude can see your account.
