Generate and manage an editorial content calendar with publication dates, channel assignments, and cadence tracking. Use this skill when the user asks to 'create a content calendar', 'editorial calendar', 'publication schedule', 'when to publish', 'content cadence', 'plan publications', 'schedule content', or wants to organize content pieces into a time-based publishing plan — even if they don't say 'calendar' explicitly.
From cogni-marketingnpx claudepluginhub cogni-work/insight-wave --plugin cogni-marketingThis skill is limited to using the following tools:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Generate a structured editorial calendar from the content strategy and campaigns. The calendar is the operational plan — it turns the strategic content matrix into dated, assigned, trackable publication slots.
The calendar is maintained in two synchronized formats:
calendar/content-calendar.yaml — Machine-readable source of truthcalendar/content-calendar.md — Human-readable rendered viewcontent-strategy.json — all planned content across markets and GTM pathscampaigns/*.json — touchpoint timelines with day offsetscontent/ — identify what's generated (draft) vs. still plannedmarketing-project.json — cadence defaultsFor each content piece, assign:
Apply cadence rules from marketing-project.json:
YAML source (content-calendar.yaml):
calendar:
start_date: "2026-04-01"
end_date: "2026-06-30"
entries:
- date: "2026-04-01"
day: "Mon"
market: "mid-market-saas-dach"
gtm_path: "ai-predictive-maintenance"
type: "demand-generation"
format: "linkedin-post"
title: "Trend hook: AI predictive maintenance"
file: "content/demand-generation/mid-market--ai-pred--linkedin-post-01.md"
channel: "linkedin"
status: "drafted"
campaign: "ai-pred-q2"
owner: "marketing"
notes: ""
Markdown view (content-calendar.md):
# Content Calendar — Q2 2026
## April 2026
| Date | Day | Market | Type | Format | Title | Channel | Status |
|------|-----|--------|------|--------|-------|---------|--------|
| Apr 1 | Mon | DACH mid-market | DG | LinkedIn post | Trend hook: AI pred. | LinkedIn | ✅ draft |
| Apr 3 | Wed | DACH mid-market | TL | Blog | AI-Driven Predictive... | Website | ✅ draft |
| Apr 4 | Thu | DACH mid-market | DG | LinkedIn post | Blog promo | LinkedIn | ⬜ planned |
...
CSV export (on request via /content-calendar --export csv):
date,market,type,format,title,channel,status,campaign,owner,file
2026-04-01,mid-market-saas-dach,demand-generation,linkedin-post,"Trend hook",linkedin,drafted,ai-pred-q2,marketing,content/demand-generation/...
After building, check for:
Present calendar summary:
Content Calendar: Q2 2026 (13 weeks)
Total entries: 42
By status: 12 drafted, 30 planned
By channel: LinkedIn 20, Blog 8, Email 8, Webinar 2, Other 4
Markets: 2 active
Urgent (next 2 weeks):
⚠️ Apr 1: LinkedIn post — drafted, ready to schedule
⚠️ Apr 3: Blog — drafted, needs review
🔴 Apr 4: LinkedIn promo — NOT YET GENERATED
Adjust dates? Add/remove entries? Or save as-is?
The calendar can be updated incrementally:
/content-calendar --add — Add new entries/content-calendar --update {date} --status published — Mark as published/content-calendar --reschedule {date} --to {new_date} — Move an entry/content-calendar --export csv — Export for tool import