blog-calendar
Skill0 starsChanged 3 months agoMITView on GitHub
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 AI citation freshness requirements (30-day update cycles). Use when user says "editorial calendar", "content calendar", "blog calendar", "publishing schedule", "blog plan", "content plan", "what should I write".
5 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- gaznilmuzammil12-prog/seo-skills-by-gaznilword for word, first seen Nov 16, 2026
- alpit-patel/seo-aeo-geo-kitedited, first seen Nov 8, 2026
- AgriciDaniel/claude-blogedited, first seen Oct 25, 2026
- coopersimson96/ai-content-systemedited, first seen Jun 25, 2026
- megastep/codex-skillsedited, first seen Feb 25, 2026
Other versions5 projects use a version of this.
Word for word · 1
- gaznilmuzammil12-prog/seo-skills-by-gaznil★ 0100% same
Edited · 4
- AgriciDaniel/claude-blog★ 2.7k48% same
- coopersimson96/ai-content-system★ 1799% same
- megastep/codex-skills★ 499% same
- alpit-patel/seo-aeo-geo-kit★ 261% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository85 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/llms-full.txtllms.txt
- docs/llms.txtllms.txt
- llms-full.txtllms.txt
- llms.txtllms.txt
- ab-testingSkill
- accessibilitySkill
- ai-seoSkill
- analyticsSkill
- attributionSkill
- blog-analyzeSkill
- blog-audioSkill
- blog-auditSkill
- blog-brandSkill
- blog-briefSkill
- blog-cannibalizationSkill
- blog-chartSkill
- blog-clusterSkill
- blog-discourseSkill
- blog-factcheckSkill
- blog-flowSkill
- blog-geoSkill
- blog-googleSkill
- blog-imageSkill
- blog-locale-auditSkill
- blog-localizeSkill
- blog-multilingualSkill
- blog-notebooklmSkill
- blog-outlineSkill
- blog-personaSkill
- blog-repurposeSkill
- blog-rewriteSkill
- blog-schemaSkill
- blog-seo-checkSkill
- blogSkill
- blog-strategySkill
- blog-taxonomySkill
- blog-translateSkill
- blog-writeSkill
- canonical-tagSkill
- competitorsSkill
- content-optimizationSkill
- content-strategySkill
- copywritingSkill
- core-web-vitalsSkill
- croSkill
- directory-submissionsSkill
- eeat-signalsSkill
- entity-seoSkill
- featured-snippetSkill
- google-search-consoleSkill
- heading-structureSkill
- indexingSkill
- indexnowSkill
- internal-linksSkill
- keyword-researchSkill
- local-seoSkill
- meta-descriptionSkill
- mobile-friendlySkill
- open-graphSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. 3 are common, 5 are distinctive, and 4 are very specific to this project.
3
Common
Most of the 4 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 96
Medium-priority posts: Update every 90 days
- Distinctive: line 97
Low-priority posts: Update annually
- Distinctive: line 98
Evergreen posts: Update when data changes
- Distinctive: line 104
Seasonal trends: Use WebSearch to check Google Trends for the niche
- Distinctive: line 105
Annual reports: When do major studies release new data?
- Common: line 112
Create "evergreen with seasonal hook" content (e.g., "X Guide [Year]" updated annually)
- Common: line 119
Use WebSearch to validate timing of trends before scheduling
- Common: line 247
Never have more than 3 clusters in active build-out simultaneously
- Very specific: line 286
After each refresh, update the lastUpdated frontmatter field
- Very specific: line 293
Start with /blog brief <first-topic> to create the first content brief
- Very specific: line 294
Use /blog write to generate articles from briefs
- Very specific: line 295
Use /blog rewrite for freshness updates on existing content
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 (AI platforms).
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)
Step 2: Topic Cluster Design
Design 3-5 topic clusters (pillar + supporting content):
Cluster: [Pillar Topic]
├── Pillar Page: [Comprehensive guide - 3,000+ words]
├── Supporting: [Subtopic 1 - 2,000 words]
├── Supporting: [Subtopic 2 - 2,000 words]
├── Supporting: [Subtopic 3 - 1,500 words]
├── Comparison: [X vs Y - 1,500 words]
└── FAQ: [Common questions - 1,500 words]Each cluster should:
- Target a primary keyword theme
- 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: 76% of top AI citations are from content updated within 30 days.
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 platforms heavily favor fresh content (76% of top citations updated within 30 days).
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 WebSearch to check Google Trends for the niche
- Annual reports: When do major studies release new data?
- Algorithm updates: Google core updates (typically 3-4 per year)
Seasonal Trends Integration
- Map seasonal peaks to content production schedule
- Plan content 4-6 weeks before seasonal peaks for indexing lead time
- Create "evergreen with seasonal hook" content (e.g., "X Guide [Year]" updated annually)
- Track industry report release cycles:
- Ahrefs Annual State of SEO (typically Q1)
- Google Year in Search (December)
- HubSpot State of Marketing (Q1)
- Gartner Hype Cycle (August)
- Major conference dates in the niche
- Use WebSearch to validate timing of trends before scheduling
Step 5: Generate the Calendar
Content Mix Formula
Apply the recommended content mix ratio: 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: 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]Quarterly Calendar Format
# Quarterly Editorial Plan: Q[N] [Year]
## Content Strategy
- Topic clusters: [N] active
- New posts planned: [N]
- Freshness updates planned: [N]
- Repurposed content: [N]
- Total content actions: [N]
## Month 1: [Month]
### Focus: [Primary cluster or theme]
| Week | Type | Title | Template | Cluster | Keyword |
|------|------|-------|----------|---------|---------|
| W1 | New | ... | how-to-guide | ... | ... |
| W1 | Update | ... | - | ... | ... |
| W2 | New | ... | comparison | ... | ... |
[...]
## Month 2: [Month]
### Focus: [Primary cluster or theme]
[...]
## Month 3: [Month]
### Focus: [Primary cluster or theme]
[...]
## Quarterly Goals
- [ ] Publish [N] new posts
- [ ] Update [N] existing posts for freshness
- [ ] Complete [Cluster] pillar + [N] supporting pages
- [ ] Achieve [metric target]Step 5.5: Topic Cluster Progress Tracking
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: 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 refresh cycles on high-traffic posts
- List posts by "next refresh date" in ascending order (most urgent first)
- Prioritize refresh order by traffic/importance
- After each refresh, update the
lastUpdatedfrontmatter field - Track refresh history to measure freshness impact on rankings/citations
- Suggest running
/blog rewritefor each scheduled refresh
Step 6: Save & Next Steps
Save the calendar and suggest:
- Start with
/blog brief <first-topic>to create the first content brief - Use
/blog writeto generate articles from briefs - Use
/blog rewritefor freshness updates on existing content - Re-run
/blog calendarnext 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

