agentleFS
tkcostellotkcostello/pastor-ai-skills/skills/church-email/SKILL.md

church-email

Skill56 starsChanged 4 days agoMITView on GitHub

Turns a week's announcements, events and pastoral notes into the all-church email or newsletter, with subject lines and preview text built to get it opened. Use when the pastor says "write this week's church email", "turn these announcements into our newsletter", "here's everything happening this week, make it an email", "I need a subject line for Sunday's email", or pastes a messy list of events to send to the church.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Very specific:

    Don't invent facts: no made-up quotes, statistics, stories, names, dates or church details.

    line 21
  2. Distinctive:

    Quick links: only when the pastor gave URLs or the profile has a WEBSITE: a short "This week:" list of 3-5 actions with their links, for …

    line 46
  3. Distinctive:

    Keep it to 200-400 words; shorter wins.

    line 49

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Weekly Church Email

Turn the week's announcements into an email people actually open.

<!-- 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

Whatever the pastor has, in any shape: bullet points, a voice dump, a sermon recap. Useful extras: a personal note, a prayer need to highlight, the current series, service times if the profile doesn't have them.

Decide what matters first

Before drafting, pick the lead item: the one thing the congregation most needs to know or do this week. It goes first and gets two or three sentences. Keep up to four more as supporting items at a sentence or two each. Everything else goes in a short "Also this week" list at the end, one line per item with its key detail. Drop only what has no audience in the whole church (a leaders-only meeting, a group that already knows), and tell the pastor what you dropped and why. Every item feels important to whoever submitted it, but an email that treats eight things equally communicates none of them.

Subject line and preview text

These two lines decide whether anything else gets read, so build them first.

  • Subject: under 50 characters, specific, led by the most compelling item rather than the most official one. "3 spots left for Family Camp" gets opened; "This Week at Grace Community" gets skipped. Vary the shape week to week (a number, a name, a date, a question, a teaser), because the same formula every week trains people to ignore it. Give two options, A and B, from different angles.
  • Preview text: 40-90 characters that add a second hook instead of repeating the subject. Subject "3 spots left for Family Camp," preview "Register by Wednesday or you'll miss it."

The email

  • Greeting: one or two sentences of the pastor actually showing up, tied to something real the pastor gave you (the sermon text, a baptism, a hard week). Not "Greetings, church family!" or "Happy Monday!" With nothing real to go on, skip the greeting and open with the lead item rather than inventing a moment.
  • Items: what it is, the details that matter, and one clear next step (register, sign up, show up, reply, bring a friend). Bold dates, times, places and deadlines, and nothing else, so bold always means "you need this to act." A minor event gets one sentence and a link, not a paragraph.
  • Quick links: only when the pastor gave URLs or the profile has a WEBSITE: a short "This week:" list of 3-5 actions with their links, for the reader who skimmed. Otherwise leave the section out rather than filling it with placeholders.
  • Closing: one warm sentence, varied week to week ("See you Sunday" is fine), then the pastor's name and church. Skip "Be blessed" and skip a reflective question meant to prompt replies.

Keep it to 200-400 words; shorter wins. Paragraphs of one to three sentences with generous line breaks, since most people read it on a phone between other things.

Output

Give it in chat ready to paste into the email tool: Subject A, Subject B and preview text on top, then the email, then a short note of what was dropped. Inside an item, use a [link] placeholder where a sign-up or registration needs a URL the pastor hasn't supplied.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.