Claude Skill A Claude Skill that takes pillars, cadence, and team capacity, and outputs a 90-day editorial calendar with named owners and slip rules.

Content Calendar Generator Claude Skill

Content Calendar Generator is a free Claude Skill that turns three inputs, your content pillars, your per-format cadence, and your named team capacity, into a 90-day editorial calendar. Every slot carries a named owner, a format, a pillar, a brief deadline, a draft deadline, and a publish date. The slip rules ship inside the output.

The Skill file states its own premise in its first line: most content calendars are wishlists. A plan written without capacity in view promises work nobody has hours for, and the misses begin in week two. This page covers what the Skill does, what a slip rule is, what a generated calendar looks like, and the requests it refuses.

What does the Content Calendar Generator skill do?

It builds one 90-day calendar from your real constraints, in four steps, and stops there.

  • Step 1, inputs. You supply pillars, per-format cadence, and named team capacity. The Skill asks for each one explicitly, and the file bars it from proceeding on placeholders: a missing input comes back as a question.
  • Step 2, balance. It works the constraints against each other: pillars rotate, formats stagger, every owner stays inside the capacity you stated, and nobody gets double-booked. Anything that cannot be balanced is surfaced as a flag, and the Skill waits for your confirmation before going on.
  • Step 3, schedule. It drafts the 90 days, each slot holding the owner, format, pillar, and all three dates. The output structure is fixed, and every required section has to be present and non-empty.
  • Step 4, guardrails. The calendar arrives with its slip rules attached: what triggers a kill, what triggers a re-shuffle, what triggers escalation.

The return is a markdown table, one row per slot with slug, format, pillar, owner, and the three dates, plus an explicit slip rules section.

What is a slip rule?

A slip rule is a decision made in advance about what happens when a slot misses its deadline. Instead of renegotiating the plan at every miss, the calendar names its three outcomes up front: a kill removes the piece, a re-shuffle moves it and shifts what depends on it, and an escalation sends the pattern to a human.

This is the part of the output most calendars lack. A schedule that only records intentions gets quietly rewritten at the first late draft, and after the second rewrite nobody trusts the dates. Written triggers turn a slipped deadline from a negotiation into a lookup.

What does a generated calendar look like?

Here is a sample built to the Skill’s own output format. The pillars, names, slugs, and dates are ours, invented for the illustration; the column set and the rules the rows obey come from the Skill file.

Say you give it two pillars (content operations, AI workflows), a cadence of one blog post a week plus a fortnightly newsletter, and three named people: Maya with capacity for two pieces a month, Sam and Priya with one each. The opening rows come back shaped like this:

SlugFormatPillarOwnerBrief deadlineDraft deadlinePublish date
content-ops-auditBlog postContent operationsMayaMar 2Mar 9Mar 16
ai-draft-review-loopBlog postAI workflowsSamMar 9Mar 16Mar 23
issue-12-capacityNewsletterContent operationsPriyaMar 16Mar 20Mar 27
prompt-library-basicsBlog postAI workflowsMayaMar 18Mar 25Apr 1

Each row traces to a hard rule. Every slot has a named owner, because the Skill never schedules a piece without one. The pillar column alternates, because it never schedules the same pillar two slots in a row. Maya appears twice inside her stated two-a-month capacity, never on overlapping deadlines, because it never overcommits a single writer. Below the table sits the slip rules section, with thresholds you confirm (these too are invented examples): a draft three days late with no revised date re-shuffles, a slot that re-shuffles twice is killed, an owner slipping twice in a month escalates. The sample passes the checks a table can show: no em dashes, no invented statistics, and the structure complete. A calendar that fails that self-check does not get handed back.

What will it refuse to do?

The refusals are written into the SKILL.md as hard rules, and they are what makes the output trustworthy rather than merely tidy.

  • It never schedules a piece without a named owner. An unowned slot is a wish, and the file bans it outright.
  • It never overcommits a single writer. Capacity you stated in step 1 is a ceiling, whatever the cadence asks for.
  • It never runs the same pillar two slots in a row. Rotation is enforced, so one topic cannot quietly swallow a month.
  • It will not invent an input. Missing pillars, cadence, or capacity produce a question back to you, and placeholders are barred.
  • It will not proceed past a flag. When the balancing step finds a conflict, it surfaces the flag and waits for your confirmation.
  • It will not return a calendar that fails its own self-check, and it writes no invented statistics or citations anywhere in the output.
  • It stops at the calendar. Push it past that scope, say by asking it to draft the pieces it just scheduled, and it declines, pointing you at the Skill in the series that owns the job.

How do you install the Content Calendar Generator skill?

Drop the SKILL.md into your Claude Code skills folder and the install is done; from there you call it by name. There is no server behind it and no account to create.

  1. Save the SKILL.md file to ~/.claude/skills/content-calendar-generator/SKILL.md on your machine.
  2. In Claude Code, invoke /content-calendar-generator. It asks for your pillars, cadence, and team capacity before it schedules anything.
  3. Confirm any flags it raises, then paste the returned calendar wherever your team plans.

The skills hub carries the general install guide for the whole series.

Who is this Skill for?

Teams whose schedule lives in a spreadsheet and in somebody’s head, and the two disagree.

  • A head of content who plans a quarter in one afternoon and watches the plan come apart by week three.
  • A production lead who spends part of every Monday arbitrating whose deadline moves.
  • A solo marketer running the whole calendar from Claude Code, where the capacity input is one person.
  • Any team that would rather have scheduling decided by written rules than by whoever asks loudest.

What’s in the bundle?

Four items, one of them behind an email form.

  • SKILL.md (raw): the full Claude Code Skill file, ready to drop into ~/.claude/skills/content-calendar-generator/.
  • One-pager PDF: a printable summary of the 4-step process, the output format, and the install steps.
  • Google Doc (gated): a Drive-resident copy plus install notes. Submit your email to access; we also tag you for the Claude Skills for content operations email sequence so you hear when the next Skill lands.
  • Card image: the hero image, sized to repost wherever you share the Skill.

Why we built it

The calendar is the artifact every content disagreement eventually lands on: what ships, who owns it, which date moves. Putting the balancing and slip rules into a file means that argument happens once, at setup, and the schedule follows them from then on, whoever runs the planning.

Content Calendar Generator is Skill 9 of 10 in Relato’s Claude Skills for content operations series, which covers the content lifecycle from brief through refresh.

It stops at the calendar. Each slot’s brief is drafted via the Brief Drafter Skill, number 1 in the series, and drafts stay with your writer pool.

Frequently asked questions

What is a Claude Skill?

A SKILL.md file that Claude Code reads when you call it by name. The frontmatter declares what the Skill is for, the body carries its steps and hard rules, and installing one means saving that single file into your skills folder.

Do I need a paid Claude plan to use this?

The Skill itself is a free markdown file under an MIT license. It runs inside Claude Code, which is the one thing you need.

What happens if I cannot state my team’s capacity yet?

The Skill asks for it and waits. The file bars it from scheduling on placeholders or inventing an input, so a run without capacity comes back as a question rather than a calendar built on guesses.

Can I change the balancing or slip rules?

Yes. The Skill file is plain markdown, MIT licensed. Rewrite the hard rules section to match how your team actually arbitrates, and every calendar after that follows your version.

Does it draft the scheduled pieces too?

No. The calendar is where it stops, by rule, and a request to draft gets declined with a pointer to the series Skill built for that step. Keeping scheduling and drafting separate is what keeps each one reviewable.

Will more Skills follow?

Content Calendar Generator is Skill 9 of ten, and the series’ final step is already live: the Refresh Queue Builder, Skill 10, ranks which published posts to refresh next. Submit your email above and the series emails reach you as each release lands.

Ready to streamline your content operations?

Start your free trial and see the difference.