Publish, post, and take the stage
31 primitives in this stage — 30 skills · 1 agent. Concept-stage catalogue, kept vendor-agnostic.
Standing queue-health watcher →
"I don't want to check the calendar every week. I want to be told when something is actually about to go wrong."
Run the final pre-send proof and clean-up pass →
"I know the piece is good. I just need to know nothing in it will embarrass me when it lands."
Sharpen the subject line and preview text →
"The piece is done. Now I need five words that make someone open it instead of archive it."
Spin up the channel distribution set for this send →
"The issue just went live. I need ten minutes of promotion assets, not a two-hour writing session."
Draft a batch of replies to incoming reactions →
"Forty replies came in today. I want to respond to all of them without spending three hours writing."
Surface standout responses worth highlighting →
"Something in the replies is better than anything in the issue. I just need to find it before the moment passes."
Read the per-send numbers and capture the takeaway →
"The numbers are in. I want to know what they're actually telling me, not just what they are."
Event brief and audience digest →
"I said yes to the event. Now I need to know exactly who's in the room and what they expect before I touch the deck."
Tailor the talk to this room →
"The talk works. I just need this version of it to feel like it was written for this room."
Harvest reusable material from the session →
"I just gave a talk. The transcript is sitting there. There's material in it I'll never use unless I pull it now."
Turn the host's brief into your talking points →
"I have the host's brief. I need to walk into this conversation knowing exactly what I want to say before they ask the first question."
Surface the stories and examples that land each point →
"I know what I want to say. I need the story that makes the abstract point land for this particular room."
Anticipate likely and hard questions →
"I want to be surprised by nothing. Give me the hard questions before the host does."
Compress prep into an on-air prompt card →
"I've done all the prep. I just need it on one screen so I can be present instead of hunting for notes."
Debrief and self-critique the appearance →
"I just came off the mic. Before I forget how it felt, I want to know what actually worked and what I'll do differently."
Tune the angle and voice to the host outlet →
"I have something to say. I need to say it in their language, not mine, or it won't get past the editor."
Draft the bylined guest piece →
"The angle is locked. Now I need the actual piece, not a skeleton — something an editor can read and say yes to."
Work the editor's revisions →
"The editor came back with changes. Some are right. Some would gut the argument. I need to know which is which before I respond."
Write the framing post for your channels →
"The episode is live. I need to tell my audience why they should care without just re-posting the link."
Pull the highlight to clip →
"There's one line in that interview that's better than the whole hour. I need to find it and get it out as a clip."
Triage comment threads worth a reply →
"Sixty comments in two hours. I can answer maybe twelve. Tell me which twelve actually matter."
Draft a reply in the scholar's voice →
"I know what I want to say back. I just need it drafted in my voice so I can review and send, not rewrite from scratch."
Reframe a difficult or hostile question on the fly →
"Someone just asked a question designed to make me look bad. I need a reframe that's honest but doesn't let them set the terms."
Capture and structure post-session conversation notes →
"I just had six conversations in forty minutes. I remember the faces. I need to remember what was said before I get on the plane."
Assess whether and how to engage a public thread →
"Someone just pushed back publicly. I want to know if engaging helps or just feeds the thread before I type a word."
Surface and prioritise live chat questions →
"I'm delivering live and the chat is moving fast. I need someone watching it so I can stay present on stage."
Run a content-queue health check →
"I haven't looked at the calendar in two weeks. Tell me what's broken before I find out the hard way."
Plan and stagger the publish schedule for a horizon →
"I have twelve things ready to ship. I need to know what goes when so nothing gets buried by the next thing."
Orchestrate cross-channel release order for a topic or launch →
"The same piece is going out on three channels. I need them to build on each other, not compete."
Assess handoff readiness and draft the chase →
"The calendar says something ships tomorrow. The pipeline says it isn't done. I need to know now, not on send day."
Run the post-cycle calendar retro and forward update →
"The cycle is done. I want to know what slipped, why it keeps slipping, and what I need to change so it doesn't happen next month."