← ClaudeAtlas

blog-editorial-calendarlisted

Run your blog like a queue, not a guessing game. This skill is the orchestration layer on top of blog-topic-research and seo-blog-writer: it keeps an evidence-backed backlog, picks the next topic so your corpus drifts toward the cluster + format mix you defined, schedules posts into a rolling daily cadence, and marks them done — autonomously, two posts a day if you want. It scores every pick by how far each topic cluster is from its target weight (so you never end up with 40 troubleshooting posts and no comparisons), reconciles the backlog against what's actually live on your CMS, and auto-refills by calling blog-topic-research when the queue runs dry. Platform-agnostic: it drives whatever publish adapter seo-blog-writer is configured for (Ghost, WordPress, static site). Built for founders, indie hackers, and content teams who want a hands-off long-tail SEO pipeline that publishes on a schedule and stays balanced. Trigger when the user says: 'what should I write next', 'pick the next topic', 'schedule the nex
AutomateLab-tech/publishing-skills · ★ 4 · Code & Development · score 80
Install: claude install-skill AutomateLab-tech/publishing-skills
# blog-editorial-calendar The scheduler and topic-picker that sits on top of the other two skills. `blog-topic-research` fills a backlog with evidence-backed topics; `seo-blog-writer` turns one topic into a published post. This skill decides **which** topic to write **next** and **when** to publish it, so the corpus drifts toward the content mix you defined instead of whatever you felt like writing that day. ``` /blog-editorial-calendar next [N] # pick + write + auto-schedule into the next slots /blog-editorial-calendar next [N] --draft # pick + write, leave as a draft (no schedule) /blog-editorial-calendar next [N] <slot>[, <slot> ...] # pick + write + schedule each explicit slot /blog-editorial-calendar status /blog-editorial-calendar add "<topic>" --cluster <c> --format <f> [--priority N] [--notes "..."] /blog-editorial-calendar mark-done <id-or-slug> /blog-editorial-calendar sync # reconcile the backlog against what's live on your CMS ``` `next` always writes. With no flags it schedules each post into the next free slot of the rolling cadence; with `--draft` it writes but leaves the post as a draft; with explicit slot args it uses the named windows. The author and target platform come from `config.json` (see below) — this skill never overrides them. --- ## Configuration — `config.json` Everything site-specific lives in `skills/blog-editorial-calendar/config.json`, **not** in this file. Edit i