sermon-research
Skill56 starsChanged 4 days agoMITView on GitHub
Researches a scripture passage for preaching or teaching (context, background, word studies, commentary, cross-references, themes and interpretive questions) without writing or outlining the sermon. Use when the pastor says "research Romans 8:1-11 for Sunday", "give me background on this passage", "what do the commentaries say about John 4", "word study on this text", or "help me study Ephesians 2 before I preach it".
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
- pastor-setupSkill
- sermon-brainstormSkill
- sermon-feedbackSkill
- 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
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Very specific: line 21
Don't invent facts: no made-up quotes, statistics, stories, names, dates or church details.
- Distinctive: line 31
If the pastor asks a specific question ("what do I do with verses 34-35?"), answer it first in 3-5 sentences, above everything else, then …
- Distinctive: line 39
Read history plainly before asking what it means theologically.
- Distinctive: line 66
If everyone walks out feeling good, was the whole text preached?
- Distinctive: line 71
No sermon outline, point structure or suggested way to organize the message, even if asked.
≈ “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
Sermon Research
Compress the front end of study so the pastor spends the week thinking and praying, not hunting for background. Research only: keeping it separate from structure stops the pastor from preaching what they already believed instead of what the text demands.
<!-- 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 passage is enough; start without follow-up questions. Use anything else offered: the angle they're preaching through, the series and where this week falls, interpretive questions they're wrestling with.
If the pastor asks a specific question ("what do I do with verses 34-35?"), answer it first in 3-5 sentences, above everything else, then give the full research.
The research, in six steps
1. Context and background
Three or four dense, specific paragraphs to orient, not a general history lesson: author, date and recipients; genre (epistle, narrative, poetry, apocalyptic, wisdom) and how it shapes what the passage demands; where it falls in the book's argument or story, what came just before and what follows; who held power, the religious setting and practices like hospitality, honor and shame, patronage and purity. Flag two or three details a modern reader would read past that the original audience would have caught at once.
Read history plainly before asking what it means theologically. The census was a political act; the Temple was a real place with real commerce. Context is not a metaphor.
2. Key word study
Pick 3-5 words that carry theological weight, have a range of meaning that affects interpretation, or are translated inconsistently. For each, in a table: English word (in the profile's translation), transliteration, literal meaning, range of meaning elsewhere in Scripture, and how two contrasting translations render it. Only give a rendering you're sure of; otherwise write [check]. The aim is a better interpretive decision the pastor can explain without a seminary lecture.
3. Commentary insights
Draw on 3-5 commentators or traditions: the passage's main interpretive question and where scholars land, where they agree (a signal worth noting), where they diverge (usually a real tension in the text), and both technical and pastoral angles.
Name the commentators and the works. Don't invent commentary quotes or page numbers: summarize a commentator's overall reading, and say so when you're unsure what a specific commentator wrote. When a passage is contested, lay out the main views fairly, then say where the church's tradition usually lands and why. references/commentary-sources.md lists the sources to draw on.
4. Cross-references
Five to eight passages, each with the reference, one sentence on why it matters here, and its type: Direct parallel (same event or teaching from another angle), Thematic connection (develops the same idea) or OT background (a text the passage quotes, alludes to or assumes). Every one should earn its place: clarify a word, trace the theme across the canon, or give a second way into the same truth.
5. Theological themes
Three to five themes, each with a short name, where and how the passage develops it, and one practical implication for a local congregation: what question it answers, what fear it addresses, what obedience it calls for. A map of the terrain, not an outline.
6. Thinking prompts
Five to seven interpretive pressure tests, written for this passage, to push the pastor's thinking before any outline or illustration. The kind of thing to ask:
- What assumption will the congregation bring that the original audience wouldn't have had?
- Where is the natural application too easy, and where is it harder than it looks?
- What does this passage demand that people probably don't want to hear?
- If everyone walks out feeling good, was the whole text preached?
- What is the most common way this passage is mishandled from the pulpit, and how do you avoid it?
What to hold back
No sermon outline, point structure or suggested way to organize the message, even if asked. Structure belongs to the pastor's own prep.
Hard passages
If the passage involves violence, sexual abuse or other trauma, add a short pastoral-care note after the thinking prompts: survivors are likely in the room, children may be in the service, and the pastor may want to tell parents or the children's ministry ahead of time.
Verify before Sunday
End with 3-5 specific claims from the research that the pastor should check against a commentary or lexicon before preaching them: a word meaning, a commentator's position, a historical detail, a manuscript note.
Output
Give the research in chat with clear headings for the six sections, then the pastoral-care note if needed and the verify list. If the pastor asks for a PDF or printable copy, follow references/pdf.md.
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.

