Make every blog, deck, and post sound like your brand
Stack a voice skill with a content skill so every format sounds like you.
Once a campaign calendar exists, each entry can fan out into per-channel deliverables through skill stacks. Free Agent Skills orchestrate the launch and execute each piece. Learn the method and run it in Claude.
Free to try. One click loads the skill into Claude or ChatGPT, with no account and no setup.
A content calendar is easy to plan and brutal to execute. Every row means a blog, a handful of posts, an email, maybe a landing page — across channels, on-brand, on schedule. Do it by hand and the calendar slips the moment things get busy; the ambitious quarter becomes three posts and an apology.
The fix is to stop treating the calendar as a list of things to write and start treating it as input to a system. An orchestration skill turns each entry into a coordinated plan; skill stacks execute each deliverable. You’re no longer writing a quarter of content — you’re running it. That’s the difference between a calendar you aspire to and one you actually ship.
The skill isn’t magic. It encodes a proven framework anyone can learn. Here’s the method itself, so you understand what it’s doing for you.
The insight that makes content scale: once a campaign calendar exists, each entry is effectively a prompt. A single row — “Week 3: launch the eligibility feature” — fans out into a blog post, three LinkedIn posts, an email sequence, and a landing page, each produced by a skill stack. The calendar stops being a to-do list and becomes the input to a production system.
Two layers make it work. An orchestration layer (product-launch-orchestrator) decides the launch tiers, channel mix, timing, and the deliverables checklist — the plan. An execution layer (the content stack: voice × content × format) produces each deliverable on-brand. The orchestrator says what and when; the stack produces the thing. Chain them and one calendar drives a quarter of coordinated, on-brand output.
Use any one on its own, or chain them. Each hands its output to the next. Every one is free in the public library.
The orchestration layer — launch tiers, channel coordination, timing sequences, and a deliverables checklist that turns a calendar into a plan.
Produces the briefs and keyword map so each calendar entry starts from intent, not a blank topic.
Executes the long-form pieces on-brand (stacked with your voice skill).
Executes the social deliverables for each calendar entry, in your voice.
Turns a campaign beat into a nurture sequence — the email channel of the fan-out.
Any time your content ambitions outrun your capacity to hand-produce — a product launch, a campaign, or just a consistent publishing cadence across channels. It’s the scale layer on top of skill stacking.
It turns a campaign calendar into executed deliverables. The orchestrator plans the launch — tiers, channels, timing, and the checklist of what each beat needs. Then the content stack produces each piece: a brief from seo-content-strategist, the long-form from blog-generator, social from linkedin-post-generator, nurture from email-sequence-architect — all in your brand voice.
The result is the scale story: instead of writing each piece from scratch, each calendar entry fans out through skills into a coordinated set of on-brand channel deliverables.

Real prompts, and what the skill hands back.
“Plan a Q3 launch for our eligibility feature: launch tiers, channels, and a deliverables checklist for each week.”
A launch plan with tiers, channel coordination, timing, and a per-beat deliverables checklist — the calendar turned into a plan.
“Take week 3 of that plan and produce all the deliverables in our brand voice — blog, three LinkedIn posts, and a nurture email.”
The full per-channel deliverable set for that calendar entry, produced on-brand by the content stack.
Each entry is a prompt that fans out into deliverables — the calendar drives production.
One layer plans (tiers, channels, timing); the stack produces each on-brand piece.
One beat becomes a blog + social + email set, coordinated and consistent.
The voice layer rides the whole stack, so scale doesn’t mean drift.
Stack image/video skills and connectors so assets come out on-brand too.
The pattern is orchestrator → briefs → content stack per channel. product-launch-orchestrator plans the beats; seo-content-strategist briefs them; the content stack executes each deliverable on-brand.
It builds on skill stacking: stacking is the unit of production, and the calendar is the loop that runs it at scale.
Plan with the orchestrator, execute with the content stack:
Already connected your library to Claude? Tell it: “Use the product-launch-orchestrator skill (and the others above) from the agentman_skills MCP server.”
Not connected yet? The Try in Claude / ChatGPT button loads the first one from the public library, with no setup. Or connect your library.
Click “Try in Claude / ChatGPT” above, or — if you’ve connected your library — tell Claude: “Use the product-launch-orchestrator skill from the agentman_skills MCP server.”
Run product-launch-orchestrator to set launch tiers, channel mix, timing, and a deliverables checklist for each calendar beat.
Run seo-content-strategist to turn each calendar row into a content brief with intent and keywords — so execution starts from a plan, not a blank page.
For each deliverable, run the content stack — blog-generator, linkedin-post-generator, email-sequence-architect — with your brand voice as input, so every piece is on-brand.
One calendar entry becomes a blog + social + email set. Repeat per row, and the quarter produces itself.
Stack an on-brand image skill (and an image/video connector) so hero images and assets come out on-brand too — the way our own blog heroes are produced.
The calendar becomes the loop; skill stacking is the unit. That’s content at scale without a content team the size of the calendar.
One click loads the skill into Claude or ChatGPT. No account, no setup.
Skill stacking produces one on-brand piece. This is the scale layer on top: an orchestration skill turns a whole calendar into a coordinated plan, and skill stacks execute each deliverable. Stacking is the unit; the calendar is the loop.
No. Run the orchestrator alone to plan a launch, or the content stack alone to produce one piece. Chained, they turn a calendar into executed, per-channel deliverables.
Yes — stack an on-brand image skill with an image or video connector. That’s how our own blog hero images are produced: an on-brand image skill stacked with an in-house generation connector.
No. Click “Try in Claude / ChatGPT” above and the orchestrator loads from our public library — no setup. Clone the skills to customize and share them.