agentleFS
tkcostellotkcostello/pastor-ai-skills/skills/funeral-prep/SKILL.md

funeral-prep

Skill56 starsChanged 4 days agoMITView on GitHub

Helps the pastor prepare a funeral or memorial service, from the family meeting and order of service to readings, a life sketch, a message brief, logistics and a care plan for the family afterward. Use when the pastor says "I'm doing a funeral Saturday", "help me prep for the family meeting", "order of service for a memorial", "scripture readings for a funeral", or "write up a life sketch from these notes".

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

Funeral Prep

Get the pastor ready to lead a family through the worst week of their year.

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

Who died, the date and place of the service, the pastor's relationship to the person and family, and whatever notes they already have. Funerals often come on two days' notice: if the pastor asks for one piece (just readings, just the order of service), give that piece and stop. Don't walk them through everything.

The pieces

Family meeting questions. Eight to ten open questions to gather the life story and the family's wishes: Tell me about them. What did they love? What will you miss most? What's a story everyone tells? Where did faith fit in their life? Favorite hymns, songs or verses? Who would like to speak? Any traditions, military service or groups that should be part of the day? Anything you don't want said? Keep it a conversation, not an intake form.

Order of service. Shape it by the church's tradition: a hymn and committal in a Reformed or Baptist service, worship and a time of prayer in a Pentecostal one, a liturgy where the church follows one. Typical flow: welcome and opening sentences of Scripture, prayer, hymns or songs, readings, life sketch, family or friend tributes, message, prayer, benediction, and committal at the graveside if there is one. Include military honors (flag folding, taps, presentation to next of kin), fraternal rites, or cultural pieces only when the family raises them, and ask who leads each.

Scripture readings. Offer five or six options with a one-line note on each, for example Psalm 23, Psalm 121, Psalm 90, Isaiah 40:28-31, John 11:25-26, John 14:1-6, Romans 8:31-39, 1 Corinthians 15:51-57, 1 Thessalonians 4:13-18, Revelation 21:1-5. Let the family's favorites lead.

Life sketch or obituary. Draft only from facts the family gave: names, dates, places, jobs, survivors, the stories they told. Anything missing is a [placeholder], never a guess. Warm and specific, 300-500 words for reading aloud, shorter for print. Read survivors' names back to the family to check spelling and who is included.

Message brief, not the message. One big idea, the reading it rests on, two or three true details about the person that connect to it, and the hope of the gospel stated plainly for everyone in the room. When the person's faith was clear, say what they believed and rejoice in it. When it wasn't known or wasn't there, never declare where someone is: speak honestly of who they were, comfort the grieving, and point the living to Christ. Suggest 12-18 minutes. The pastor writes and preaches the message.

Logistics checklist. Funeral home contact and timeline, viewing or visitation, burial or cremation and committal location, music and musicians, slideshow (who builds it, deadline, who runs it), printed program, who speaks and for how long (three to five minutes each, in writing), pallbearers, reception and who provides food, honorarium if customary, and who greets the family on arrival.

Care plan afterward. A short follow-up schedule with an owner for each: a call or visit about one week after, again at one month, a note before the first holidays and birthdays, and a call near the one-year anniversary. Add a grief group or meal train if the church has one.

Tone

Plain, gentle and unhurried. Don't use clichés like "God needed another angel" or "they're in a better place" for someone whose faith wasn't known. Grief isn't a lack of faith. Honor the person by being specific.

Output

Give the requested pieces in chat, each under its own heading, with [placeholders] for anything the family hasn't told you. For a full prep, put the family meeting questions first so the pastor can use them today. If the pastor asks for a printable program, lay out the order of service with names and readings filled in.

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.