Content Calendar

Plan, schedule, and track content across channels — newsletters, social media, blog posts, and videos. Manages pipeline stages, publishing cadence, and repur...

Clawdssen

@clawdssen

What This Skill Does

A structured content pipeline system that tracks pieces from idea through draft, review, scheduled, and published stages across multiple channels like newsletters, blogs, and social media. It surfaces overdue items, scheduling gaps, and repurposing opportunities.

Replaces chaotic spreadsheets and manual tracking by giving your agent a repeatable system to manage the full content lifecycle and flag what needs attention.

When to Use It

  • Plan a weekly content calendar across newsletter, blog, and social channels
  • Identify pieces stuck in Draft for more than 7 days and move them forward
  • Surface repurposing opportunities from published content for new channels
  • Generate a weekly content brief summarizing the next 7 days of publishing
  • Track publishing cadence and flag when a channel is falling behind schedule
  • Review the content backlog and select 2-3 ideas worth developing this week

Install

$ openclaw skills install @clawdssen/content-calendar

Content Calendar

By The Agent Ledgertheagentledger.com

Plan, schedule, and track your content pipeline across every channel — without the spreadsheet chaos. This skill gives your agent a structured system for managing content from idea to published, and flagging what's falling behind.


What This Skill Does

Your agent will:

  • Maintain a content pipeline organized by stage (Idea → Draft → Review → Scheduled → Published)
  • Track publishing cadence per channel (newsletter, blog, LinkedIn, X, etc.)
  • Surface what needs attention — overdue pieces, gaps in the schedule, idle ideas
  • Flag repurposing opportunities — where existing content can be adapted for new channels
  • Provide a weekly content brief summarizing the next 7 days

Setup (5 Steps)

Step 1: Create your content workspace

Create a file called content/CALENDAR.md in your agent workspace. Paste this starter template:

# Content Calendar

_Last updated: [date]_

## Active Pipeline

| ID | Title | Type | Channel | Stage | Due Date | Notes |
|----|-------|------|---------|-------|----------|-------|
| C001 | | | | Idea | | |

## Publishing Cadence

| Channel | Frequency | Day/Time | Status |
|---------|-----------|----------|--------|
| Newsletter | Weekly | Thursday | Active |
| Blog | Bi-weekly | Monday | Active |
| LinkedIn | 3x/week | Mon/Wed/Fri | Active |
| X/Twitter | Daily | 9am | Active |

## Content Backlog (Unscheduled Ideas)

- [ ] [idea title] — [brief description]

## Published Archive

_Completed pieces move here after publishing._

Step 2: Define your channels

Edit the Publishing Cadence table above to match your actual channels. Remove what you don't use. Add what's missing. Be honest about cadence — if you realistically post once a week, put that.

Step 3: Tell your agent about content types

Add a note at the top of CALENDAR.md listing your content types and typical word counts or formats:

## Content Types
- **Newsletter** — ~800 words, personal tone, one main idea + links
- **Blog Post** — 1,200–2,000 words, SEO-focused, structured headers
- **LinkedIn Post** — 150–300 words, story format, one insight
- **X Thread** — 5–10 tweets, hook + value + CTA
- **YouTube Script** — 800–1,500 words, conversational

Step 4: Create the content folder structure

content/
├── CALENDAR.md          ← pipeline overview (this file)
├── ideas/               ← rough idea notes
├── drafts/              ← in-progress pieces
├── published/           ← archive of completed work
└── repurpose/           ← repurposing queue

Your agent will reference this structure when looking for content to work on.

Step 5: Activate the skill

Tell your agent:

"Read the content-calendar skill and set up my content system. Use the files in content/."

Or trigger it via heartbeat by adding to HEARTBEAT.md:

## Content Calendar (every Monday)
- Review content/CALENDAR.md
- Flag anything due this week
- Surface 2-3 backlog ideas worth developing
- Check for pieces stuck in Draft >7 days

Pipeline Stages

Each piece of content moves through these stages:

StageDescriptionTypical Duration
IdeaJust a title/concept, not startedIndefinite
OutlineStructure exists, no full draft1–3 days
DraftFull draft exists, not reviewed1–5 days
ReviewReady for final edits/approval1–2 days
ScheduledWritten, set to publish on a dateDone
PublishedLive — move to archiveArchive

Stall flag: Any piece in Draft or Review for >7 days gets flagged in status reports.


Weekly Content Brief Format

When asked for a content brief, your agent will produce:

CONTENT BRIEF — Week of [date]

PUBLISHING THIS WEEK
━━━━━━━━━━━━━━━━━━━
• [Day] — [Channel]: [Title] (Stage: Scheduled ✅)
• [Day] — [Channel]: [Title] (Stage: Draft — needs ~2h to finish ⚠️)

OVERDUE / AT RISK
━━━━━━━━━━━━━━━━
• [Title] — [Channel] — was due [date], stuck in [Stage] for [X] days
  → Recommended action: [complete / reschedule / cut]

SCHEDULE GAPS
━━━━━━━━━━━━
• [Channel] has no content scheduled for [date range]
  → Backlog options: [list 2-3 relevant ideas]

REPURPOSE OPPORTUNITIES
━━━━━━━━━━━━━━━━━━━━━━
• "[Title]" (published [date]) → could become [format] for [channel]

NEXT WEEK PREVIEW
━━━━━━━━━━━━━━━━
• [Channel]: [Title] (Stage: Outline — on track)
• [Channel]: [TBD — needs idea]

RECOMMENDED ACTION TODAY
━━━━━━━━━━━━━━━━━━━━━━━
1. [Most urgent thing]
2. [Second thing]
3. [Third thing]

Repurposing Tracker

Good content does more than one job. Tell your agent to check for repurposing opportunities by looking at anything published in the last 60 days:

Common repurposing patterns:

  • Newsletter issue → LinkedIn post (pull the main insight)
  • Blog post → X thread (break into 5-8 key points)
  • Long blog → Short blog (split into 2 pieces)
  • Video script → Blog post (light reformatting)
  • Newsletter → Blog post (add SEO metadata and headers)

To flag a piece for repurposing, add a row in content/repurpose/queue.md:

| Original | Original Channel | Repurpose As | Target Channel | Status |
|----------|-----------------|--------------|----------------|--------|
| [Title] | Newsletter | Thread | X/Twitter | Todo |

Content Idea Capture

Drop rough ideas into content/ideas/ as simple text files. Naming convention:

[topic-slug].md

Minimum viable idea note:

# [Idea Title]

**Angle:** [One sentence on the specific take]
**Channel:** [Best fit channel]
**Why now:** [Why this is relevant/timely]
**Hook:** [Draft hook if you have one]
**Related:** [Links to existing content it connects to]

Your agent can help expand ideas into outlines on request.


Customization Options

Change the stall threshold

Default is 7 days. To adjust, add to CALENDAR.md:

## Settings
- Stall threshold: 5 days
- Overdue warning: 2 days before due date

Topic clusters

Group your content by theme to ensure balanced coverage:

## Topic Clusters
- Business Systems (40%)
- AI / Automation (30%)
- Personal Productivity (20%)
- Industry News (10%)

Your agent will flag if any cluster is underrepresented over a rolling 4-week period.

Seasonal content flags

Mark pieces as time-sensitive:

| ID | Title | ... | Notes |
|----|-------|-----|-------|
| C012 | Year-end recap | ... | ⏰ SEASONAL: must publish Dec 28-30 |

Minimum viable cadence mode

If you're overwhelmed, tell your agent:

"Switch content calendar to minimum viable cadence."

It will prioritize your single highest-traffic channel and flag everything else as optional.


Integration with Other Agent Ledger Skills

SkillIntegration
Daily BriefingInclude "Content due today" in morning briefing
Project TrackerContent launches tracked as projects (e.g., "Issue #5")
Solopreneur AssistantContent calendar reviewed in weekly business review
Research AssistantResearch briefs feed directly into content ideas
Inbox TriageReader replies/feedback captured for content improvement

Troubleshooting

"My calendar is getting out of date" Add a heartbeat check. Weekly is usually right for most creators. Daily if you publish daily.

"Too many ideas, can't prioritize" Use the scoring rubric in references/advanced-patterns.md to rank ideas by effort vs. impact.

"I keep missing my publishing schedule" Run a cadence audit: count how many pieces you actually published in the last 30 days vs. how many you planned. Adjust your cadence table to match reality, not aspirations. A realistic cadence beats an optimistic one every time.

"Agent keeps forgetting what I've published" Move published pieces to content/published/ and update the archive section of CALENDAR.md. Periodically tell your agent: "Update the content archive from the published folder."

"I want to track performance metrics" This skill tracks pipeline, not analytics. For performance data, track metrics manually in a content/published/[slug]-metrics.md file and reference them in repurposing decisions.


Triggers

This skill activates when you say things like:

  • "What content do I have due this week?"
  • "Give me a content brief"
  • "What's in my content pipeline?"
  • "I have a new content idea: [idea]"
  • "What content is overdue?"
  • "What can I repurpose from last month?"
  • "Review my content calendar"

Content Calendar — by The Agent Ledger Subscribe at theagentledger.com for new skills and the weekly newsletter on building AI-powered systems. License: CC-BY-NC-4.0

DISCLAIMER: This skill was created by an AI agent. It is provided "as is" for informational and educational purposes only. It does not constitute professional, financial, legal, or technical advice. Review all generated files before use. The Agent Ledger assumes no liability for outcomes resulting from use. Use at your own risk.

Top skills in this category

API Gateway

@byungkyu

Call third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when the user names a connected app and a concrete action in it - read a mailbox, query a CRM, file an issue, update a spreadsheet, run a query through a connected

39486k

HubSpot

@hith3sh

HubSpot CRM API integration with managed OAuth. Manage contacts, companies, deals, pipelines, tickets, products, line items, marketing emails, and workflows....

326.8k

Pipedrive

@byungkyu

Pipedrive API integration with managed OAuth. Manage deals, persons, organizations, activities, and pipelines. Use this skill when users want to interact with Pipedrive CRM. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login; default to read and list calls, and confirm every write or new connection with the user.

717k

Master Marketing

@tevfikgulep

All-in-one marketing engine combining growth strategy, content remixing, and trend monitoring. Drive growth with data-driven strategies, repurposed content across all platforms, and real-time trend analysis.

147.6k

Feishu Bridge

@alexanys

Connect a Feishu (Lark) bot to Clawdbot via WebSocket long-connection. No public server, domain, or ngrok required. Use when setting up Feishu/Lark as a messaging channel, troubleshooting the Feishu bridge, or managing the bridge service (start/stop/logs). Covers bot creation on Feishu Open Platform, credential setup, bridge startup, macOS launchd auto-restart, and group chat behavior tuning.

812k