Pastor Setup logo

Pastor Setup

Community
tkcostello
pastor-setup

Use when setting up pastor-ai-skills for the first time, when a pastor wants to view or change their church profile (church name, denomination, attendance, congregation, community, Bible translation), or when any pastor skill cannot find the church profile file at ~/.claude/pastor-profile.md.

Overview

Publishertkcostello
Repositorypastor-ai-skills
Skill namepastor-setup
Stars
56
Forks
34
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by tkcostello on GitHub. Read the source before you install it.

Installation

Install the Pastor Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/tkcostello/pastor-ai-skills/tree/main/skills/pastor-setup
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/tkcostello/pastor-ai-skills.git /tmp/pastor-ai-skills
mkdir -p .claude/skills
cp -r /tmp/pastor-ai-skills/skills/pastor-setup .claude/skills/pastor-setup
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Pastor Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Pastor Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Pastor Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

  1. Checks whether ~/.claude/pastor-profile.md already exists.
  2. If it exists: show the current values and ask what to change. Update only what the pastor asks to change.
  3. If it does not exist: run the interview below.

Interview Rules

These rules are non-negotiable:

  • 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.

  1. Church name. "What's your church's name?"
  2. 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.)
  3. Denomination or tradition. "What denomination or tradition are you part of? Totally fine to say nondenominational." (Default: nondenominational evangelical.)
  4. Attendance. "About how many people attend on an average weekend?"
  5. Location. "What city and state?" If they only give a city, that's enough.
  6. 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 5 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:

  1. Community. "Tell me about your community. Urban, suburban, or rural, and anything that defines it: college town, military base, retirement area, tourist economy."
  2. Congregation. "Who actually fills your seats? Age mix, young families vs. seniors, long-timers vs. new believers, anything that shapes how you communicate."
  3. 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."
  4. 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."
  5. Voice. "Last one. When your church communicates, do you lean formal or casual? Any words or phrases you always use, or never use?"

Writing the Profile

Write the answers to ~/.claude/pastor-profile.md in exactly this format. Omit any line the pastor skipped, except DENOMINATION and BIBLE_TRANSLATION, which always get written with their defaults if skipped.

markdown
# 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
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

## Notes
Anything else the pastor wants every skill to know goes here.

SERVICE_TIMES and WEBSITE were not interview questions. If they came up naturally, save them. Otherwise leave them out.

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.

Frequently asked questions

What does the Pastor Setup AI skill do?

Use when setting up pastor-ai-skills for the first time, when a pastor wants to view or change their church profile (church name, denomination, attendance, congregation, community, Bible translation), or when any pastor skill cannot find the church profile file at ~/.claude/pastor-profile.md.

Why use Pastor Setup on TypingMind?

Because you install it once and use it with any model. Pastor Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Pastor Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/tkcostello/pastor-ai-skills/tree/main/skills/pastor-setup. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Pastor Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Pastor Setup?

As many as you like. As long as a model supports skills, you can use Pastor Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Pastor Setup AI skill free?

Yes. It is published on GitHub by tkcostello under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇