Blog Calendar Editorial Planner
Turn blog topics, refresh cycles, and distribution timing into an actionable editorial calendar.
The skill primarily generates editorial calendars and requests no credentials, destructive actions, or direct external writes, so permission risk is relatively low; however, it asks to scan project files, use WebSearch, and save results without defining data flows, user confirmation, sensitive-data handling, rollback, or source attribution, so points are deducted.
The workflow and output templates are fairly coherent, with clear cadence defaults, content ratios, and classifications; however, it lacks diagnosable failure behavior for unavailable Glob/WebSearch, invalid dates, missing frontmatter, empty repositories, or unavailable referenced templates, and there are no skill-specific tests, so the static cap and uncertainty apply.
Triggers, inputs, monthly/quarterly formats, and intended blog scenarios are clear; however, non-fit boundaries, language support, and environment constraints are not declared. Seasonal research depends on WebSearch, which may have reachability issues for mainland-China users, and semantic non-trigger conditions are not specified, so points are deducted.
The file has valid frontmatter, MIT licensing, stepwise organization, example tables, and a cross-reference; however, installation guidance, versioning, changelog, maintenance ownership, update path, and availability of referenced files are not clear within the skill, while external-command and repository-layout assumptions remain implicit.
It can produce directly structured topic clusters, schedules, decay reports, refresh queues, and distribution plans, making the core output usable; however, claimed SEO/AI-citation benefits and figures such as “76%” are not verified in the skill, and the actual completion of scanning, trend research, and template integration cannot be confirmed statically, so the score remains conservative.
The skill supplies explicit rules, tables, and procedures, while repository context claims CI and tests exist; however, the supplied tests do not cover blog-calendar key paths, date thresholds, output completeness, or WebSearch behavior, and no independent third-party execution evidence is provided, warranting only limited static evidence credit.
- The “76% of top AI citations” claim and related SEO/AI-platform preferences are unsupported by the supplied source material and should not be treated as verified facts.
- Seasonal-trend planning depends on WebSearch; the skill gives no fallback when search is unavailable or unreachable and does not specify confirmation before external access.
- Confirm the scan scope first, especially if project files may contain sensitive content, and manually review dates, traffic classifications, source attribution, and distribution recommendations.
- The cross-referenced references/content-templates.md and references/distribution-playbook.md were not supplied, so their details and availability cannot be verified.
What does this skill do, and when should you use it?
Blog Calendar is one Agent Skill in the claude-blog repository for producing monthly or quarterly blog editorial calendars. It designs topic clusters, schedules new and updated posts, and identifies content decay, seasonal opportunities, and distribution timing. Its planning model targets SEO topical authority while maintaining AI-citation freshness through recurring update cycles. It is best suited to creators, marketing teams, and agencies managing an ongoing publishing program rather than a single article.
It gathers the blog niche, existing content, publishing cadence, planning timeframe, and business goals. It scans existing Markdown, MDX, or HTML posts and reads frontmatter date or lastUpdated fields. It then designs three to five topic clusters, produces a decay report using traffic and staleness thresholds, plans 30-day, 90-day, annual, or data-change-driven refresh cycles, and adds seasonal and industry-event opportunities. The final calendar applies a 60% new content, 30% freshness updates, and 10% repurposed content mix, recommends templates for new posts, and schedules distribution across LinkedIn, Reddit, email, YouTube, and Twitter/X.
- A solo blogger needs next month's topics and publishing dates for a one- or two-post-per-week cadence.
- A marketing team has a large archive of older posts and needs to prioritize refreshes by traffic and staleness.
- An SEO lead is building topic clusters and needs an ordered plan for pillar pages, supporting articles, comparisons, and FAQs.
- A content team wants to prepare seasonal pieces four to six weeks before expected peaks and coordinate channel distribution.
- An agency needs quarterly calendars for clients while tracking topic-cluster completion and remaining spokes.
What are this skill's strengths and limitations?
- Combines cluster planning, publishing cadence, content decay, refresh scheduling, and channel distribution.
- Provides both monthly and quarterly formats with templates, target keywords, and status fields.
- Uses an explicit 60% new, 30% updated, and 10% repurposed content formula.
- Assigns different freshness cycles to high-, medium-, and low-priority posts.
- Seasonal and Google Trends validation depends on WebSearch, but the source does not identify the exact search implementation or data source.
- The skill does not perform keyword discovery itself; its workflow points to `/blog flow find` or another research process.
- Decay detection depends on posts exposing `date` or `lastUpdated` frontmatter fields.
- The README's test counts and five-gate delivery contract describe the wider claude-blog collection, not isolated test coverage for this skill.
How do you install this skill?
Install it as part of the AgriciDaniel/claude-blog collection. For Claude Code 1.0.33+, run /plugin marketplace add AgriciDaniel/claude-blog, then /plugin install claude-blog@agricidaniel-claude-blog. You may also place the repository's skills/blog-calendar/ folder in an Agent Skills-compatible skills directory; the source does not specify a universal directory path.
How do you use this skill?
In Claude Code, trigger /blog calendar, or use a natural-language request described by the skill, such as “Create a quarterly editorial calendar for a SaaS blog.” If existing content is available, the skill is designed to scan *.md, *.mdx, and *.html files. Before choosing topics, run /blog flow find for keyword discovery, prioritization, and audience-avatar prompts. The source does not document a standalone command interface or save location outside the claude-blog orchestrator.
How does this skill compare with similar options?
Compared with a one-off prompt for article ideas, this skill places topic clusters, legacy-post refreshes, seasonal opportunities, and channel distribution into one monthly or quarterly plan. It is therefore a planning tool, not a standalone article-writing workflow.