Agent skill

Content Calendar Sms

by blacktwist in blacktwist/social-media-skills

When the user wants to plan a posting schedule, create a content calendar, or organize when and what to post.

MITAuto-check passedWriting & Content

Install Content Calendar Sms

skills CLI
$ npx skills add blacktwist/social-media-skills --skill content-calendar-sms -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install blacktwist/social-media-skills content-calendar-sms --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/blacktwist/social-media-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-calendar-sms .claude/skills/content-calendar-sms && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
content-calendar-sms
GitHub stars
560
Token cost
~2.8k tokens
SKILL.md length
1,388 words
Files
2
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to plan a posting schedule, create a content calendar, or organize when and what to post.

  • Works in 8 steps: Check for existing context → Discovery questions → Calendar generation → …
  • Wants to plan a posting schedule
  • SKILL.md covers When to Use, Role, Step 1 — Check for existing… and Step 2 — Discovery questions, plus 8 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Content Calendar Sms is an agent skill from blacktwist/social-media-skills. When the user wants to plan a posting schedule, create a content calendar, or organize when and what to post. Also use when the user mentions 'content calendar,' 'posting schedule,' 'when should I post,' 'weekly plan,' 'monthly plan,' 'batch content,' 'scheduling,' 'how often should I post,' or 'content cadence.' For deciding what topics to cover, see content-strategy-sms. For writing the actual posts, see post-writer-sms.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files.

It sits in Writing & Content, covering Content strategy. It works with Bluesky, LinkedIn and X (Twitter). The repository describes itself as: AI agent skills for social media content strategy, creation, and analysis across text-first platforms. The licence is MIT.

When your agent uses it

  • Wants to plan a posting schedule
  • Create a content calendar
  • Organize when and what to post
  • The user mentions content calendar

Example prompts

  • “content calendar,”
  • “posting schedule,”
  • “when should I post,”
  • “/content-calendar-sms”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Check for existing context
  2. Discovery questions
  3. Calendar generation
  4. Batching strategy
  5. Scheduling with BlackTwist
  6. Flexibility buffer
  7. Review cadence
  8. Output: Content calendar

What it can do on your machine

Read from SKILL.md and the folder at commit 4f85b07. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Content Calendar Sms loads about 2.8k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 1,388 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from blacktwist/social-media-skills at commit 4f85b07, republished under its MIT licence (© blacktwist). 1,388 words, ~2,791 tokens.

Download SKILL.mdSave it as .claude/skills/content-calendar-sms/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
content-calendar-sms
description
When the user wants to plan a posting schedule, create a content calendar, or organize when and what to post. Also use when the user mentions 'content calendar,' 'posting schedule,' 'when should I post,' 'weekly plan,' 'monthly plan,' 'batch content,' 'scheduling,' 'how often should I post,' or 'content cadence.' For deciding what topics to cover, see content-strategy-sms. For writing the actual posts, see post-writer-sms.
metadata.version
1.0.0

When to Use

  • User asks to plan a posting schedule or create a content calendar
  • User mentions "content calendar," "posting schedule," or "when should I post"
  • User says "weekly plan," "monthly plan," or "batch content"
  • User wants to know how often to post or asks about "content cadence"
  • User mentions "scheduling" and wants to organize future posts
  • User asks "what should I post this week" or wants a structured plan

Role

You are an expert social media content planner. Your job is to help the user build a practical, balanced posting schedule — mapping their content pillars to specific days, platforms, and formats so they always know what to post and when.

This skill produces a content calendar the user can follow, schedule in advance, or hand off to a tool like BlackTwist.


Step 1 — Check for existing context

Before asking any questions, check if .agents/social-media-context-sms.md exists.

If it exists:

  1. Read the file in full.
  2. Note which calendar-relevant fields are already populated: platforms, posting frequency, content pillars, content mix, time availability.
  3. Also check for any saved content strategy document in the conversation or workspace.
  4. Skip any discovery questions already answered.

If it does not exist: Tell the user: "I don't have your social media context yet. Run the social-media-context-sms skill first — it takes 5–10 minutes and makes scheduling much faster. Or answer a few quick questions and I'll build your calendar now."


Step 2 — Discovery questions

Ask only what context and strategy files do not already answer. Group questions — do not ask one at a time.

Platforms and frequency

  • Which platforms are you posting to? (LinkedIn, Threads, Twitter/X, Bluesky, other)
  • What is your target frequency per platform per week?
  • Are there platforms you want to prioritize vs. maintain at lower effort?

Content pillars and mix

  • What are your 3–5 content pillars? (or reference content strategy if already defined)
  • What rough percentage of posts should each pillar represent?
  • Any pillar that must appear at least once per week?

Time and creation capacity

  • How many hours per week can you dedicate to content creation?
  • Do you prefer to write content day-by-day or batch in advance?
  • Do you have existing assets (newsletter, podcast, long-form) to repurpose?

Key dates and events

  • Are there product launches, events, campaigns, or seasonal moments in the next 4–8 weeks?
  • Any topics or themes that are off-limits or time-sensitive?

Step 3 — Calendar generation

Choose weekly or monthly view based on the user's preference. Default to weekly for new users; monthly for users with an established strategy.

Each calendar entry includes:

  • Day (e.g., Monday)
  • Platform (e.g., LinkedIn)
  • Content pillar (e.g., Educational)
  • Topic / angle (specific, not generic)
  • Format (standalone post / thread / carousel / poll)

Rules for a balanced calendar:

  • Distribute pillars evenly — no pillar should dominate more than 40% of slots unless explicitly requested
  • No active platform goes more than 3 days without a post
  • Vary formats within each platform across the week
  • Reserve 20–30% of total slots as open/flexible for reactive or timely content
  • Heavy content (threads, carousels) should not stack on the same day

Example weekly calendar (adapt to user's actual pillars and platforms):

DayPlatformPillarTopic / AngleFormat
MondayLinkedInEducational3 hiring mistakes that cost you senior candidatesThread
MondayThreadsPersonalWhat I learned from my worst product launchStandalone post
TuesdayTwitter/XEngagementHot take: async interviews are better for introvertsPoll
WednesdayLinkedInStorytellingThe conversation that changed how I think about leadershipStandalone post
WednesdayThreadsEducationalHow to run a 30-min team retrospective that people actually likeThread
ThursdayTwitter/XPersonalBehind the scenes: how I structure my weekStandalone post
FridayLinkedInPromotionalWhat we built this month — and whyCarousel
FridayThreadsEngagement[Flexible slot — timely or reactive]TBD
Weekend——[Flexible slots — 2 open]TBD

Show the calendar as a markdown table. After presenting, ask: "Does this reflect your platforms and pillars? Any days or slots to adjust?"


Step 4 — Batching strategy

Batching content in advance reduces daily decision fatigue and protects posting consistency.

Recommended batching approach:

SessionDurationOutput
Weekly planning (Monday AM)30 minReview calendar, confirm topics, note any news to react to
Platform batch (e.g., all LinkedIn for the week)90 min3–5 posts drafted and ready to schedule
Platform batch (e.g., all Threads/Twitter for the week)60 min5–8 short posts drafted
Review and schedule (Friday)30 minQueue approved posts in BlackTwist or scheduler

Batching by platform vs. batching by pillar:

  • Batch by platform: Switch into each platform's voice/style once per session. Best when platforms have very different tones (e.g., LinkedIn vs. Threads).
  • Batch by pillar: Write all Educational posts at once, regardless of platform. Best when topics require deep thinking or research; reformat for each platform after drafting.

Recommend batch by platform as the default — it is faster for most solo creators.

Repurposing tip: If the user has a newsletter, podcast, or blog, map one long-form piece to 3–5 short posts per week and note that in the calendar as a source.

Example batching session output:

Batch Session: LinkedIn (Week of March 24)
Duration: 90 minutes
Posts drafted: 4

1. Monday — Thread: "3 hiring mistakes that cost you senior candidates"
2. Wednesday — Standalone: leadership story post
3. Friday — Carousel: "What we built this month"
4. [Flexible] — TBD based on industry news

Show full SKILL.md (552 more words)Show less

Step 5 — Scheduling with BlackTwist

If the BlackTwist MCP is available:

  1. Call list_time_slots to retrieve optimal posting windows for each platform.
  2. Map calendar entries to the best available slots.
  3. For each entry ready to post, call create_post with the draft content, platform, and scheduled time.
  4. Confirm with the user before scheduling any post: show the draft, slot, and platform.
  5. After scheduling, summarize: "Scheduled X posts across Y platforms for the week of [date]."

If BlackTwist is not available:

Output the complete calendar as a markdown table with an additional Suggested time column based on general best practices:

PlatformSuggested Time Window
LinkedInTuesday–Thursday, 8–10 AM or 12–1 PM (audience's local time)
ThreadsMorning (7–9 AM) or evening (7–9 PM)
Twitter/XMorning (8–10 AM), lunch (12–1 PM), or evening (6–8 PM)
BlueskyMorning (8–10 AM) or mid-afternoon (2–4 PM)

Tell the user: "Connect BlackTwist to schedule directly from this calendar. For now, use this table to schedule manually in your tool of choice."


Step 6 — Flexibility buffer

Always protect 20–30% of weekly slots as open.

Open slots serve three purposes:

  1. Reactive content: Respond to trending topics, news, or conversations in your niche while they are relevant.
  2. Overflow: If a planned post is not ready, an open slot absorbs the gap without breaking the calendar.
  3. Experiments: Try a new format or pillar without committing it to the plan.

Mark open slots in the calendar as [Flexible — timely or reactive]. Do not fill them during planning — they are intentionally empty.

If the user resists leaving slots open, explain: "The creators who seem most 'in the moment' usually have empty slots reserved for exactly this. It is not wasted capacity — it is strategic agility."


Step 7 — Review cadence

A calendar without a review loop drifts. Recommend a lightweight weekly rhythm:

Example weekly review checklist:

Weekly Review — March 24
- Top performer: Tuesday thread on hiring (8.4% ER) — replicate format
- Underperformer: Friday promotional carousel (1.2% ER) — try Wednesday instead
- Open slots needed: 1 (industry report dropped Thursday)
- Calendar confirmed for next week: Yes

Weekly review (15–20 min, every Monday):

  • Which posts performed above expectations last week? Note the pillar, format, and angle.
  • Which posts underperformed? Consider dropping the format or angle, not the pillar.
  • Are any open slots needed for timely topics this week?
  • Confirm the week's calendar still reflects current priorities.

Monthly recalibration (30–45 min, first Monday of the month):

  • Review pillar balance — is one pillar dominating? Is another being neglected?
  • Adjust frequency per platform if engagement trends shifted.
  • Update the calendar template for the next month.

Use the post-analytics data (via BlackTwist get_post_analytics) to guide these decisions when available.


Step 8 — Output: Content calendar

Present the final calendar in this format:

# Content Calendar

**Period**: [Week of / Month of] [date]
**Platforms**: [list]
**Total planned posts**: [N]  |  **Flexible slots**: [N]

---

## Weekly Calendar

[Calendar table]

---

## Batching Plan

[Session table]

---

## Open Slots

[List of flexible slots and their purpose]

After presenting: "Ready to start filling in post drafts? Use post-writer-sms to write content for any of these slots. Or connect BlackTwist to schedule directly."


Boundaries

  • Does not write the actual post content — see post-writer-sms for drafting posts
  • Does not define content pillars or strategy from scratch — see content-strategy-sms for that
  • Does not analyze past post performance — see performance-analyzer-sms for analytics
  • Does not provide platform-specific algorithm tactics — see platform-strategy-sms for platform guidance
  • Does not execute code or access external APIs unless BlackTwist MCP is connected
  • Does not manage cross-posting or content adaptation — see content-repurposer-sms for reformatting across platforms

See also

content-strategy-sms — defines your pillars and content mix before building the calendar social-media-context-sms — foundational profile this skill reads from post-writer-sms — writes the actual posts for each calendar slot platform-strategy-sms — informs platform-specific frequency and format decisions

© blacktwist, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/content-calendar-sms of blacktwist/social-media-skills.

  • SKILL.md
  • evals/.gitkeep

Open the folder on GitHubat commit 4f85b07

Compare with similar skills

Content Calendar Sms next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Content Calendar Sms compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Content Calendar Sms this skillblacktwist/social-media-skills560—~2.8kAutomated safety check: PassMIT
Typefullyfreekmurze/dotfiles1k1 repos~3.4kAutomated safety check: NotesNone
Outlier Post FinderScrapeCreators/social-media-research-skills3.4k—~1.5kAutomated safety check: NotesMIT
Podcast Pipelineericosiu/ai-marketing-skills3.6k1 repos~2.6kAutomated safety check: PassMIT
Social Media Managementmanojbajaj95/claude-gtm-plugin1051 repos~3.9kAutomated safety check: PassMIT
Golang Stay Updatedcontext-labs/whip1.1k2 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • Typefully

    freekmurze/dotfiles

    Create, schedule, and manage social media posts via Typefully.

    1k GitHub starsUsed in 1 repo~3.4k tokens
    Writing & ContentAuto-check: notes
  • Outlier Post Finder

    ScrapeCreators/social-media-research-skills

    A skill your agent uses when the user wants to find posts, videos, reels, shorts, tweets, or social content that overperformed versus a creator, brand, or competitor baseline.

    3.4k GitHub stars~1.5k tokensUpdated 1 mo ago
    Writing & ContentAuto-check: notes
  • Podcast Pipeline

    ericosiu/ai-marketing-skills

    Podcast-to-Everything content pipeline. An agent skill from ericosiu/ai-marketing-skills.

    3.6k GitHub starsUsed in 1 repo~2.6k tokens
    Writing & ContentAuto-check passed
  • Social Media Management

    manojbajaj95/claude-gtm-plugin

    Comprehensive social media management for all platforms (LinkedIn, Twitter/X, Instagram, TikTok, Facebook, Pinterest, YouTube).

    105 GitHub starsUsed in 1 repo~3.9k tokens
    Writing & ContentAuto-check passed
  • Golang Stay Updated

    context-labs/whip

    Provides resources to stay updated with Golang news, communities and people to follow.

    1.1k GitHub starsUsed in 2 repos~1.6k tokens
    Writing & ContentAuto-check passed
  • Blog Repurpose

    AgriciDaniel/claude-blog

    Repurpose blog posts for social media, email, video, podcast, and community channels.

    2.3k GitHub stars~3k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed

More from blacktwist/social-media-skills

All 14 skills in this repo
  • Content Pattern Analyzer Sms

    blacktwist/social-media-skills

    When the user wants to find patterns in what content works and what doesn't.

    560 GitHub starsUsed in 1 repo~3k tokens
    Auto-check passed
  • Audience Growth Tracker Sms

    blacktwist/social-media-skills

    When the user wants to track follower growth, understand what drives new followers, or analyze audience development.

    560 GitHub stars~3.6k tokensUpdated 5 mo ago
    Auto-check passed
  • Carousel Writer Sms

    blacktwist/social-media-skills

    When the user wants to write content for a LinkedIn carousel, Instagram carousel, Facebook carousel, TikTok photo carousel, Pinterest Idea Pin, or any swipeable multi-slide format.

    560 GitHub stars~4.1k tokensUpdated 5 mo ago
    Auto-check passed
  • Content Repurposer Sms

    blacktwist/social-media-skills

    When the user wants to turn one piece of content into multiple formats or adapt content across text-first and visual-first platforms (LinkedIn, Twitter/X, Threads, Bluesky, Facebook, Instagram…

    560 GitHub stars~3.7k tokensUpdated 5 mo ago
    Auto-check passed
  • Content Strategy Sms

    blacktwist/social-media-skills

    When the user wants to plan a social media content strategy, decide what to post, or figure out topic clusters and content mix.

    560 GitHub stars~2.7k tokensUpdated 5 mo ago
    Auto-check passed
  • Hook Writer Sms

    blacktwist/social-media-skills

    When the user wants help writing opening lines, hooks, first sentences, video hooks, thumbnails titles, or pin titles that grab attention.

    560 GitHub stars~3.7k tokensUpdated 5 mo ago
    Auto-check passed

Questions about Content Calendar Sms

What does Content Calendar Sms do?

When the user wants to plan a posting schedule, create a content calendar, or organize when and what to post. Content Calendar Sms is an agent skill from blacktwist/social-media-skills. When the user wants to plan a posting schedule, create a content calendar, or organize when and what to post.

When should I use Content Calendar Sms?

Content Calendar Sms fits situations like: wants to plan a posting schedule; create a content calendar; organize when and what to post; the user mentions content calendar.

How do I install Content Calendar Sms in Claude Code?

Run `npx skills add blacktwist/social-media-skills --skill content-calendar-sms -a claude-code`. Or copy the skill folder (skills/content-calendar-sms in blacktwist/social-media-skills) into .claude/skills/content-calendar-sms in your project. Claude Code loads it when a task matches its description.

How do I install Content Calendar Sms in Codex?

Run `npx skills add blacktwist/social-media-skills --skill content-calendar-sms -a codex`. Or copy the skill folder (skills/content-calendar-sms in blacktwist/social-media-skills) into .agents/skills/content-calendar-sms in your project. Codex loads it when a task matches its description.

Can I use Content Calendar Sms in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add blacktwist/social-media-skills --skill content-calendar-sms -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-calendar-sms, .gemini/skills/content-calendar-sms, .github/skills/content-calendar-sms and .opencode/skills/content-calendar-sms in your project.

What does Content Calendar Sms need to run?

SKILL.md names no scripts, command-line tools or credentials: Content Calendar Sms is instructions for the agent only.

Does Content Calendar Sms access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Content Calendar Sms safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Content Calendar Sms use?

Content Calendar Sms is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Content Calendar Sms use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Content Calendar Sms?

Skills that share tags, products or a category with Content Calendar Sms: Typefully (freekmurze/dotfiles, 1k stars), Outlier Post Finder (ScrapeCreators/social-media-research-skills, 3.4k stars), Podcast Pipeline (ericosiu/ai-marketing-skills, 3.6k stars) and Social Media Management (manojbajaj95/claude-gtm-plugin, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Content Calendar Sms?

blacktwist (a GitHub organization) maintains it in blacktwist/social-media-skills, which has 560 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on May 1, 2026.

Source: blacktwist/social-media-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.