agentleFS
tkcostellotkcostello/pastor-ai-skills/skills/announcement-script/SKILL.md

announcement-script

Skill56 starsChanged 4 days agoMITView on GitHub

Writes a word-for-word spoken announcement script for Sunday morning, cut to the three or four items that matter and kept under 90 seconds. Use when the pastor says "write Sunday's announcements", "turn this list into a script for our worship leader", "we have too many announcements, help me cut them", "script for our announcement video", or pastes this week's events for the stage.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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

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

Sunday Announcement Script

Say what matters in 90 seconds or less.

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

The list of everything being considered; more is fine. Helpful extras: who is delivering it (lead pastor, worship leader, volunteer), the tone of the service, and anything that has to be said aloud no matter what.

Cut first

Announcements get tuned out because they try to cover everything. If there are more than four items, rank them by urgency (a deadline this week or next, a real opportunity someone would miss) and by how much of the room it applies to. Only the top three or four make the spoken script. Everything else goes in a short "For the bulletin, slides or email" list at the end with its key logistics. Anything the pastor marked as must-say stays in regardless of rank. A death, birth or serious care need for a known member gets one line from the stage even when it doesn't make the top items. Be decisive: a crowded script helps no one.

Writing for the ear

  • Open with something that earns attention, not "We have a few announcements," which is the room's cue to check their phones. A tie to what just happened in worship, or straight into the first item. Match the energy to the profile's CONGREGATION and VOICE: a quick "Three things, then we'll worship" suits a young room; an older room wants it warm and unhurried.
  • Give each item two or three sentences: why it matters to the person in the seat, the logistics they need (day, time, place), and one specific action the pastor actually gave you (grab a card, text a number, sign up at the table). "Check it out" isn't an action, and don't invent a table or a number that may not exist.
  • Leave the fine print for the bulletin. Room numbers, committee chairs, parking details and form locations don't survive being heard once.
  • Bridge between items simply. "Also" and "One more thing" are fine; a clever segue that strains to connect two unrelated items is worse than none.
  • Close by leading into what's next in the service ("Now, let's worship."), not "That's all I've got" or "Back to you, Pastor."
  • Keep it to 150-225 words, which is 60-90 seconds at a natural pace. If it runs long, cut an item rather than asking the announcer to talk faster. Ninety seconds feels like three minutes to a room waiting to worship.

Write every sentence so it can be read aloud as written, with no blanks to fill. Never put a [placeholder] in the spoken script: if a must-say item is missing a detail (date, time, place), ask the pastor before writing; otherwise move the item to the bulletin list with its gap marked there. Add a delivery cue in brackets only where it helps: [pause], [hold up the card], [point to the screen]. If someone other than the lead pastor is delivering, add a one- or two-line tone note at the top so the script fits their voice and energy.

Output

Give the script in chat with its estimated length in seconds and the bumped items below it. If the pastor asks for a PDF or printable copy for the announcer, follow references/pdf.md.

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.