Skip to content

Makes

Content calendar

Turns a playbook chapter, article or theme into a 3-posts-a-week LinkedIn calendar, stops for you to pick topics, and ends with a block you paste into any sheet.

Other tools

Add this skill to Claude

Claude takes skills as a ZIP file. Your download has started; if it didn't, use the button below.

  1. 1In Claude, open Customize, then Skills.
  2. 2Choose +, then Upload a skill, and pick content-calendar.zip.
  3. 3Ask for it by name, or let Claude use it when a task matches.

Skills need code execution turned on in Claude's settings. On a Team or Enterprise plan, an admin can share it with everyone.

Download the folder

Try it now, without installing

See the skill work on a made-up input before you add it. Nothing is installed, and you can swap in your own input.

Open in the Claude app

Opens a new chat in the Claude desktop app with the prompt filled in. Nothing is sent until you press enter.

Includes the whole SKILL.md and the sample input. Paste it into Claude, ChatGPT or any chat.

Influenced by
LinkedIn reach research
Needs
The source · Your pick
Works with
Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md
Version
1.0.0 · Last checked · License MIT
Maintained by
Sabih AhmedContent
SkillContent

Content calendar

Example output

Topics from one chapter
TopicPillarShape
The 4-check auditTrusted figuresAnchor framework
A blank source fieldTacticalSymptom callout
Software can't hear a podcastBoth kinds of truthMyth vs reality

Turns a playbook chapter, article or theme into a 3-posts-a-week LinkedIn calendar, stops for you to pick topics, and ends with a block you paste into any sheet.

The skill

The whole skill, in plain text.

Nothing is hidden. Read it, change it to fit your team, or take the whole folder.

Scripts
Optional Python scripts for the counting. It works without them and says which way it ran.
Network
Doesn't need the internet.

3 test cases

content-calendar/SKILL.md

In the folder

  • content-calendar/SKILL.md
  • content-calendar/references/angles-and-calendar.md
  • content-calendar/references/extraction.md
  • content-calendar/scripts/calendar_balance.py
---name: content-calendardescription: >-  Turns one playbook chapter, article or theme into a LinkedIn posting calendar at 3 posts a week. Reads the source  through an operator lens and a buyer lens, pulls every topic that passes a strict quality bar plus the source's  anchor framework, frames each with a pillar from the messaging house, a buyer role, a post shape and a hook line from  company-profile.md, then stops for the reader to pick topics. After the pick it sequences them under balancing rules  (strategic and tactical mix, shapes, formats, every buyer role each month, no duplicates) and ends with a  tab-separated block that pastes into any sheet. Use it to plan founder or company posts from a source. Not for  writing the posts (use founder-post) or repurposing a finished article into assets (use repurpose).license: MITcompatibility: >-  Works in Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md. Never pushes to a sheet or tool; the  reader pastes the block. Python 3 is optional, for sequencing the calendar.metadata:  author: SHAKEUP  version: "1.0.0"  stage: make  plugin: content  homepage: https://www.shakeuphq.com/skills/content-calendar--- # Content calendar Finds every post worth writing in one source, lets the reader pick, and lays the picks out so no week repeats itself. ## Purpose - One job: from one source, a picked set of framed topics in a balanced calendar.- Stage: make. It ends in its own checks and a fix loop of at most 2 rounds, with one named stop for the pick.- It never invents a topic, a figure or a reaction the source doesn't support, never builds the calendar before the reader picks, and never pushes anything to a sheet or a tool. ## Use when / not | Situation | Use || --- | --- || A playbook chapter, guide section or article should become a month of posts | this skill || A theme already broken into topic ideas needs framing and a calendar | this skill, bare theme source || Picked topics need a calendar (the pick already happened) | this skill, from step 7 || Writing one of the posts | `founder-post`, from the calendar row || Only hooks | `hook-writer` || Posts, an email and scripts from one finished article, placed by channel | `repurpose` | ## Inputs | Input | Required | Ways to provide, in order | If missing || --- | --- | --- | --- || The source: a chapter, an article or a bare theme | yes | a file or URL the agent can read; pasted text; an `article-write` or `repurpose` handoff | ask once; `BLOCKED` without it || The reader's pick | yes, for the calendar | the reader's answer at the checkpoint | stop at `AWAITING PICK` || Start date and posting days | no | the reader; `### Founder voice` > `Posting days` | next Monday; Tuesday, Wednesday, Thursday || The existing calendar | no | rows the reader pastes or exports from their sheet | duplicates checked within this run only; said so || Messaging house, buyers, moments | no | the profile | pillar `tactical` for all, personas from the source; coverage `partial` | ## Profile read From `company-profile.md`: `## Product`, `## Buyers` and `### Buying group`, `## Buying moments`, `## Positioning`, `## Messaging house`, `## Voice` with `### Founder voice`, `## Claims and proof` with `### Never say`, `## Channels`, and every `## Learnings` entry for `content-calendar` and `founder-post`. No profile: ask in one message for the buyer roles, the 2 or 3 messages the company stands for, and what it sells. Say that `company-profile` saves this next time. ## Steps 1. **Apply learnings.** Picks the reader always skips (a `proposal` accepted as a rule) and archetype results (`fact`) shape the framing and the ranking. 2. **Name the source type** (`references/extraction.md`): chapter, article or bare theme. One source per run. 3. **Read through both lenses.** Fill the operator lens and the buyer lens fields, each grounded in a source line or a profile entry, or `none found`. 4. **Extract.** Find the anchor first (and run its headline through the narrative test), then every nugget that passes all 7 points of the quality bar, at most 1 or 2 per named section of the source. Name the exact section each came from. If nothing passes, stop with `NO TOPICS`. 5. **Frame every topic** (`references/angles-and-calendar.md`): core belief, persona, archetype, hook line, why it lands, what it means for the buyer, how we can sell it, motion, channel, format. Framing runs on every topic, not only the likely picks, so the reader picks with the full picture. A forced fit is written as `none found`. 6. **Check the hook lines** before showing them: 18 words or fewer, no bait, no rhetorical question, no dash, a specific in each, and every figure traceable to the source or `## Claims and proof` (`claim-check`, or its test inline). Fix and recheck at most twice (Loop). 7. **Checkpoint.** Show the topic preview (one small table per topic, anchor first) and ask which topics carry forward and whether the anchor is in. Stop: `AWAITING PICK`. 8. **Sequence the picks.** Run:    ```   python3 scripts/calendar_balance.py --input picked.json   ```    Without Python, place topics slot by slot (3 a week) and check each placement against the balancing rules: no more than 2 strategic or 2 tactical in a row, no archetype twice in a week, no more than 1 anchor a week, no more than 2 of a format in a row, arcs back to back in order; then check every persona appears in each 4-week stretch and nothing repeats the existing calendar. Say which way you ran it. A rule the picks can't meet is reported, never forced. 9. **Show the calendar** in the same per-topic table format, then the tab-separated block with every column on every row. ## Check and verdict | Verdict | Condition (first match wins) || --- | --- || `BLOCKED` | No source || `NO TOPICS` | No nugget passes the quality bar: say what the source lacks (a consequence, a case, a figure, a position) || `AWAITING PICK` | Topics are framed and the reader hasn't picked yet || `READY WITH GAPS` | The calendar is built, but a balancing rule couldn't be met, a duplicate was flagged, a persona is missing from a 4-week stretch, or a hook still has an open item || `READY` | The calendar is built and every rule holds | Named stops: `BLOCKED` asks for a source. `AWAITING PICK` is the checkpoint: it stops until the reader picks, on every run, including repeat runs. No other stops. ## Loop 1. Check the hook lines (step 6) and, after sequencing, the balancing rules (step 8).2. Fix: rewrite a failed hook once, changing only what failed; re-sequence once if a rule failed and another order exists.3. Recheck. At most 2 rounds; then hand over with what's still open, labelled. Never fix balance by inventing or splitting a topic. ## Learn Append to `## Learnings` when: - the reader's picks show a pattern across 2 or more runs, such as skipping every tactical topic (a `proposal`);- posts from the calendar come back with results by archetype, pillar or persona (a `fact`, with the source);- the reader changes the cadence or days (a `fact`, and update `### Founder voice` > `Posting days`). Example: `- 2026-10-24 | content-calendar | proposal | Lead each month with a self-check list anchor | Why: anchors in that shape drew the most saves in 3 of 4 months (post analytics, Jun to Sep 2026) | Status: proposed` ## Output At the checkpoint: ```Verdict: AWAITING PICK · Coverage: <complete | partial (no messaging house; no buying moments)>Source: <name, type> · Topics: <n> plus <n> anchor **Anchor. <the framework, in one plain sentence>**| Field | Value |(pulled from, archetype, channel, core belief, motion, why it lands, hook line, what it means for the buyer, how we can sell it) **1. <topic in one plain sentence>**| Field | Value |(repeat per topic) Which topics carry forward (numbers or "all"), and is the anchor in? Start date and days, if not the defaults?``` After the pick: ```Verdict: <READY | READY WITH GAPS> · Sequenced by: <script | hand placement>Cadence: <n> a week, <days>, from <date> **Week 1, <day> <date>: <topic>**| Field | Value |(repeat per post) Rules: <each rule: held | broken at slot n, why> · Persona gaps: <weeks, missing roles, or none> · Duplicates: <topic → match, or none> <tab-separated block in a code fence: header row, then one row per post>Learnings applied: <list, or none>``` Then the handoff block. ## Hand off ```handoffskill: content-calendarversion: 1.0.0verdict: READYcoverage: completefor: <source name>outputs:  posts: 9  weeks: 3  start: <YYYY-MM-DD>  rows: [<week, date, topic, pulled_from, hook>]  anchors: 1next: [founder-post]open: []``` `founder-post` takes one row at a time: it re-reads the source from `pulled_from` and keeps the row's hook word for word. At `AWAITING PICK`, `next` is `[]`. ## Failure modes | Problem | Do this || --- | --- || The source is a sales page or a list of features | Few or no nuggets pass point 6 or 7; say so, return `NO TOPICS` if none || The reader says "pick for me" | Rank the topics (anchor first, then strongest consequence) and show the ranking at the checkpoint; still wait for a yes || A topic is already in the existing calendar | Flag it with the match; the reader decides whether to keep it || The picks are all one persona | Build the calendar, report the gap, and point to the topics at the checkpoint that would fill it || The reader names 3 topics as an arc | Keep them back to back in the order problem, reframe, proof, and tag each with its role || A figure in a hook has no source | Take the figure out of the hook; keep the topic | ## Influenced by - Richard van der Blom's research on LinkedIn reach, which found the best posting frequency has dropped to 2 to 4 posts a week: https://creatorscience.com/podcast/richard-van-der-blom-2/- SHAKEUP's social pipeline: an operator lens and a buyer lens on the same source, a strict quality bar for what counts as a topic, an anchor per chapter held to a narrative test, framing on every topic before the pick, and a paste-ready block instead of a push.

How it thinks

Inputs in, a verdict out, and a stop only where you decide.

What we built

Our social pipeline reads each chapter through the founder's eyes and the buyer's, and holds every topic to a bar of its own. It frames every topic before the pick and hands over a block to paste, not a push into a tool.

It reads your company profile if you have one, or asks for only what it needs. Then it works through its steps, checks its own work and ends in a verdict.

The steps

  1. 01

    Read the source 2 ways

    As the founder would, for the contrarian angle, the gap between theory and practice and the proof. Then as a skeptical buyer would, for the pain, the doubt and the line that stops the scroll.

  2. 02

    Pull the topics

    The anchor framework comes first, then every topic that passes a strict bar. It must be in the source, state what it costs the buyer, and be something only a practitioner could say.

  3. 03

    Frame every topic

    A message pillar or tactical, a buyer role, a post shape, a hook line, why it lands and how your product answers it. Every topic is framed, so you pick with the full picture.

  4. 04

    Stop for your pick

    Each topic shows as a small table you can read in a minute, anchor first. Nothing is scheduled until you choose.

  5. 05

    Balance the calendar

    Its script orders your picks so no week repeats a post shape. No more than 2 strategic or tactical posts run in a row, and every buyer role appears each month.

  6. 06

    Give you a block to paste

    A tab-separated block with every column on every row, which splits into columns when you paste it into any sheet. It never pushes anywhere itself.

What you need

  • Required

    The source

    A chapter, article or theme your agent can read → Text you paste → An article write or repurpose handoff

  • Required

    Your pick

    Your answer at the checkpoint

  • Optional

    Start date and posting days

    Your answer → The posting days in your founder's voice

  • Optional

    Your existing calendar

    Rows you paste or export from your sheet

What it can return

  • AWAITING PICK

    Topics are framed and it's waiting for your choice.

  • READY

    The calendar is built and every balancing rule holds.

  • READY WITH GAPS

    The calendar is built, but a rule couldn't be met, a duplicate was flagged or a buyer role is missing for a month.

  • NO TOPICS

    Nothing in the source passes the bar. It says what the source lacks.

  • BLOCKED

    There's no source.

Where it stops for you

  • At the checkpoint, every run, until you pick the topics

Example output

What you get back.

A run for a made-up company. Your output depends on your inputs.

Here's a run for a made-up B2B SaaS company that sells attribution software, after the reader picked 6 topics from a playbook chapter.

Verdict

READY WITH GAPS

Sequenced by script

3 a week, Tuesday to Thursday, from 3 November

WeekDayTopicShapeRole
1TueThe 4-check audit before a board meetingAnchor frameworkHead of demand gen
1WedA blank source field hides a channelSymptom calloutHead of demand gen
1ThuSoftware can't hear a podcastMyth vs realityHead of demand gen
2TueMap stages on day 1Process revealHead of demand gen
2WedCost per opportunity in a budget reviewMetric reframeHead of demand gen
2ThuRewriting stages costs RevOps' trustTeardownHead of demand gen
Gaps

the podcast topic repeats a row already in the sheet from October. The CMO, RevOps and finance roles are missing for the month.

The handoff block the next skill reads
skill: content-calendar
version: 1.0.0
verdict: READY WITH GAPS
coverage: complete
for: chapter 4, the board-ready attribution audit
outputs:
  posts: 6
  weeks: 2
  start: 2026-11-03
next: [founder-post]
open: [keep or replace the duplicate podcast topic, add a topic for the CMO]

What good looks like

  • Every topic names the exact section of the source it came from
  • One anchor topic, shown first
  • A stop for your pick before any dates appear
  • No post shape twice in a week, and every buyer role each month
  • Duplicates flagged, never dropped quietly

Install

Use it in the tool you already have.

Pick your tool. Each tab has the shortest path we know of.

  1. 01
  2. 02
    In Claude, open Customize, then Skills.
  3. 03
    Choose +, then Upload a skill, and pick the ZIP. Code execution must be on in your settings.
  4. 04
    Ask for it by name, or let Claude use it when a task matches.

Questions

Before you add it.

Why 3 posts a week?

It sits inside the 2 to 4 posts a week that recent research on the platform finds works for most creators. Change it if the founder's own figures say otherwise.

Can it pick the topics for me?

It ranks them for you, anchor first, then by the sharpest cost to the buyer. The final yes stays with you, because the founder has to want to post them.

Does it work with our sheet?

Yes. The block at the end is tab-separated, so it splits into columns in any spreadsheet when you paste it. Nothing is sent anywhere.