Claude Cowork social media automation
Run Claude Cowork as your desktop control layer. Genviral is the skill it loads to handle connected accounts, AI media, scheduling, posting, and the analytics that feed the next batch.
- Cowork owns conversation, memory, and multi-step desktop work
- Genviral publishes to 8 platforms from one API key
- Skill loads from SKILL.md — Cowork picks it up automatically
Skill is MIT-licensed · @genviral/cli on npm
# Drop the skill into Claude's skills folder$ git clone https://github.com/fdarkaou/genviral-skill.git \$ ~/.claude/skills/genviral# Install the CLI Cowork shells out to$ npm install -g @genviral/cli# Then in the Cowork chat:# "Use the Genviral skill to post tomorrow's Reel to Instagram."
Two layers
Cowork reasons. Genviral executes.
Cowork is great at planning, conversation, and multi-step desktop work. Genviral is great at being the only tool it actually needs to do social.
Cowork owns
Desktop-native chat
Cowork runs where your other work runs. The same window that drafts the LinkedIn post can call into Genviral to publish it — no terminal context switch.
Skills system
Cowork loads skills from local files. Drop the Genviral skill in the right folder and Claude knows how to plan, post, render, and check analytics on demand.
Persistent context
Memory survives across turns and sessions. Brand voice, board lists, account rules, and the last week's performance are all there next time you open the chat.
Conversational handoff
Approve, redirect, or rewrite mid-task. Cowork can pause for confirmation, accept tweaks in plain English, and resume without losing thread.
Genviral owns
Connected social accounts
TikTok, Instagram, YouTube, Pinterest, LinkedIn, Facebook, X, and Bluesky behind one API key — no Meta or TikTok partner approval wait.
AI media generation
Slideshows, images, and videos rendered through Genviral's AI Studio. No separate model wiring — Cowork calls one endpoint and gets a finished asset.
Cross-platform scheduling
One queue, every platform. Idempotent posting via `external_id`, retry-safe drafts, and per-account cooldowns Cowork can drive from one endpoint.
Analytics feedback loop
Genviral feeds last-30-day performance back to Cowork so the next batch rewrites hooks against whichever format actually outperformed.
Setup
From zero to a sample post in 5 steps
Each step links to the real surface in your dashboard. Run them once, then let Cowork take the recurring work.
- 01Step 1 of 5
Drop the Genviral skill into Claude's skills folder
Cowork auto-loads skills from your local skills directory. The Genviral skill ships an opinionated SKILL.md, slideshow workflow, defaults file, and a feedback loop tuned for social — no manual wiring required.
View the skill on GitHubClone the skill into Claude's skills directory
- 02Step 2 of 5
Install the Genviral CLI
The skill shells out to `genviral`, the same CLI any agent uses. Cowork's tool calls run shell, the shell runs `genviral`, and Genviral does the rest.
View on npmInstall once, globally
- 03Step 3 of 5
Create a scoped API key
Create one key per workspace Cowork is allowed to drive. Drop it into `GENVIRAL_API_KEY` in your shell profile so the skill picks it up on every Cowork session.
Create API keySet the key once for your shell
- 04Step 4 of 5
Connect your social accounts in Genviral
Connect TikTok, Instagram, YouTube, Pinterest, LinkedIn, Facebook, X, and Bluesky once in the dashboard. Cowork never touches OAuth — it just reads the account list and uses the IDs.
Connect accountsConfirm Cowork can see your accounts
- 05Step 5 of 5
Ask Cowork to draft one sample post
In the Cowork chat, ask Claude to generate one slideshow, review it, and create a draft post. Cowork uses the skill end-to-end — you watch it work before promoting anything to public.
Read related guides
Use cases
Six recurring Cowork workflows
Each one follows the same loop: Cowork plans, Genviral renders and publishes, analytics feeds the next chat.
TikTok
Daily slideshows from a fixed format
Pinterest
Recurring infographic pins
YouTube
Shorts from a shared queue
Instagram
Reels from an approved media folder
LinkedIn
Posts from release notes & drafts
Facebook
Cross-post filler for brand-page trust
Why an API layer
Cowork still needs a real execution surface
You could wire Cowork into every platform's API yourself. In practice that's slow and breaks often. Here's the comparison.
Wire it yourself
Meta and TikTok partner approvals can take months
Every platform has its own auth, post settings, and quirks
AI assets need separate model providers and plumbing
Scaling to many accounts gets you shadowbanned and locked out
Genviral does this
Genviral fronts those approvals so Cowork posts on day one
One endpoint per concept; Genviral maps it per platform
Genviral's AI Studio ships slideshows, images, and video in-API
Hosted, pre-warmed accounts keep posting reliable past the early stage
Guides
What to read before you wire this up
The developer surfaces are the source of truth. Each link is one of the integration points Cowork calls under the hood.
- Read guide
All Genviral developer surfaces
Side-by-side of the REST API, the CLI, the agent skill, and the hosted accounts add-on. Pick the integration that matches your runtime.
- Read guide
Genviral Partner API reference
Full request/response shapes for every endpoint Cowork will call. `create-post`, `slideshows/*`, `analytics/*`, and the Studio routes are the high-traffic ones.
- Read guide
Hermes Agent + Genviral
The hosted-agent variant: same API surface, but Hermes owns memory and cron natively instead of you keeping Cowork open.
- Read guide
OpenClaw social media skill
The same skill Cowork loads, packaged for OpenClaw runtimes. Useful if you want a continuous, self-improving agent loop.
FAQ
Claude Cowork social media questions
The details teams ask before handing recurring social workflows to a desktop agent.
What is Claude Cowork?
Cowork is Anthropic's collaborative Claude surface — a desktop chat where Claude can plan, run multi-step work, and use locally-loaded skills. It's the same Claude model you know, paired with a tool layer designed for sustained work alongside you.
How does Cowork post to social media?
Cowork itself doesn't ship with platform connectors. You install the Genviral skill into Claude's skills directory and the `@genviral/cli` package. Cowork then drives `genviral` shell commands for accounts, slideshows, posts, analytics, and trends — Genviral handles auth, rendering, scheduling, and publishing to every supported network.
Do I need the Genviral skill, or just the CLI?
Both. Cowork looks for skills under Claude's skills directory; the Genviral skill ships SKILL.md, a slideshow workflow, defaults, and a feedback loop Cowork auto-loads. The CLI is what the skill actually shells out to, so you install it alongside.
Which platforms can Cowork post to through Genviral?
TikTok, Instagram, YouTube, Pinterest, LinkedIn, Facebook, X, and Bluesky. Analytics coverage is strongest for TikTok, Instagram, and YouTube. Cowork publishes from your connected accounts via one API key — no Meta or TikTok partner approval wait.
Does this need an MCP server?
No. Cowork uses the skill via local files and shells out to `genviral` directly. There is no separate MCP server to operate, no extra process to keep alive, and no MCP-specific wire format to maintain.
Can Cowork run on a schedule?
Cowork is interactive by design, so it doesn't own cron. For recurring jobs, schedule the `genviral` CLI directly (cron, systemd, or a GitHub Action), or use the Hermes Agent integration, which has native scheduled tasks. Cowork is best for the interactive parts of the loop: planning, reviewing, and approving.
Should I let Cowork publish without confirmation?
Not at first. Post manually for a few days, then have Cowork generate one sample post in chat. Review the image, caption, tags, and destination. Only after the sample is right should you let Cowork publish without asking. Use draft modes (TikTok MEDIA_UPLOAD, YouTube unlisted, Instagram private) for the first few runs.
Get started
Give Claude Cowork a real social media backend
Connect your accounts, scope an API key, and let Cowork drive a skill built for generated content, scheduled posts, teams, and analytics.