[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ED198SH8RXEEFT0QDHVCFC":3,"skill-same:01M7ED198SH8RXEEFT0QDHVCFC":49},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":13,"repositoryHtmlUrl":25,"repositoryHomepageUrl":6,"ownerHtmlUrl":26,"ownerBlogUrl":6,"ownerDescription":27,"updatedAt":28,"install":29,"resources":42},"01M7ED198SH8RXEEFT0QDHVCFC","blog-calendar",null,"jonahthan433\u002FCortexOS","jonahthan433","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F211465495?v=4","01M7ECH9HPHGA89DCXHHJBTS3C","jonah.ai","01M7ECH9JCEM45DZMWPT7148S1",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fproductivity\u002Fblog-calendar\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"# blog-calendar\n\n# Blog Calendar: Editorial Planning\n\nGenerates editorial calendars with topic clusters, publishing cadence,\nfreshness update schedules, content decay detection, template recommendations,\ndistribution planning, and seasonal hooks. Optimized for building topical\nauthority (Google) and maintaining citation freshness (AI platforms).\n\n## Cross-reference\n\nThis skill operates at the FLOW Find stage. Before selecting topics, run\n`\u002Fblog flow find` for keyword discovery, content prioritization, and audience\navatar prompts that should inform cluster selection and topic sequencing.\n\n## Workflow\n\n### Step 1: Understand the Blog\n\nGather context:\n1. **Niche\u002Findustry**: What is the blog about?\n2. **Existing content**: Scan for existing blog posts (Glob for *.md, *.mdx, *.html)\n3. **Publishing cadence**: How often can they publish? (default: 2x\u002Fweek)\n4. **Timeframe**: Monthly or quarterly calendar?\n5. **Business goals**: What should the blog drive? (traffic, leads, authority)\n\n### Step 2: Topic Cluster Design\n\nDesign 3-5 topic clusters (pillar + supporting content):\n\n```\nCluster: [Pillar Topic]\n├── Pillar Page: [Comprehensive guide - 3,000+ words]\n├── Supporting: [Subtopic 1 - 2,000 words]\n├── Supporting: [Subtopic 2 - 2,000 words]\n├── Supporting: [Subtopic 3 - 1,500 words]\n├── Comparison: [X vs Y - 1,500 words]\n└── FAQ: [Common questions - 1,500 words]\n```\n\nEach cluster should:\n- Target a primary keyword theme\n- Cover the topic comprehensively for topical authority\n- Include varied content types (guides, comparisons, how-tos, listicles)\n- Support internal linking between cluster pages\n\n### Step 2.5: Content Decay Detection\n\nScan existing blog posts for `lastUpdated` or `date` fields in frontmatter.\nClassify each post by staleness using these thresholds:\n\n| Traffic Level | Stale Threshold | At-Risk Threshold |\n|---------------|----------------|-------------------|\n| High-traffic posts | >30 days since update | >90 days |\n| Medium-traffic posts | >90 days since update | >180 days |\n| Low-traffic posts | >180 days since update | >365 days |\n\nReference: 76% of top AI citations are from content updated within 30 days.\n\nOutput a decay report:\n\n```\n## Content Decay Report\n| Post | Last Updated | Days Stale | Priority | Action |\n|------|-------------|-----------|----------|--------|\n| [slug] | [date] | [N] | Critical | Refresh immediately |\n| [slug] | [date] | [N] | High | Schedule this month |\n| [slug] | [date] | [N] | Medium | Schedule this quarter |\n```\n\nPriority levels:\n- **Critical**: High-traffic post stale >30 days: refresh immediately\n- **High**: Any post stale beyond its threshold: schedule this month\n- **Medium**: Posts approaching their threshold: schedule this quarter\n- **Low**: Posts within threshold: no action needed\n\n### Step 3: Freshness Update Schedule\n\nAI platforms heavily favor fresh content (76% of top citations updated within 30 days).\n\nPlan update cycles:\n- **High-priority posts** (traffic drivers): Update every 30 days\n- **Medium-priority posts**: Update every 90 days\n- **Low-priority posts**: Update annually\n- **Evergreen posts**: Update when data changes\n\n### Step 4: Seasonal & Trending Hooks\n\nResearch seasonal opportunities:\n1. **Industry events**: Conferences, product launches, algorithm updates\n2. **Seasonal trends**: Use WebSearch to check Google Trends for the niche\n3. **Annual reports**: When do major studies release new data?\n4. **Algorithm updates**: Google core updates (typically 3-4 per year)\n\n#### Seasonal Trends Integration\n\n- Map seasonal peaks to content production schedule\n- Plan content 4-6 weeks before seasonal peaks for indexing lead time\n- Create \"evergreen with seasonal hook\" content (e.g., \"X Guide [Year]\" updated annually)\n- Track industry report release cycles:\n  - Ahrefs Annual State of SEO (typically Q1)\n  - Google Year in Search (December)\n  - HubSpot State of Marketing (Q1)\n  - Gartner Hype Cycle (August)\n  - Major conference dates in the niche\n- Use WebSearch to validate timing of trends before scheduling\n\n### Step 5: Generate the Calendar\n\n#### Content Mix Formula\n\nApply the recommended content mix ratio:\n**60% new content \u002F 30% freshness updates \u002F 10% repurposed content**\n\n| Cadence | Monthly Posts | New | Refreshes | Repurposed |\n|---------|-------------|-----|-----------|------------|\n| 2 posts\u002Fweek | 8 | 5 | 2 | 1 |\n| 3 posts\u002Fweek | 12 | 7 | 4 | 1 |\n| 4 posts\u002Fweek | 16 | 10 | 5 | 1 |\n| 1 post\u002Fweek | 4 | 2-3 | 1 | 0-1 |\n\nWithin new posts, aim for content type diversity:\n- **Guides\u002FHow-tos**: 30-40% of new content\n- **Comparisons\u002FAlternatives**: 15-20%\n- **Listicles\u002FRoundups**: 15-20%\n- **Case studies\u002FData research**: 10-15%\n- **Thought leadership\u002FNews analysis**: 10-15%\n\n#### Template Integration\n\nFor each new post entry, recommend a content template from these 12 available:\n`how-to-guide`, `listicle`, `case-study`, `comparison`, `pillar-page`,\n`product-review`, `thought-leadership`, `roundup`, `tutorial`,\n`news-analysis`, `data-research`, `faq-knowledge`\n\nReference: `references\u002Fcontent-templates.md` for full template details.\n\n#### Monthly Calendar Format\n\n```\n# Editorial Calendar: [Month Year]\n\n## Publishing Cadence: [N] posts\u002Fweek\n## Content Mix: [N] new \u002F [N] refreshes \u002F [N] repurposed\n\n### Week 1: [Date Range]\n| Day | Type | Title | Template | Cluster | Target Keyword | Status |\n|-----|------|-------|----------|---------|---------------|--------|\n| Mon | New | [Title] | how-to-guide | [Cluster] | [keyword] | Draft |\n| Thu | Update | [Existing post] | - | [Cluster] | [keyword] | Refresh |\n\n### Week 2: [Date Range]\n| Day | Type | Title | Template | Cluster | Target Keyword | Status |\n|-----|------|-------|----------|---------|---------------|--------|\n| Mon | New | [Title] | comparison | [Cluster] | [keyword] | Brief |\n| Thu | New | [Title] | listicle | [Cluster] | [keyword] | Brief |\n\n### Week 3: [Date Range]\n[...]\n\n### Week 4: [Date Range]\n[...]\n\n## Content Mix This Month\n- New posts: [N]\n- Freshness updates: [N]\n- Repurposed content: [N]\n- Content types: [guides, comparisons, how-tos, listicles, ...]\n\n## Freshness Update Queue\n| Post | Last Updated | Priority | Scheduled |\n|------|-------------|----------|-----------|\n| [slug] | [date] | High | Week 2 |\n| [slug] | [date] | Medium | Week 4 |\n\n## Seasonal Hooks\n- [Event\u002Ftrend and how to leverage it]\n```\n\n#### Quarterly Calendar Format\n\n```\n# Quarterly Editorial Plan: Q[N] [Year]\n\n## Content Strategy\n- Topic clusters: [N] active\n- New posts planned: [N]\n- Freshness updates planned: [N]\n- Repurposed content: [N]\n- Total content actions: [N]\n\n## Month 1: [Month]\n### Focus: [Primary cluster or theme]\n| Week | Type | Title | Template | Cluster | Keyword |\n|------|------|-------|----------|---------|---------|\n| W1 | New | ... | how-to-guide | ... | ... |\n| W1 | Update | ... | - | ... | ... |\n| W2 | New | ... | comparison | ... | ... |\n[...]\n\n## Month 2: [Month]\n### Focus: [Primary cluster or theme]\n[...]\n\n## Month 3: [Month]\n### Focus: [Primary cluster or theme]\n[...]\n\n## Quarterly Goals\n- [ ] Publish [N] new posts\n- [ ] Update [N] existing posts for freshness\n- [ ] Complete [Cluster] pillar + [N] supporting pages\n- [ ] Achieve [metric target]\n```\n\n### Step 5.5: Topic Cluster Progress Tracking\n\nTrack the build-out state of each topic cluster. Prioritize completing\npartially-built clusters over starting new ones.\n\n```\n## Topic Cluster Progress\n| Cluster | Pillar | Spokes Published | Spokes Planned | Coverage |\n|---------|--------|-----------------|----------------|----------|\n| [Topic] | Published | 5\u002F10 | 5 this quarter | 50% |\n| [Topic] | Draft | 2\u002F8 | 3 this quarter | 25% |\n| [Topic] | Not started | 0\u002F6 | 1 this quarter | 0% |\n```\n\nRules for cluster prioritization:\n- Clusters at 50%+ coverage: highest priority to complete\n- Clusters with published pillar but few spokes: second priority\n- New clusters: only start when existing clusters reach 75%+ coverage\n- Never have more than 3 clusters in active build-out simultaneously\n\n### Step 5.6: Distribution Scheduling\n\nFor each new post, plan distribution across channels. Include distribution\ntiming in the calendar output.\n\n```\n## Distribution Schedule\n| Post | Publish Date | LinkedIn | Reddit | Email | YouTube |\n|------|-------------|----------|--------|-------|---------|\n| [Title] | [Date] | Same day | +2-3 days | Next batch | If pillar |\n```\n\nChannel timing rules:\n- **LinkedIn**: Same day as publish (share key insight + link)\n- **Reddit**: 2-3 days after publish (share genuine insight, not a link drop)\n- **Email newsletter**: Batch weekly (include 2-3 posts per newsletter)\n- **YouTube**: Plan companion video for pillar posts only (resource-intensive)\n- **Twitter\u002FX**: Same day as publish (thread key takeaways)\n\nReference: `references\u002Fdistribution-playbook.md` for detailed channel tactics.\n\n### Step 5.7: Freshness Automation\n\nSet up a system for ongoing freshness maintenance:\n\n```\n## Freshness Schedule: Next 30 Days\n| Post | Last Updated | Next Refresh Date | Priority | Owner |\n|------|-------------|-------------------|----------|-------|\n| [slug] | [date] | [date + 30] | High | [name] |\n| [slug] | [date] | [date + 90] | Medium | [name] |\n```\n\nAutomation recommendations:\n- Set calendar reminders for 30-day refresh cycles on high-traffic posts\n- List posts by \"next refresh date\" in ascending order (most urgent first)\n- Prioritize refresh order by traffic\u002Fimportance\n- After each refresh, update the `lastUpdated` frontmatter field\n- Track refresh history to measure freshness impact on rankings\u002Fcitations\n- Suggest running `\u002Fblog rewrite` for each scheduled refresh\n\n### Step 6: Save & Next Steps\n\nSave the calendar and suggest:\n1. Start with `\u002Fblog brief \u003Cfirst-topic>` to create the first content brief\n2. Use `\u002Fblog write` to generate articles from briefs\n3. Use `\u002Fblog rewrite` for freshness updates on existing content\n4. Re-run `\u002Fblog calendar` next month\u002Fquarter for the next plan\n5. Review the Content Decay Report weekly and address Critical items first\n6. Track Topic Cluster Progress monthly to ensure clusters reach completion\n\n### Step 7: Notion MCP (Optional)\n\nAfter delivering the calendar to chat, attempt `notion-query-data-sources`. If it returns results, Notion is connected — run the push below. If it fails or is unavailable, skip and append the alert.\n\n**If Notion connected:**\n\nThe editorial calendar is structured data (Title, Type, Template, Cluster, Keyword, Status, Publish Date, Author) — a natural Notion database. Push it directly:\n\n1. Call `notion-search` for an existing Content Calendar database in the workspace\n2. If found: call `notion-create-pages` to add each new article\u002Fupdate entry to the existing database — skip entries that already exist (match on Title + Publish Date)\n3. If not found: call `notion-create-database` to initialize a Content Calendar database with properties:\n   - Title (title), Type (select: New \u002F Refresh \u002F Repurposed), Template (select), Cluster (select), Keyword (rich text), Status (select: Brief \u002F Draft \u002F Review \u002F Published), Publish Date (date), Author (person)\n   Then call `notion-create-pages` to populate it with every entry from the calendar\n4. Call `notion-create-view` to add a Calendar view grouped by Publish Date (so the team can see the schedule visually)\n5. Confirm: \"✅ Editorial calendar pushed to Notion — [N] entries added. Calendar view created.\"\n\nOn re-runs (next month\u002Fquarter): call `notion-query-database-view` first to fetch existing entries, skip duplicates, only add new ones.\n\n**If not connected:**\n> 💡 **Notion not connected** — your editorial calendar is output to chat only. Connect the Notion MCP connector to automatically push it to a Notion database with a calendar view your whole team can track. Setup: [notion-mcp-server](https:\u002F\u002Fgithub.com\u002Fmakenotion\u002Fnotion-mcp-server)\n",{},"main","38b32c99e7ed0b8e215d638e92cfa452c1ec3079","skills\u002Fimported\u002Fproductivity\u002Fblog-calendar","https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS","https:\u002F\u002Fgithub.com\u002Fjonahthan433","AI Consultant","2026-10-24 05:13:39",{"source":7,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add jonahthan433\u002FCortexOS --skill blog-calendar",{"tool":35,"command":36},"bunx","bunx skills add jonahthan433\u002FCortexOS --skill blog-calendar",{"tool":38,"command":39},"pnpm","pnpm dlx skills add jonahthan433\u002FCortexOS --skill blog-calendar","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fproductivity\u002Fblog-calendar\u002FSKILL.md",true,[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"skill.json","REFERENCE","参考文档",288,"https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS\u002Fblob\u002Fmain\u002Fskills\u002Fimported\u002Fproductivity\u002Fblog-calendar\u002Fskill.json",[50,56,62,68,74,80],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M7EDQZDQX3Q8Y7GCQX6KN9V7","opportunity-brief","https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS\u002Fblob\u002Fmain\u002Fskills\u002Fsales\u002Fopportunity-brief\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7EDQYA0V9Y99VKBREJJ3MRT","morning-intel","https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fmorning-intel\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EDQVX1JVY0B6PDHKKGM19G","decision-brief","https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fdecision-brief\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7EDQV1GENZAC2SZSD8KZ3GM","weekly-review","https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fweekly-review\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7EDQT2KETJ1Y3CGVN9EKW2J","system-health","https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS\u002Fblob\u002Fmain\u002Fskills\u002Fops\u002Fsystem-health\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M7EDQQN2JK3XPWMS1M4T0F3K","backup-restore","https:\u002F\u002Fgithub.com\u002Fjonahthan433\u002FCortexOS\u002Fblob\u002Fmain\u002Fskills\u002Fops\u002Fbackup-restore\u002FSKILL.md",[],[]]