agentleFS
BenPremBenPrem/business-brain/.claude/skills/content-calendar/SKILL.md

content-calendar

Skill1 starsChanged 3 months agoMITView on GitHub

Plan and manage a content calendar for your business or a client. Use when the operator says 'content calendar', 'what should I post', 'plan this month's content', or asks about posting schedules. Handles SCHEDULING and POST PLANNING only — assumes a strategy exists (run content-strategy first if not); for writing the actual posts use content-repurposer or social-media-manager. Execution tasks live in <TASK SYSTEM>.

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use campaign-brief, x-writer and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • DanderlionJerSkill

    campaign-brief

    Generate comprehensive campaign brief from strategy notes and goals

    Also in 3 projects that use this

  • stevenflanagan1Skill

    x-writer

    X/Twitter Content Specialist. Writes X-native posts — hooks, threads, and standalone tweets optimised for the platform. Strictly enforces the 280 character limit with a count on every post. Supports standalone tweets and X threads (1/ format). Reads brand-style.md and content-calendar.md. Optional X trend research via Tasty Content MCP. Output to outputs/x/.

    Also in 3 projects that use this

  • stevenflanagan1Skill

    linkedin-writer

    LinkedIn Content Specialist. Writes LinkedIn-native posts for SMB clients — first-person, professional-but-human, built for LinkedIn's format and algorithm. Not adapted captions: posts written from first principles for the platform. Reads brand-style.md and content-calendar.md. Flags posts that would benefit from a Blotato infographic. Output to outputs/linkedin/.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No content strategy exists for this account yet → run content-strategy FIRST.

    line 12
  2. Distinctive:

    Every account needs 3-5 recurring themes — they prevent "what do I post?" paralysis.

    line 38
  3. Distinctive:

    Create one <TASK SYSTEM> task per calendar item:

    line 82

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Content Calendar

Plan what to post, when, and where — tied to business goals, not random inspiration.

Routing

  • No content strategy exists for this account yet → run content-strategy FIRST. The calendar is the execution layer; it needs pillars, audience, and tone to build from.
  • Writing the actual posts → content-repurposer (from source material) or social-media-manager (from scratch)
  • Auditing an existing social presence → social-media-auditor
  • The daily-brief session kickoff may flag "content planning" as today's priority — that lands here.

Step 1 — Gather inputs

Ask the operator:

  1. Who is this for? (own business or a specific client)
  2. Time period? (this week, next 2 weeks, this month)
  3. Platforms? (LinkedIn, X/Twitter, Instagram, Facebook, newsletter, blog — active ones only)
  4. Upcoming events or launches? (new service, case study, local event, seasonal tie-in)
  5. Existing content to repurpose? (blog posts, videos, call transcripts)

Then read the account's strategy doc and, for client work, clients/<client-slug>/brand/brand.md.


Step 2 — Confirm the content pillars

Every account needs 3-5 recurring themes — they prevent "what do I post?" paralysis. Pull them from the strategy doc. Typical service-business pattern:

  1. Expertise / educational — tactical tips in their domain (positions them as the expert)
  2. Customer stories / results — before/after, testimonials (social proof)
  3. Behind the scenes — team, process, lessons learned (trust)
  4. Industry or local insights — market trends, local observations (authority)
  5. Direct offers / CTAs — use sparingly, max 20% of posts

Step 3 — Build the calendar

Posting cadence baseline

PlatformMinimumIdealGood default slots (local time)
LinkedIn2/week3-4/weekTue-Thu, 8-10am
X/Twitter3/weekDailyTue+Thu threads, daily singles
Instagram2/week3-4/weekTue-Thu, 11am-1pm
Facebook2/week3/weekWed-Fri, 1-3pm
Newsletter1/bi-weekly1/weekFriday morning
Blog2/month4/monthMonday publish

Calendar format

One row per post:

| Date | Platform | Pillar | Topic | Format | CTA | Status |
|------|----------|--------|-------|--------|-----|--------|
| Mar 18 | LinkedIn | Educational | "3 things your website is missing" | Text post | Follow for more | Draft |
| Mar 18 | X/Twitter | Educational | Same topic, thread format | Thread (5 tweets) | Bookmark | Draft |
| Mar 19 | Facebook | Customer story | Recent project spotlight | Text + image | Request a quote | Idea |

Formats: text post, thread, carousel, video script, story, reel script, poll, newsletter, blog post. Status flow: Idea → Draft → Review → Scheduled → Posted.


Step 4 — Log to the task system

Create one <TASK SYSTEM> task per calendar item:

  • Task: "[Platform] — [topic short title]"
  • Due date: scheduled post date
  • Notes: pillar, format, CTA, any source material to repurpose

Optionally save the calendar brief to clients/<client-slug>/deliverables/content/ (or your own venture's content folder).


Step 5 — Present the plan

Content Calendar — [Who] — [Period]
====================================
WEEK OF [DATE]:
  Mon: [Platform] — [Topic] — [Format]
  Tue: [Platform] — [Topic] — [Format]
  ...
  Fri: [Newsletter] — [Topic]

Pillar distribution: Educational 3 · Customer story 1 · BTS 2 · Local insight 1
Logged [X] tasks to <TASK SYSTEM>.

Ready to write? Run content-repurposer or social-media-manager on any of these.

Step 6 — Flag repurposing chains

Mark calendar items that can share source material — this is where content-repurposer takes over:

REPURPOSE CHAIN:
  Blog post "3 Website Mistakes" (Mon)
    → LinkedIn post (Tue) — key insight standalone
    → X thread (Tue) — expanded with examples
    → Newsletter block (Fri) — personal angle + CTA
  = 4 pieces from 1 idea

Monthly review

At month end (or "how did content do?"):

  • Review which posts got the most engagement (operator provides platform data)
  • Identify the best-performing pillars
  • Lean next month's calendar into what's working; cut what isn't
  • Route durable lessons into the strategy doc so they survive between sessions

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.