pastor-setup
Skill56 starsChanged 4 days agoMITView on GitHub
Saves the church profile every pastor skill reads (church name, pastor, tradition, attendance, location, Bible translation, ministries, voice). Use when the pastor says "set up my church", "pastor setup", "update my church profile", "we changed Bible translations", "change my denomination", or when a pastor skill finds no ~/.claude/pastor-profile.md.
In this repository18 other files it gives its agents.
- announcement-scriptSkill
- church-emailSkill
- church-letterSkill
- church-social-postSkill
- funeral-prepSkill
- meeting-agendaSkill
- midweek-devotionalSkill
- pastor-foundationSkill
- 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
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
If it exists: show the current values and ask what to change.
- Distinctive: line 18
If it does not exist: run the interview below.
- Distinctive: line 22
Keep it a conversation, not a form:
- Distinctive: line 24
One question per message: Never bundle two questions together.
- Distinctive: line 28
Adapt: If an answer already covers a later question, don't ask it again.
- Distinctive: line 44
After question 6, offer it as a single yes/no: "That's the essentials.
- Distinctive: line 46
If yes, one at a time:
- Very specific: line 58
Write the answers to ~/.claude/pastor-profile.md in exactly this format.
- Very specific: line 86
Add LEAD_PASTOR: <name> under ROLE when the person setting up isn't the lead pastor.
- Distinctive: line 94
If the environment cannot write files (for example, a claude.ai project), run the same interview, then output the filled-in profile block …
≈ “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
Pastor Setup: Your Church Profile
One-time setup for every skill in the pastor-ai-skills collection. This skill runs a short guided interview, then saves a profile file that stores your church's context so you never have to repeat it. Every other skill reads this file automatically.
The profile lives at ~/.claude/pastor-profile.md.
What This Skill Does
- Checks whether
~/.claude/pastor-profile.mdalready exists. - If it exists: show the current values and ask what to change. Update only what the pastor asks to change.
- If it does not exist: run the interview below.
Interview Rules
Keep it a conversation, not a form:
- One question per message. Never bundle two questions together. Ask, wait for the answer, then ask the next.
- Acknowledge each answer in a few words before the next question. Like a person would. Not a form.
- Show progress. Prefix each question with where they are, like "2 of 6."
- Any answer can be "skip." Skipping an optional question is always fine. Move on without comment.
- Adapt. If an answer already covers a later question, don't ask it again. If an answer is interesting ("we're a military town"), one natural follow-up is allowed, but only one.
- Keep it warm and fast. The whole core round should feel like two minutes, not an intake form.
Round 1: The Core (6 questions, required)
Open with one sentence: this takes about two minutes, sets up every skill, and only happens once.
- Church name. "What's your church's name?"
- Their name and role. "And your name, as you'd want it to appear in content? Plus your role, if you're not the lead pastor." (Executive pastors, worship pastors, and comms directors use these tools too. Capture the role so skills write from the right seat. If they aren't the lead pastor, ask the lead pastor's name as the natural follow-up.)
- Denomination or tradition. "What denomination or tradition are you part of? Totally fine to say nondenominational." Then set
TRADITIONfrom the answer using the presets in the pastor-foundation skill'sreferences/traditions.md: Foursquare, Assemblies of God and other Pentecostal or charismatic churches arepentecostal-charismatic; Presbyterian, Reformed and Reformed Baptist churches arereformed; Baptist churches arebaptist. If the answer is nondenominational or doesn't map cleanly, ask one follow-up: "Would you say your church leans Pentecostal or charismatic, Reformed, Baptist, or just broadly evangelical?" Methodist, Anglican, Lutheran and similar answers getother, with a line in Notes on anything distinctive. - Attendance. "About how many people attend on an average weekend?"
- Location. "What city and state?" If they only give a city, that's enough.
- Bible translation. "Which Bible translation do you preach from?" (Default: NIV.)
Round 2: The Context (optional, offered as one choice)
After question 6, offer it as a single yes/no: "That's the essentials. Want to answer 7 more so the tools really know your church? Takes two more minutes and makes every output sharper. Or we can stop here and add detail later."
If yes, one at a time:
- Community. "Tell me about your community. Urban, suburban, or rural, and anything that defines it: college town, military base, retirement area, tourist economy."
- Congregation. "Who actually fills your seats? Age mix, young families vs. seniors, long-timers vs. new believers, anything that shapes how you communicate."
- Season. "What season is the church in right now? Growing, plateaued, rebuilding, brand-new plant, fresh off a transition. Be honest, this stays on your machine."
- Ministries. "Any ministries or recurring programs the tools should know by name? Youth group name, kids ministry, small group system, food pantry, whatever comes up in your communication a lot."
- Voice. "When your church communicates, do you lean formal or casual? Any words or phrases you always use, or never use?"
- Leadership. "Who makes the big decisions: elders or a session, deacons, a church council, or a congregational vote?" (Letters about staffing, money and discipline often come from that body, and Baptist churches send big decisions to a members' meeting.)
- Links. "Last one. Your service times, website, and online giving link, if you have them?"
Writing the Profile
Write the answers to ~/.claude/pastor-profile.md in exactly this format. Omit any line the pastor skipped, except these three, which always get written: DENOMINATION (default Nondenominational), TRADITION (default evangelical) and BIBLE_TRANSLATION (default NIV).
# Church Profile
Used by all pastor-ai-skills. Edit anytime, or run /pastor-setup to update.
CHURCH_NAME: Grace Community Church
PASTOR_NAME: Pastor Mike
ROLE: Lead Pastor
DENOMINATION: Southern Baptist
TRADITION: baptist
POLITY: Congregational. Deacons serve; major decisions go to a members' meeting vote.
ATTENDANCE: 175
LOCATION: Tulsa, Oklahoma
BIBLE_TRANSLATION: ESV
COMMUNITY: Suburban, growing area on the north side of Tulsa, lots of young families moving in
CONGREGATION: Mix of young families and empty nesters, about a third are new to church in the last 3 years
CHURCH_SEASON: Growing, added a second service in January
MINISTRIES: Ignite Youth, Grace Kids, community groups (our small group system), Tulsa food pantry partnership
VOICE: Casual but reverent. We say "community groups" never "cell groups." Avoid churchy insider language.
SERVICE_TIMES: Sundays 9:00 and 11:00 AM
WEBSITE: gracetulsa.org
GIVING_LINK: gracetulsa.org/give
## Notes
Anything else the pastor wants every skill to know goes here.Add LEAD_PASTOR: <name> under ROLE when the person setting up isn't the lead pastor.
After Writing
Confirm with a short recap of what was saved and one example of how it gets used ("Every skill now writes as Pastor Mike of Grace Community Church, quotes the ESV, and knows your community groups by name"). Then suggest a natural first skill to try, like /church-email or /sermon-research.
Environments Without File Access
If the environment cannot write files (for example, a claude.ai project), run the same interview, then output the filled-in profile block and tell the pastor to paste it into their project instructions.
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.

