cms-event-publishlisted

Guided workflow to create a full CMS agenda event: event item (start/end datetime, category, status, scheduling, paywall) + structured body paragraphs (text, photo, quote, embed). Dry-run by default — the user validates before any mutation. Verifies each mutation with a get to confirm. Use by default whenever the user wants to create, add, schedule, or publish an event, agenda item, or calendar entry, even indirectly or with approximate wording. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.
goodbarber/goodbarber-skills · ★ 2 · AI & Automation · score 75

Install: claude install-skill goodbarber/goodbarber-skills

You are an assistant that executes this skill workflow for the user. You MUST execute the required tool workflow and return the output in the required format sections. Do not skip required steps and do not replace the required report/template with a short summary. ## Goal Create a complete, correctly-dated agenda event with its body content in one guided pass, validating each mutation so the published event is never missing its start/end time or description. ## Access contract - `READ_WRITE`. ## Input contract Before starting, gather from the user: - Title (required) - Target category / section (required — resolved to a category id) - `sortDate`: event **start** instant — required, ISO datetime **with timezone offset** - `endDate`: event **end** instant — required, must be after `sortDate` - Optional `date`: editorial listing date (display metadata only) - Optional `allDay` flag (when true, `endDate` may equal `sortDate`) - Optional body blocks (ordered): `text`, `quote`, `photo` (`originalThumbnail`), `embed` (`embedUrl`) - Optional publication control: `status` (`published` / `draft` / `stock`), `publishedDate` (future ISO, **only with `status=stock`**), `publicationEndDate` - Optional `accessTier` (`free` / `premium`) — **IAP apps only** ## Required Tool Workflow (strict order) Follow the sequence below exactly when those tools are available for the request context. 1. **Pre-flight discovery**: - `cms_list_cms_sections` with `type='agenda'` → resolve target