跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
效率与协作

church-social-post

Use when writing social media posts for a church: Facebook, Instagram, or Twitter/X captions for events, sermons, scripture, holidays, or announcements.

tkcostello · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add tkcostello/pastor-ai-skills --skill church-social-post

技能说明


name: church-social-post description: Use when writing social media posts for a church: Facebook, Instagram, or Twitter/X captions for events, sermons, scripture, holidays, or announcements. argument-hint: "[topic or event]"

Church Social Media Post

One topic, three platforms, zero stress.

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 any of the following:

  • A topic (e.g., "We just baptized 12 people this Sunday")
  • An upcoming event (e.g., "Easter Sunday service on April 20")
  • A scripture verse (e.g., "Romans 8:28")
  • A sermon quote or insight (e.g., "You can't lead people where you haven't been yourself")
  • A church win, story, or milestone
  • A general idea you want to post about

Optional: Tell me which platform(s) you want, and if you have a post type preference: quote graphic, photo caption, engagement question, event promo, or story/testimony.


Step 1: Select Post Type

Before writing, I match your input to the best post format:

InputBest Post Type
Scripture verseQuote graphic with reflection caption
Upcoming eventEvent promo with clear CTA
Sermon quote or insightThought-leadership caption
Church win or storyTestimony/celebration post
No specific inputEngagement question or behind-the-scenes prompt

If you tell me your preference, I use that. If not, I choose based on what will perform best for your input.


Step 2: Write Platform-Specific Posts

I write a distinct, optimized post for each platform. These are never copy-paste copies of each other. Each platform has a different culture, audience behavior, and algorithm. I respect that.


Facebook

Target length: 100-250 words. Facebook rewards slightly longer posts that invite conversation. Walls of text kill reach. So does one-sentence fluff.

Structure:

  • Hook line (first sentence must stop the scroll)
  • Body (context, story, or reflection)
  • CTA (what do you want them to do next?)
  • Question (drives comments, which drive reach)

Image suggestion: I describe the ideal image for this post. If it's a quote graphic, I give you the exact quote text (under 15 words) and a style description.

Example output format:

[Hook line]

[Body: 2-4 short paragraphs with a clear point or story]

[CTA: one sentence]

[Comment-driving question]

Image: [Description of ideal photo, graphic, or design]


Instagram

Target length: 50-150 words for feed post. Instagram is visual first, caption second. The caption supports the image, not the other way around.

Structure:

  • Hook line (this must work before the "...more" cutoff, roughly 125 characters)
  • Body (reflection, context, or story)
  • 3-5 hashtags at the end (never at the start, never 30 at once)

Story version: If relevant, I suggest a quick Story format using a poll sticker, question sticker, or countdown for events.

Carousel suggestion: If the content is list-based or has multiple points, I flag it as a carousel opportunity and suggest what each slide covers.

Image suggestion: I describe the ideal image or graphic concept. If quote graphic: exact text (under 15 words) and style description.

Example output format:

[Hook line]

[Body: short, punchy, visual language]

#hashtag1 #hashtag2 #hashtag3

Image: [Description]

Story version (optional): [Poll or question sticker concept]


Twitter/X

Target length: Under 280 characters, ideally under 200. Twitter rewards punchy, opinionated, conversational posts. This is not the place for paragraphs.

Tone: Slightly edgier than Facebook or Instagram. More direct. Less polish. More personality.

Hashtags: 0-1. No keyword stuffing.

Format options:

  • Standalone tweet: one punchy statement, observation, or question
  • Thread starter: first tweet hooks, rest of thread delivers the value (I note when the content calls for this)

Example output format:

[Punchy, under-200-character tweet]

Format: Standalone tweet (or) Thread starter

Thread notes (if applicable): [What each follow-up tweet covers]


Step 3: Image Suggestions

For every post, I give you a specific image description. Not vague. Not generic. Specific enough that you can brief a designer or find the right stock photo.

For quote graphics, I give you:

  • The exact quote text (15 words or fewer)
  • Font style direction (bold/serif/clean/etc.)
  • Color palette suggestion (if relevant to your church brand)
  • Background style (solid color, texture, lifestyle photo with overlay, etc.)

Anti-Patterns I Avoid

These are the things that kill reach, signal low effort, and make your church look out of touch online. I never do these.

  • Never post the same caption across all three platforms. Different platforms need different voices. What works on Facebook reads wrong on Twitter.
  • Never use more than 5 hashtags on any platform. More is not more. It looks spammy and tanks reach on most platforms.
  • Never start an Instagram caption with a hashtag. It buries the hook before anyone reads it.
  • Never post a Facebook link with no context. A bare link with no caption or setup gets almost zero organic reach. Always write a post around the link.
  • Never post scripture without reflection. "Jeremiah 29:11" alone is not a strategy. Every verse needs a sentence or two connecting it to real life. Otherwise it's noise.
  • Never use em dashes. Periods, commas, and colons do the job without looking like generated content.

Output Format

I deliver posts in this order:

  1. Post Type Selected (one line, explains which format and why)
  2. Facebook Post (full caption + image suggestion)
  3. Instagram Post (full caption + hashtags + image suggestion + Story version if relevant)
  4. **
阅读完整来源 ↗