Social Media Calendar logo

Social Media Calendar

Community
tkcostello
social-media-calendar

Use when planning a week or month of church social media content, mapping posts to dates, platforms, sermon series, and upcoming events.

Overview

Publishertkcostello
Repositorypastor-ai-skills
Skill namesocial-media-calendar
Stars
56
Forks
34
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by tkcostello on GitHub. Read the source before you install it.

Installation

Install the Social Media Calendar AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/tkcostello/pastor-ai-skills/tree/main/skills/social-media-calendar
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/tkcostello/pastor-ai-skills.git /tmp/pastor-ai-skills
mkdir -p .claude/skills
cp -r /tmp/pastor-ai-skills/skills/social-media-calendar .claude/skills/social-media-calendar
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Social Media Calendar in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Social Media Calendar on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Social Media Calendar is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Social Media Content Calendar

Plan a week (or month) of posts in five minutes.

Before writing: follow the pastor-foundation skill and load the church profile from ~/.claude/pastor-profile.md. If the profile file is missing, run the pastor-setup skill first.


What You Need to Provide

Give me the following so I can build your calendar:

  • Time period: This week, next week, this month, or a specific date range
  • Upcoming sermon series or topics: What are you preaching? Series title, week number, or key theme
  • Events and key dates: Anything on the church calendar: baptisms, volunteer appreciation, outreach events, guest speakers, special services
  • Any special emphasis: Missions month, giving campaign, prayer initiative, back-to-school, holiday season, launch Sunday
  • Posting frequency (optional): Default is 4-5 times per week. Tell me if you want more or less.

You do not need to have everything figured out. Give me what you have and I will fill in the gaps with content that fits your church's rhythm.


Step 1: Map the Calendar

Before writing any post ideas, I build the content foundation using this weekly framework. The goal is a balanced mix: reinforce the message, build community, drive engagement, and invite action.

DayContent TypePurpose
SundaySermon quote or recapReinforce the message people just heard
MondayBehind-the-scenes or team highlightBuild community, show the human side
TuesdayEngagement question or pollDrive interaction and comments
WednesdayMidweek encouragement (scripture or devotional thought)Pastoral care between Sundays
ThursdayEvent promo or practical tipDrive action, fill seats, move people
FridayFun, lighthearted content, or testimonyEnd the week on a positive note
SaturdaySunday preview or community inviteBuild anticipation, drive attendance

This framework adapts based on your actual events and calendar. If you have a baptism Sunday, that changes everything around it. If you have no events that week, I lean into message-driven and engagement content.

Not every day needs a post. Four to five quality posts per week outperforms seven mediocre ones every time.


Step 2: Generate the Calendar

I produce a complete calendar table with every post mapped out:

DateDayPlatformPost TypeTopic and Content IdeaCTA

Each row includes:

  • Date: The specific date (e.g., April 13)
  • Day: Day of the week
  • Platform: Facebook, Instagram, or both (when cross-posting makes sense)
  • Post Type: Sermon quote, engagement question, event promo, testimony, behind-the-scenes, scripture, fun/lighthearted, Sunday invite
  • Topic and Content Idea: A clear, ready-to-use concept. Not a vague suggestion. A specific idea with enough detail to write the post or brief a team member.
  • CTA: The one action you want people to take. Comment below. Share this. Register here. See you Sunday.

Step 3: Notes and Flags

After the calendar table, I add three categories of notes:

Graphics Needed I flag every post that benefits from a custom graphic. I note whether it is a quote card, event promo image, or photo opportunity. If you have a graphic designer or volunteer on Canva, this list tells them exactly what to build and when it needs to be ready.

Evergreen Posts I identify 1-2 posts in the calendar that are not date-sensitive. These can be scheduled in advance, batched when you have a creative burst, or held as backup content if a week falls apart. Knowing which posts are evergreen keeps your calendar flexible without going dark.

Platform Notes I call out which posts are platform-specific versus which can be cross-posted with minor adjustments. Cross-posting is not always lazy. Sometimes the same message genuinely works on Facebook and Instagram. But I will tell you when a post needs a different hook, different image format, or different caption length for each platform.


How I Prioritize Content

Not all weeks are equal. When you give me your inputs, I run them through this priority filter before building the calendar:

  1. Major events first. Easter, launch Sunday, baptism Sunday, a guest speaker. These anchor the calendar. Everything else builds around them.
  2. Sermon series next. Your preaching is the thread that holds the week together. At minimum, Sunday gets a sermon recap or quote and the rest of the week echoes the theme.
  3. Engagement content throughout. Comments and saves tell the algorithm your page is worth showing. I place engagement questions and interactive posts at consistent intervals to keep the week from going flat.
  4. Evergreen and practical content as fill. Tips, testimonies, and behind-the-scenes posts round out the calendar without requiring constant creativity.

Anti-Patterns I Avoid

These are the habits that turn a social media calendar into noise. I will not build a calendar around them.

  • Never schedule more than one post per day per platform. Posting twice in a day trains the algorithm to split your reach and trains your audience to ignore you.
  • Never require a graphic designer for every post. A text-based post on a solid color background or a good phone photo is better than no post while you wait on a designer. I build calendars that are actually executable.
  • Never fill with filler content. Four posts your congregation will stop for beats seven posts they will scroll past. If the idea is weak, it does not make the calendar.
  • Never ignore the sermon. Sunday morning is the center of your church's week. Your social media should extend that message, not replace it with something unrelated.
  • Never use em dashes. Periods, commas, and colons handle transitions without signaling that a machine wrote it.

Output Format

Here is what you get when this skill runs:

  1. Calendar Overview: One paragraph summarizing the week or month, the main themes, and any anchor moments I built around.
  2. Content Calendar Table: Every post mapped by date, platform, post type, idea, and CTA. Ready to hand to a team member or fill in directly.
  3. Graphics Needed: A short list of posts requiring a designed asset, what the asset should be, and a suggested deadline.
  4. Evergreen Posts: 1-2 posts flagged as schedule-in-advance opportunities.
  5. Platform Notes: Any posts that need platform-specific adjustments or are best kept to one platform only.

Everything is ready to act on. No vague suggestions. No research required on your end. You get a calendar you can hand off or execute yourself.


Usage Examples

Input: "This week only. Preaching on generosity, series called 'Open Hands.' We have a volunteer spotlight happening Sunday afternoon. Posting 4 times this week."

Input: "Build me April's calendar. Series is 'Rooted' through the book of John. We have baptisms on April 27 and a community cleanup event on April 19. Missions emphasis all month."

Input: "Next week. No series yet, in between series. Back Sunday with a standalone message on anxiety. Nothing special on the calendar."

Input: "Two weeks. We just launched a new kids ministry called Basecamp. Big push to get families to check it out. Preaching through Ephesians."

Give me what you have. The more context, the sharper the calendar. But even a single sentence gets us started.

Frequently asked questions

What does the Social Media Calendar AI skill do?

Use when planning a week or month of church social media content, mapping posts to dates, platforms, sermon series, and upcoming events.

Why use Social Media Calendar on TypingMind?

Because you install it once and use it with any model. Social Media Calendar is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Social Media Calendar in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/tkcostello/pastor-ai-skills/tree/main/skills/social-media-calendar. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Social Media Calendar?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Social Media Calendar?

As many as you like. As long as a model supports skills, you can use Social Media Calendar with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Social Media Calendar AI skill free?

Yes. It is published on GitHub by tkcostello under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇