Generate editorial calendars for blogs with topic clusters, publishing schedules, material-change reviews, update plans, seasonal opportunities, content mix formula, template integration, and distribution scheduling. Plans monthly or quarterly calendars around reader needs, evidence changes, and sustainable publishing capacity. Use when user says "editorial calendar", "content calendar", "blog calendar", "publishing schedule", "blog plan", "content plan", "what should I write".
blog-calendar is an editorial-planning skill that generates monthly or quarterly content calendars for blogs. It solves the problem of ad-hoc, unsustainable publishing by planning topics around reader needs, topic clusters, evidence changes, and realistic team capacity. Explicitly, it does not treat publishing or update frequency as a ranking or citation signal, positioning itself as an evidence-grounded planning aid rather than a growth-hacking gimmick.
The workflow starts by understanding the blog (niche, existing content scanned via Glob for markdown/HTML, cadence, timeframe, and goals), then designs three to five topic clusters (pillar plus supporting content) for topical authority. A content-decay detection step scans existing posts for material-change signals (fact volatility, performance trends, source availability, reader intent) and outputs a prioritized decay report, with clear guidance not to prioritize updates solely because a frontmatter date is old. It plans freshness review triggers, researches seasonal and trending hooks (using Google Trends and WebSearch, validating timing against official sources like the Google Search Status Dashboard), and finally generates the calendar using a content-mix formula (roughly 60% new, 30% refreshes, 10% repurposed) with template recommendations from twelve types and a week-by-week table.
It targets content strategists, SEO managers, and solo bloggers who need a defensible publishing plan. It operates at the FLOW Find stage and cross-references the /blog flow find command and the content-templates reference, so it is designed to work within the broader blog skill collection.
Monthly or quarterly editorial calendars, with a default publishing cadence of twice per week that you can adjust.
It runs content-decay detection on existing posts, scoring material-change evidence and performance context into Critical/High/Medium/Low priorities, and applies a 60% new / 30% refresh / 10% repurposed content-mix heuristic.
It uses WebSearch and Google Trends for seasonal and trend timing, and advises validating algorithm-update timelines against the official Google Search Status Dashboard rather than a static list.
It cross-references /blog flow find for keyword discovery and the content-templates reference file, so it is intended as part of the larger blog skill set.
No. It states plainly that it does not treat publication or update frequency as a ranking or citation signal.
Quick Setup:
.claude/skills/Repository
agricidaniel/claude-blog