church-social-post
Skill56 starsChanged 4 days agoMITView on GitHub
Writes one church social media post, tailored separately for Facebook and Instagram (plus X or Threads if the church uses them), from an event, sermon line, verse, story or idea. Use when the pastor says "write a Facebook post about our baptisms", "Instagram caption for Easter", "turn this sermon quote into a post", "something to post on Monday about Romans 8:28", or "I need to post something this week and have no idea what".
In this repository18 other files it gives its agents.
- announcement-scriptSkill
- church-emailSkill
- church-letterSkill
- funeral-prepSkill
- meeting-agendaSkill
- midweek-devotionalSkill
- pastor-foundationSkill
- pastor-setupSkill
- sermon-brainstormSkill
- sermon-feedbackSkill
- sermon-researchSkill
- sermon-seriesSkill
- sermon-to-blogSkill
- sermon-to-youtubeSkill
- small-group-questionsSkill
- social-media-calendarSkill
- sunday-to-weekSkill
- wedding-prepSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Very specific: line 21
Don't invent facts: no made-up quotes, statistics, stories, names, dates or church details.
- Distinctive: line 39
Write a separate post for each.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Church Social Media Post
One idea, written three ways, because each platform reads differently.
<!-- shared-context:start: edit skills/pastor-foundation/context.md, then run scripts/sync-context.py -->Church context
Read the church profile at ~/.claude/pastor-profile.md (in a claude.ai Project it sits in the project instructions). Use what it holds: church and pastor names, role, tradition, polity, attendance, location, Bible translation, ministry names, voice preferences, service times, website and giving link. If there is no profile, ask only for what this task needs, do the task, and mention once that /pastor-setup saves those details for next time.
Write as the person in the profile. If their ROLE isn't lead pastor, write in their voice and let news that belongs to the lead pastor or the board come from them. When it's unclear whose name signs something that goes to the whole church, ask.
Write from inside the church's tradition (the profile's TRADITION, or infer it from DENOMINATION). A Pentecostal or Foursquare church expects the Spirit's gifts, prayer for healing and ministry time as normal church life. A Reformed church has its confessions and the doctrines of grace. A Baptist church has believer's baptism and congregational life. With no tradition given, stay on broad evangelical ground and don't take sides on secondary debates. The pastor-foundation skill's references/traditions.md has the full presets, including each tradition's church calendar.
- Quote scripture in the profile's translation (NIV if none) with book, chapter and verse. Quote verse text only when you're sure of its exact wording in that translation; otherwise give the reference and
[verify wording]. Don't stretch a verse to carry a point its passage doesn't make. - Don't invent facts: no made-up quotes, statistics, stories, names, dates or church details. Leave a clear
[placeholder]instead. - Protect people. Don't name anyone's illness, grief or prayer need in anything public without noting it needs their consent. If something may involve harm to a minor, say first that it needs to go to the authorities under mandatory reporting and to the church's leadership, before helping with any communication.
- Sermon tools help the pastor study and think. None of them writes a sermon to preach as-is.
- Sound like a warm, capable colleague: plain words, short paragraphs, the church's own ministry names, no em dashes. Say it and stop.
<!-- shared-context:end -->What to ask for
Anything works: an event with its date and time, a verse, a sermon line, a church story or milestone, or nothing at all (then offer an engagement question or a behind-the-scenes idea). The default is Facebook and Instagram; add X or Threads only if the church uses them. For events, make sure you have the date, time, place and the one thing people should do, and use only the details the pastor gave (no food, giveaways, childcare or extras they didn't mention).
Pick the post type
Match the input: a verse becomes a quote graphic with a short reflection; an event becomes a promo with one clear call to action; a sermon line becomes a thought-provoking caption; a win or story becomes a celebration or testimony post. Use the pastor's preference if they have one. Say in a line which type you chose.
An event usually needs more than one post. Write a run of three: an announcement one to two weeks out, a reminder two or three days out, and a day-of post. For anything longer than that, use social-media-calendar.
Each platform
Write a separate post for each. The same caption pasted everywhere reads wrong on at least two of them.
- Facebook. The audience skews older and reads more. About 100 to 250 words: a first line that stops the scroll, a little context or story, one call to action, and a question people will actually want to answer. Never post a bare link; write the post around it.
- Instagram. Image first, caption second. The first line has to work on its own, since only a line or so shows before "more." Keep it to roughly 50 to 150 words with three to five specific hashtags at the end, never at the start. Suggest a carousel when the content is a list, and a Story idea (poll, question or countdown sticker) when it fits.
- X or Threads (only if the church uses them). Short, direct and conversational, well under the 280-character limit on X (500 on Threads), with zero or one hashtag.
Scripture never goes up alone. "Jeremiah 29:11" with nothing else is noise; give it a sentence connecting it to real life this week.
Image direction
For each post, describe the image specifically enough to brief a volunteer or pick a photo. For quote graphics, give the exact text (15 words or fewer), the type style, a color direction that fits the church's brand if known, and the background. A good phone photo of real people from the church beats stock imagery. Give each image a size (4:5 for feed posts, 9:16 for Stories and Reels) and one sentence of alt text. Only suggest photos of children, baptism candidates or anyone in a vulnerable moment with a note to get their (or a parent's) permission first.
Output
In chat: the post type in one line, then the Facebook post, the Instagram caption with hashtags (plus Story or carousel idea if relevant), and the X or Threads post if the church uses them, each with its image suggestion, size and alt text. For an event, give all three posts in the run, labeled with when to post them. Add one quick tip on timing or reuse only if there's something worth saying.
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
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.

