Download brain/.raw/sources/claude-blog-skill/skills/blog-calendar/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does blog-calendar live?
The publisher keeps it at https://github.com/AgriciDaniel/claude-blog.
Which agents can use blog-calendar?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
>
name: blog-calendar
description: >
Generate editorial calendars for blogs with topic clusters, publishing
schedules, content decay detection, freshness update plans, seasonal
opportunities, content mix formula, template integration, and distribution
scheduling. Plans monthly or quarterly calendars optimized for SEO topic
authority and freshness signals based on content priority.
Use when user says "editorial calendar", "content calendar", "blog calendar",
"publishing schedule", "blog plan", "content plan", "what should I write".
user-invokable: true
argument-hint: "[]"
license: MIT
Blog Calendar: Editorial Planning
Generates editorial calendars with topic clusters, publishing cadence,
freshness update schedules, content decay detection, template recommendations,
distribution planning, and seasonal hooks. Optimized for building topical
authority (Google) and maintaining citation freshness for AI surfaces.
Cross-reference
This skill operates at the FLOW Find stage. Before selecting topics, run
/blog flow find for keyword discovery, content prioritization, and audience
avatar prompts that should inform cluster selection and topic sequencing.
Workflow
Step 1: Understand the Blog
Gather context:
Niche/industry: What is the blog about?
Existing content: Scan for existing blog posts (Glob for *.md, *.mdx, *.html)
Publishing cadence: How often can they publish? (default: 2x/week)
Timeframe: Monthly or quarterly calendar?
Business goals: What should the blog drive? (traffic, leads, authority)
Cover the topic comprehensively for topical authority
Include varied content types (guides, comparisons, how-tos, listicles)
Support internal linking between cluster pages
Step 2.5: Content Decay Detection
Scan existing blog posts for lastUpdated or date fields in frontmatter.
Classify each post by staleness using these thresholds:
Traffic Level
Stale Threshold
At-Risk Threshold
High-traffic posts
>30 days since update
>90 days
Medium-traffic posts
>90 days since update
>180 days
Low-traffic posts
>180 days since update
>365 days
Reference: some practitioner AI-citation SEO datasets report a freshness skew toward recently updated content. Treat this as a directional signal, not a universal rule, unless the dataset, method, and date are available.
Output a decay report:
## Content Decay Report
| Post | Last Updated | Days Stale | Priority | Action |
|------|-------------|-----------|----------|--------|
| [slug] | [date] | [N] | Critical | Refresh immediately |
| [slug] | [date] | [N] | High | Schedule this month |
| [slug] | [date] | [N] | Medium | Schedule this quarter |
Priority levels:
Critical: High-traffic post stale >30 days: refresh immediately
High: Any post stale beyond its threshold: schedule this month
Medium: Posts approaching their threshold: schedule this quarter
Low: Posts within threshold: no action needed
Step 3: Freshness Update Schedule
AI citation surfaces often favor fresh content, but the 30-day signal is directional and methodology-dependent, not a universal rule.
Plan update cycles:
High-priority posts (traffic drivers): Update every 30 days
Medium-priority posts: Update every 90 days
Low-priority posts: Update annually
Evergreen posts: Update when data changes
Step 4: Seasonal & Trending Hooks
Research seasonal opportunities:
Industry events: Conferences, product launches, algorithm updates
Seasonal trends: Use Google Trends UI, API, or exported data when available; if relying on WebSearch only, mark trend timing as unverified
Annual reports: When do major studies release new data?
Algorithm updates: Validate the current Google update timeline against the Google Search Status Dashboard before scheduling update content. Do not rely on a static list.
Seasonal Trends Integration
Map seasonal peaks to content production schedule
Plan content 4-6 weeks before seasonal peaks for indexing lead time
Use WebSearch to validate timing of trends before scheduling
Step 5: Generate the Calendar
Content Mix Formula
Start from this planning heuristic, then adjust for decay risk, authority gaps,
team capacity, and available source material:
60% new content / 30% freshness updates / 10% repurposed content
Cadence
Monthly Posts
New
Refreshes
Repurposed
2 posts/week
8
5
2
1
3 posts/week
12
7
4
1
4 posts/week
16
10
5
1
1 post/week
4
2-3
1
0-1
Within new posts, aim for content type diversity:
Guides/How-tos: 30-40% of new content
Comparisons/Alternatives: 15-20%
Listicles/Roundups: 15-20%
Case studies/Data research: 10-15%
Thought leadership/News analysis: 10-15%
Template Integration
For each new post entry, recommend a content template from these 12 available:
how-to-guide, listicle, case-study, comparison, pillar-page,
product-review, thought-leadership, roundup, tutorial,
news-analysis, data-research, faq-knowledge
Reference: skills/blog/references/content-templates.md for full template details.
Monthly Calendar Format
# Editorial Calendar: [Month Year]
## Publishing Cadence: [N] posts/week
## Content Mix: [N] new / [N] refreshes / [N] repurposed
### Week 1: [Date Range]
| Day | Type | Title | Template | Cluster | Target Keyword | Status |
|-----|------|-------|----------|---------|---------------|--------|
| Mon | New | [Title] | how-to-guide | [Cluster] | [keyword] | Draft |
| Thu | Update | [Existing post] | - | [Cluster] | [keyword] | Refresh |
### Week 2: [Date Range]
| Day | Type | Title | Template | Cluster | Target Keyword | Status |
|-----|------|-------|----------|---------|---------------|--------|
| Mon | New | [Title] | comparison | [Cluster] | [keyword] | Brief |
| Thu | New | [Title] | listicle | [Cluster] | [keyword] | Brief |
### Week 3: [Date Range]
[...]
### Week 4: [Date Range]
[...]
## Content Mix This Month
- New posts: [N]
- Freshness updates: [N]
- Repurposed content: [N]
- Content types: [guides, comparisons, how-tos, listicles, ...]
## Freshness Update Queue
| Post | Last Updated | Priority | Scheduled |
|------|-------------|----------|-----------|
| [slug] | [date] | High | Week 2 |
| [slug] | [date] | Medium | Week 4 |
## Seasonal Hooks
- [Event/trend and how to leverage it]
Track the build-out state of each topic cluster. Prioritize completing
partially-built clusters over starting new ones.
## Topic Cluster Progress
| Cluster | Pillar | Spokes Published | Spokes Planned | Coverage |
|---------|--------|-----------------|----------------|----------|
| [Topic] | Published | 5/10 | 5 this quarter | 50% |
| [Topic] | Draft | 2/8 | 3 this quarter | 25% |
| [Topic] | Not started | 0/6 | 1 this quarter | 0% |
Rules for cluster prioritization:
Clusters at 50%+ coverage: highest priority to complete
Clusters with published pillar but few spokes: second priority
New clusters: only start when existing clusters reach 75%+ coverage
Never have more than 3 clusters in active build-out simultaneously
Step 5.6: Distribution Scheduling
For each new post, plan distribution across channels. Include distribution
timing in the calendar output.
## Distribution Schedule
| Post | Publish Date | LinkedIn | Reddit | Email | YouTube |
|------|-------------|----------|--------|-------|---------|
| [Title] | [Date] | Same day | +2-3 days | Next batch | If pillar |
Channel timing rules:
LinkedIn: Same day as publish (share key insight + link)
Reddit: 2-3 days after publish (share genuine insight, not a link drop)
Email newsletter: Batch weekly (include 2-3 posts per newsletter)
YouTube: Plan companion video for pillar posts only (resource-intensive)
Twitter/X: Same day as publish (thread key takeaways)
Reference: skills/blog/references/distribution-playbook.md for detailed channel tactics.
Step 5.7: Freshness Automation
Set up a system for ongoing freshness maintenance:
## Freshness Schedule: Next 30 Days
| Post | Last Updated | Next Refresh Date | Priority | Owner |
|------|-------------|-------------------|----------|-------|
| [slug] | [date] | [date + 30] | High | [name] |
| [slug] | [date] | [date + 90] | Medium | [name] |
Automation recommendations:
Set calendar reminders for 30-day review cycles on high-traffic or fast-changing posts
List posts by "next refresh date" in ascending order (most urgent first)
Prioritize refresh order by traffic/importance
After each refresh, update the lastUpdated frontmatter field
Track refresh history to measure freshness impact on rankings/citations
Suggest running /blog rewrite for each scheduled refresh
Step 6: Save & Next Steps
Save to calendars/[yyyy-mm]-editorial-calendar.md unless the user specifies
another path. Create calendars/ if it does not exist.
Suggested workflow:
Run /blog strategy when positioning or pillars are unclear
Run /blog cluster plan <seed-keyword> for cluster-heavy calendars
Use /blog brief <first-topic> or /blog outline <first-topic> for the first scheduled item
Use /blog write to generate articles from approved briefs or outlines
Use /blog rewrite for freshness updates on existing content
Re-run /blog calendar next month/quarter for the next plan
Review the Content Decay Report weekly and address Critical items first
Track Topic Cluster Progress monthly to ensure clusters reach completion
How do I install blog-calendar?
Download brain/.raw/sources/claude-blog-skill/skills/blog-calendar/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does blog-calendar live?
The publisher keeps it at https://github.com/AgriciDaniel/claude-blog.
Which agents can use blog-calendar?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.