Run a content-queue health check
Packaged know-how that tells an agent how to do a job well.
You might say…
“I haven't looked at the calendar in two weeks. Tell me what's broken before I find out the hard way.”
What it does
Reads the master calendar and current pipeline state and produces a health report — date conflicts, topic clusters colliding, channel gaps, and missing Produce handoffs — flagging issues without rescheduling.
Trigger: Use as a periodic pass to surface scheduling risks and pipeline gaps before committing to the next window's schedule.
I/O: Master calendar + pipeline state (drafts / ready / scheduled) → structured health report with flagged issues
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation