blog-calendar
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".
What this skill does
# 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: 1. **Niche/industry**: What is the blog about? 2. **Existing content**: Scan for existing blog posts (Glob for *.md, *.mdx, *.html) 3. **Publishing cadence**: How often can they publish? (default: 2x/week) 4. **Timeframe**: Monthly or quarterly calendar? 5. **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: 1. **Industry events**: Conferences, product launches, algorithm updates 2. **Seasonal trends**: Use WebSearch to check Google Trends for the niche 3. **Annual reports**: When do major studies release new data? 4. **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 Fo
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".