What it does
Takes a rough list of topics or keywords and a publishing cadence, then produces a calendar with a proposed publish date, slug, and target keyword for each, spacing out similar topics so the site doesn't publish two near-duplicate posts in the same week. It checks existing scheduled and published posts to avoid a date or topic collision.
Install
This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:
Use it in your AI assistant
Claude Code
.claude/skills/content-calendar-planner/ (or ~/.claude/skills/content-calendar-planner/ for all projects)
GitHub Copilot (VS Code)
.github/skills/content-calendar-planner/
OpenAI Codex
.codex/skills/content-calendar-planner/
Cursor
.cursor/skills/content-calendar-planner/ (or ~/.cursor/skills/content-calendar-planner/ globally)
Compatibility
Any WordPress site. No special plugin required; benefits from read access to the existing post schedule to avoid collisions, works with core scheduled posts or an editorial calendar plugin.
The complete SKILL.md for this skill:
---
name: content-calendar-planner
description: Use when a user has a list of topics and wants them turned into a scheduled publishing calendar. Triggers on "build a content calendar from these topics", "schedule out these posts", or "plan the next month of posts".
---
# Content Calendar Planner
## When to use
A rough list of topics or keywords exists and needs to become a concrete publishing schedule, with dates, slugs, and spacing that avoids clustering similar posts together.
## Procedure
1. Confirm the publishing cadence (posts per week) and the date range to plan for.
2. Check existing scheduled and recently published posts so the new calendar doesn't collide on dates or repeat a topic covered too recently.
3. Group the topic list by theme or similarity, and space same-theme topics apart across the calendar rather than clustering them in the same week.
4. Assign each topic a publish date, a proposed URL slug, and a target keyword, in a simple table format.
5. Flag any topic on the list that's too similar to an already-published post, and suggest either merging it in or sharpening the angle to differentiate.
## Guardrails
- Do not schedule posts automatically; produce the calendar as a proposal for the user to review, since publish timing often depends on factors (launches, promotions) outside the content itself.
- Do not cluster multiple posts on closely related topics within the same week just to fill the calendar; spacing them out serves readers and SEO better than a topic pile-up.