agentsclimarketplace

Creator content calendar

Skill SkillMedev/skills/skills/creator-content-calendar

The open Skill Me catalog — every hosted skill as a portable, MIT-licensed SKILL.md

Install
npx -y skills add SkillMedev/skills --skill creator-content-calendar

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Designs a sustainable publishing system for a solo creator - 3-4 content pillars, a cadence set at the creator's consistent floor, a fixed pillar rotation, a 30-day idea bank, and a monthly audit loop - delivered as a weekly calendar skeleton. Use when someone says "help me plan my content", "I keep falling off my posting schedule", "I'm launching a channel, what should my cadence be", or "audit my stalled content strategy". Do NOT use for a brand or social team's multi-platform posting grid with per-channel cadences and campaign dates - use social-content-calendar instead; do NOT use to fan one finished pillar piece into derivatives - use content-repurposing instead; do NOT use to write the individual posts or scripts - use youtube-script-writer or linkedin-post-writer instead.

SKILL.md

7.3 KB, as published. Nobody here has run it

Creator Content Calendar

A content calendar is a sustainability tool, not an idea list. Its job is to prevent decision fatigue, guarantee pillar balance, and make consistency achievable at the creator's real energy level - because the channel-killer is not bad content, it is the boom-bust cycle where an ambitious schedule collapses after three weeks and the creator disappears for two months. This skill produces a calendar structure the creator can hold through their worst week.

Operating procedure

Run in order: cadence decisions made before pillars exist produce a schedule with nothing to fill it, and idea banks built before pillars produce ideas with no home.

Step 1: gather inputs

  1. Real weekly hours available for content, on a bad week - not an inspired one. This is the binding constraint.
  2. Fixed constraints: job, family, travel rhythm, energy patterns (batch filmer vs. daily writer).
  3. Primary channel and format (the calendar is single-creator; multi-channel derivatives come from repurposing, not extra slots).
  4. Current output history: what they actually shipped in the last 8 weeks, not what they intended. Label any estimate a guess.
  5. Goal per pillar if known (growth, trust, sales); default to growth.

Step 2: define three to four content pillars

A pillar is not a topic; it is a content type with a predictable format and audience expectation. The standard four: Tutorial (how-to, educational), Story (experience, case study), Opinion (take, commentary), Showcase (product, result, before/after). Every piece of content must map to exactly one pillar. Hard rule: more than four pillars means no pillars - collapse until at most four remain.

Step 3: set cadence at the consistent floor

Cadence is set by the creator's floor, not their best-week ceiling: if they can produce two pieces per week every week without exception, the cadence is two per week - even if they occasionally could do five. The right cadence is the one that survives a bad week. Proven sustainable structures:

  • One long-form per week + 2-3 short-form repurposes of it.
  • One long-form every two weeks + daily short-form.
  • Three mid-form pieces per week, no short-form.

If stated ambition exceeds the 8-week shipping history by more than 50%, set the calendar to history plus one piece, and let them earn the raise after four consistent weeks.

Step 4: rotate pillars on a fixed schedule

Assign pillars to slots so "what do I post today" is never a question. A four-pillar channel publishing twice weekly runs a two-week rotation: week one covers pillars one and two; week two covers pillars three and four - every pillar gets coverage monthly by construction. Theme weeks (one topic across all pillars) layer on top for launches or seasonal moments, without breaking the rotation underneath.

Step 5: build the 30-day idea bank

Before the calendar goes live, generate 8-10 specific ideas per pillar. The bank kills the blank-page problem and enables batching - filming or writing multiple pieces in one session - which is the single biggest lever for consistency. Operating rule: the creator is never fewer than 30 days ahead on ideation (not production).

Step 6: install the monthly audit

A 20-minute audit every month: what published, what did not, and why. Track exactly one metric per pillar (views, shares, or replies - whichever matches that pillar's goal) to find which pillar grows the audience fastest. Adjust pillar weight quarterly, on data, not preference. A missed post is not a failure; it is a cadence recalibration signal - if two posts slip in a month, the floor was set too high, so lower the cadence rather than shame the creator toward quitting.

Weekly calendar skeleton

Copy and fill. Example rotation: 4 pillars, 2 posts/week, two-week cycle.

CREATOR: [FILL]   CADENCE: [FILL: n]/week (floor-verified)   HOURS/WK: [FILL]
PILLARS: 1.[FILL: e.g. Tutorial] 2.[FILL: Story] 3.[FILL: Opinion] 4.[FILL: Showcase]

WEEK A
  Slot 1 - [FILL: day]  | Pillar 1 | Idea: [FILL from bank] | Batch day: [FILL]
  Slot 2 - [FILL: day]  | Pillar 2 | Idea: [FILL from bank] | Batch day: [FILL]
WEEK B
  Slot 1 - [FILL: day]  | Pillar 3 | Idea: [FILL from bank] | Batch day: [FILL]
  Slot 2 - [FILL: day]  | Pillar 4 | Idea: [FILL from bank] | Batch day: [FILL]
(rotation repeats: A, B, A, B…)

IDEA BANK (8-10 per pillar before launch)
  Pillar 1: [FILL x8-10]   Pillar 2: [FILL x8-10]
  Pillar 3: [FILL x8-10]   Pillar 4: [FILL x8-10]

MONTHLY AUDIT (20 min, [FILL: recurring date])
  Shipped vs planned: ____/____   Slipped because: [FILL]
  Pillar metrics - P1 [FILL metric]: __  P2: __  P3: __  P4: __
  Fastest-growing pillar: ____   Quarterly weight change (data only): [FILL]

Detail-plan only the next four weeks; week five onward stays as bare pillar slots, because over-planning is the other way calendars die.

Deliverable

Produce a calendar system containing: the 3-4 named pillars with format and audience expectation each, the floor-verified cadence with its justification, the fixed rotation mapped onto the weekly skeleton, a launched 30-day idea bank (8-10 ideas per pillar), and the monthly audit template with one metric assigned per pillar.

Do NOT

  • Do not build the calendar around an ideal scenario; build around the job, family, and energy constraints stated in Step 1 - an aspirational calendar is a quitting plan with dates on it.
  • Do not allow more than four pillars; a channel that is about everything is discovered for nothing.
  • Do not set cadence from a motivated week; the ceiling always collapses, and the collapse costs more than the extra posts gained.
  • Do not detail-plan beyond four weeks out; leave week five onward as pillar slots only.
  • Do not fill slots with ideas that map to no pillar - that is how calendars drift back into random posting.
  • Do not treat a missed post as failure; treat two misses in a month as a signal to lower the floor.

Quality bar

  • Every slot in the skeleton maps to exactly one pillar, and every pillar appears at least monthly by construction.
  • The cadence is defensible against the creator's worst realistic week and their actual 8-week history.
  • The idea bank holds 8-10 ideas per pillar before the calendar starts.
  • The audit has a date, a 20-minute scope, and one named metric per pillar.
  • The creator could execute the next four weeks without making a single "what should I post" decision.

For a brand or team running multiple channels with campaign dates and per-channel cadences, route to social-content-calendar. Once a pillar piece ships, content-repurposing fills the short-form slots from it.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.