// Editorial calendar planning and content scheduling. Use when user wants to plan a content calendar, create a publishing schedule, organize content across platforms, or plan a content series.
| name | content-calendar |
| description | Editorial calendar planning and content scheduling. Use when user wants to plan a content calendar, create a publishing schedule, organize content across platforms, or plan a content series. |
Check for brand context: Read brand/VOICE.md if it exists. Calendar planning should align content themes with brand pillars. If the user has already run the content-strategy skill, reference the content pillars and briefs from that output.
Determine the calendar type: Ask the user (or infer from their prompt) what kind of planning they need:
templates/monthly-calendar.md.template)templates/campaign-plan.md.template)templates/content-series.md.template)Gather inputs: Platforms the user publishes on, existing content pillars, any fixed dates (launches, events, holidays), production capacity (how much content per week is realistic), and current content pipeline.
Understand the constraints before scheduling anything:
cadence-guide.md.brand/BRAND.md or the output of the content-strategy skill if available. If no pillars are defined, suggest 3-5 based on the user's context.Set the publishing cadence for each platform based on:
cadence-guide.md for recommended frequencies.Recommended starting cadences for a solo creator or small team:
| Platform | Minimum Viable Cadence | Ideal Cadence |
|---|---|---|
| Blog | 1/week | 2/week |
| X / Twitter | 3/week | 1-2/day |
| 2/week | 4-5/week | |
| Newsletter | 1/every two weeks | 1/week |
| YouTube | 1/every two weeks | 1/week |
| 1/week | 2-3/week |
Assign topics to calendar slots:
Build the calendar using the appropriate template:
templates/monthly-calendar.md.template. Week-by-week view with columns for date, platform, format, topic, pillar, status, and notes.templates/campaign-plan.md.template. Timeline view with phases, content pieces per phase, and coordinated multi-platform execution.templates/content-series.md.template. Sequential view showing how individual pieces connect, with consistent cadence and a connecting thread.Review the assembled calendar for:
When the same theme appears across platforms, adapt it for each platform's norms:
| Platform | Adaptation |
|---|---|
| Blog | Full-depth treatment with structure, examples, and detail |
| X / Twitter | Extract the sharpest insight as a hook. Thread for more depth. |
| Professional framing, personal perspective, lesson-oriented | |
| Newsletter | Curated summary with personal commentary and links |
| YouTube | Visual treatment, demo or walkthrough format |
| Community-first framing, practical value, avoid self-promotion tone |
The key principle: Same theme, different treatment. Never copy-paste the same text across platforms. Each platform's audience expects content that feels native.
Use these status labels for tracking:
| Status | Meaning |
|---|---|
idea | Topic identified, no brief yet |
briefed | Content brief is written |
in-progress | Draft is being written |
review | Draft is complete, being reviewed |
scheduled | Final version ready, publication date set |
published | Live |
flex | Slot reserved for reactive/timely content |
This skill coordinates with the broader content system:
| Need | Skill |
|---|---|
| Define content pillars | /content strategy |
| Write a blog post from the calendar | /content blog |
| Write a thread from the calendar | /content twitter |
| Write a LinkedIn post from the calendar | /content linkedin |
| Create a video from the calendar | /content video |
| Repurpose one piece into multiple formats | /content repurpose |
| Audit a piece before publishing | /content audit |
Before delivering the calendar, verify:
Content studio with brand consistency. Use this skill whenever the user wants to create content — blog posts, social media (X/Twitter, LinkedIn, Reddit, HN), presentations (Slidev/Reveal/Spectacle), infographics, image prompts, video scripts (Remotion), editorial calendars, or content audits. Also triggers on brand setup, voice profiling, content repurposing, and content strategy. Covers any request involving writing, publishing, visual content creation, or content planning. Even if the user doesn't say "content" explicitly — if they're asking to write a blog post, create slides, draft a thread, plan a content calendar, or check content quality — use this skill.
Content quality audit with anti-slop detection and brand consistency scoring. Use when user wants to check content quality, audit a draft, score content, verify brand consistency, detect AI-generated patterns, or run a quality check before publishing.
Long-form blog post generation with brand voice integration and anti-slop enforcement. Use when user wants to write a blog post, article, tutorial, case study, opinion piece, deep dive, or listicle.
Hacker News post generation for Show HN, Ask HN, and submissions. Use when user wants to post to Hacker News or write a Show HN/Ask HN post.
Image prompt engineering for AI image generation models. Use when user wants to generate images, create image prompts, or optimize prompts for DALL-E, Midjourney, Stable Diffusion, or other image generation tools.
Generate SVG and HTML infographics with brand-aware design. Use when user wants to create an infographic, data visualization, process flow, comparison chart, stat card, or visual data summary.