$npx -y skills add AgriciDaniel/claude-blog --skill blog-calendarGenerate 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 SE
| 1 | # Blog Calendar: Editorial Planning |
| 2 | |
| 3 | Generates editorial calendars with topic clusters, publishing cadence, |
| 4 | freshness update schedules, content decay detection, template recommendations, |
| 5 | distribution planning, and seasonal hooks. Optimized for building topical |
| 6 | authority (Google) and maintaining citation freshness (AI platforms). |
| 7 | |
| 8 | ## Cross-reference |
| 9 | |
| 10 | This skill operates at the FLOW Find stage. Before selecting topics, run |
| 11 | `/blog flow find` for keyword discovery, content prioritization, and audience |
| 12 | avatar prompts that should inform cluster selection and topic sequencing. |
| 13 | |
| 14 | ## Workflow |
| 15 | |
| 16 | ### Step 1: Understand the Blog |
| 17 | |
| 18 | Gather context: |
| 19 | 1. **Niche/industry**: What is the blog about? |
| 20 | 2. **Existing content**: Scan for existing blog posts (Glob for *.md, *.mdx, *.html) |
| 21 | 3. **Publishing cadence**: How often can they publish? (default: 2x/week) |
| 22 | 4. **Timeframe**: Monthly or quarterly calendar? |
| 23 | 5. **Business goals**: What should the blog drive? (traffic, leads, authority) |
| 24 | |
| 25 | ### Step 2: Topic Cluster Design |
| 26 | |
| 27 | Design 3-5 topic clusters (pillar + supporting content): |
| 28 | |
| 29 | ``` |
| 30 | Cluster: [Pillar Topic] |
| 31 | ├── Pillar Page: [Comprehensive guide - 3,000+ words] |
| 32 | ├── Supporting: [Subtopic 1 - 2,000 words] |
| 33 | ├── Supporting: [Subtopic 2 - 2,000 words] |
| 34 | ├── Supporting: [Subtopic 3 - 1,500 words] |
| 35 | ├── Comparison: [X vs Y - 1,500 words] |
| 36 | └── FAQ: [Common questions - 1,500 words] |
| 37 | ``` |
| 38 | |
| 39 | Each cluster should: |
| 40 | - Target a primary keyword theme |
| 41 | - Cover the topic comprehensively for topical authority |
| 42 | - Include varied content types (guides, comparisons, how-tos, listicles) |
| 43 | - Support internal linking between cluster pages |
| 44 | |
| 45 | ### Step 2.5: Content Decay Detection |
| 46 | |
| 47 | Scan existing blog posts for `lastUpdated` or `date` fields in frontmatter. |
| 48 | Classify each post by staleness using these thresholds: |
| 49 | |
| 50 | | Traffic Level | Stale Threshold | At-Risk Threshold | |
| 51 | |---------------|----------------|-------------------| |
| 52 | | High-traffic posts | >30 days since update | >90 days | |
| 53 | | Medium-traffic posts | >90 days since update | >180 days | |
| 54 | | Low-traffic posts | >180 days since update | >365 days | |
| 55 | |
| 56 | Reference: 76% of top AI citations are from content updated within 30 days. |
| 57 | |
| 58 | Output a decay report: |
| 59 | |
| 60 | ``` |
| 61 | ## Content Decay Report |
| 62 | | Post | Last Updated | Days Stale | Priority | Action | |
| 63 | |------|-------------|-----------|----------|--------| |
| 64 | | [slug] | [date] | [N] | Critical | Refresh immediately | |
| 65 | | [slug] | [date] | [N] | High | Schedule this month | |
| 66 | | [slug] | [date] | [N] | Medium | Schedule this quarter | |
| 67 | ``` |
| 68 | |
| 69 | Priority levels: |
| 70 | - **Critical**: High-traffic post stale >30 days: refresh immediately |
| 71 | - **High**: Any post stale beyond its threshold: schedule this month |
| 72 | - **Medium**: Posts approaching their threshold: schedule this quarter |
| 73 | - **Low**: Posts within threshold: no action needed |
| 74 | |
| 75 | ### Step 3: Freshness Update Schedule |
| 76 | |
| 77 | AI platforms heavily favor fresh content (76% of top citations updated within 30 days). |
| 78 | |
| 79 | Plan update cycles: |
| 80 | - **High-priority posts** (traffic drivers): Update every 30 days |
| 81 | - **Medium-priority posts**: Update every 90 days |
| 82 | - **Low-priority posts**: Update annually |
| 83 | - **Evergreen posts**: Update when data changes |
| 84 | |
| 85 | ### Step 4: Seasonal & Trending Hooks |
| 86 | |
| 87 | Research seasonal opportunities: |
| 88 | 1. **Industry events**: Conferences, product launches, algorithm updates |
| 89 | 2. **Seasonal trends**: Use WebSearch to check Google Trends for the niche |
| 90 | 3. **Annual reports**: When do major studies release new data? |
| 91 | 4. **Algorithm updates**: Google core updates (typically 3-4 per year) |
| 92 | |
| 93 | #### Seasonal Trends Integration |
| 94 | |
| 95 | - Map seasonal peaks to content production schedule |
| 96 | - Plan content 4-6 weeks before seasonal peaks for indexing lead time |
| 97 | - Create "evergreen with seasonal hook" content (e.g., "X Guide [Year]" updated annually) |
| 98 | - Track industry report release cycles: |
| 99 | - Ahrefs Annual State of SEO (typically Q1) |
| 100 | - Google Year in Search (December) |
| 101 | - HubSpot State of Marketing (Q1) |
| 102 | - Gartner Hype Cycle (August) |
| 103 | - Major conference dates in the niche |
| 104 | - Use WebSearch to validate timing of trends before scheduling |
| 105 | |
| 106 | ### Step 5: Generate the Calendar |
| 107 | |
| 108 | #### Content Mix Formula |
| 109 | |
| 110 | Apply the recommended content mix ratio: |
| 111 | **60% new content / 30% freshness updates / 10% repurposed content** |
| 112 | |
| 113 | | Cadence | Monthly Posts | New | Refreshes | Repurposed | |
| 114 | |---------|-------------|-----|-----------|------------| |
| 115 | | 2 posts/week | 8 | 5 | 2 | 1 | |
| 116 | | 3 posts/week | 12 | 7 | 4 | 1 | |
| 117 | | 4 |