Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@contentstudio

Content calendar

@contentstudio/content-calendar

Plan a few weeks of content across LinkedIn, a newsletter, a blog, and more. A script lays out dated slots per channel with your content pillars rotated evenly, then Claude fills in specific topics and hooks you can actually write. Exports a CSV for your sheet or planner.

SkillContentv1.0.0 (latest)Tested
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1---
  2. 2name: content-calendar
  3. 3description: Plan a content calendar for the next few weeks across channels (LinkedIn, newsletter, blog, X, Instagram, YouTube, podcast). A script lays out dated slots with content pillars rotated evenly; Claude then fills each slot with a specific topic and hook, and exports a CSV for a spreadsheet or planner. Use when the user says "plan our content", "content calendar", "what should we post this month?", "editorial calendar", or "posting schedule".
  4. 4license: MIT
  5. 5---
  6. 6
  7. 7# Content calendar
  8. 8
  9. 9Most content calendars fail in one of two ways: a grid of empty boxes, or a list of vague themes ("thought leadership"). This one gets the structure right with a script (dates, channels, an even pillar mix) and then fills every slot with a topic specific enough to start writing today.
  10. 10
  11. 11## When to use
  12. 12
  13. 13- Planning the next 2 to 8 weeks of posts, newsletters, or articles.
  14. 14- "What should we post this month?", "build our content calendar", "plan LinkedIn for Q1".
  15. 15- To turn one big piece into many, use `repurpose-long-form` and slot the results in here.
  16. 16
  17. 17## Inputs
  18. 18
  19. 19Ask in one message, with these defaults:
  20. 20
  21. 211. **Start date** (next Monday) and **weeks** (4).
  22. 222. **Channels and days.** Default: LinkedIn Mon, Wed, Fri; newsletter Thu; blog Tue. Fewer channels done well beats many done badly. Suggest cutting if the team is one person and they ask for more than 4 pieces a week.
  23. 233. **Pillars:** 3 to 4 recurring themes (default: Product tips, Customer stories, Behind the scenes). Good pillars map to what the audience wants, not to departments.
  24. 244. **Audience** in one line, and **what is coming up:** launches, events, holidays, dates to skip.
  25. 255. **Raw material:** existing posts, docs, customer quotes, or notes in `content/`. Read them; good topics come from here.
  26. 266. **Voice:** follow `brand.md` if it exists.
  27. 27
  28. 28## Steps
  29. 29
  30. 301. **Lay out the slots.**
  31. 31
  32. 32 ```bash
  33. 33 node scripts/calendar.mjs content/calendar --start 2026-11-09 --weeks 4 --cadence "linkedin:mon,wed,fri newsletter:thu blog:tue" --pillars "Product tips,Customer stories,Behind the scenes" --skip 2026-11-26
  34. 34 ```
  35. 35
  36. 36 It writes `content-calendar.csv`, `.md`, and `.json` in `content/calendar/`. It will not overwrite an existing calendar; pass `--name december` for a new one, or `--force` only if the user says to replace it.
  37. 372. **Place the fixed moments first:** launches, events, and holidays go in the slots nearest their dates. Put a teaser 3 to 5 days before a launch and a recap after.
  38. 383. **Fill every slot** in the CSV: `topic` (specific, one sentence) and `hook` (the first line a reader sees). Match the pillar and the channel format:
  39. 39 - LinkedIn post: one idea, a story or a lesson, 150 to 250 words.
  40. 40 - Newsletter issue: one main piece plus two short links.
  41. 41 - Blog article: a question people search for, 800 to 1,500 words.
  42. 42 - Thread or carousel: a list of 5 to 8 steps or examples.
  43. 43 Specific beats general: "How one clinic cut no-shows from 18% to 7% with a two-line text" beats "Customer success story".
  44. 444. **Reuse on purpose.** A blog article on Tuesday can feed Wednesday's LinkedIn post and Thursday's newsletter. Note the source in `link`.
  45. 455. **Check the mix:** no pillar twice in a row on the same channel, no more than one promotional piece in five, at least one piece a week that asks the audience a question.
  46. 466. **Update the `.md`** to match the filled CSV and show the first two weeks in chat. Ask what to swap.
  47. 47
  48. 48See `examples/content-calendar-filled.csv` for what a finished week looks like.
  49. 49
  50. 50## Output format
  51. 51
  52. 52```markdown
  53. 53# Content calendar: 2026-11-09 to 2026-12-04
  54. 54
  55. 5520 pieces over 4 weeks. linkedin 12, blog 4, newsletter 4.
  56. 56
  57. 57## Week 1 (from 2026-11-09)
  58. 58| Date | Channel | Format | Pillar | Topic | Hook |
  59. 59| --- | --- | --- | --- | --- | --- |
  60. 60| Mon 2026-11-09 | linkedin | post | Product tips | The 2-line reminder text that halves no-shows | "Most reminder texts are too long. Ours is 2 lines." |
  61. 61```
  62. 62
  63. 63## Guardrails
  64. 64
  65. 65- Never schedule or publish anything. This plans; people post.
  66. 66- Do not invent customer names, results, or quotes for topics. Use `<customer story: need one>` and list what material is missing.
  67. 67- Keep the calendar realistic for the team size the user gave. Say so if the plan is more than they can produce.
  68. 68- Do not overwrite a calendar that has topics filled in.
Sign in to comment on a line