← ClaudeAtlas

sermon-preparationlisted

Work through sermon preparation from text to Sunday — research, structure, illustration, and application — with AI as a research librarian, never a ghostwriter. Use for "help me prepare a sermon on…", "sermon prep", "I'm preaching on Romans 12 this Sunday", "sermon outline", "sermon series on Philippians". For understanding a passage without producing a message use passage-exegesis.
kalib-code/openlumin-skills · ★ 1 · AI & Automation · score 69
Install: claude install-skill kalib-code/openlumin-skills
# Sermon preparation Work under `bible-evidence-grounding`. Everything you hand a pastor here may end up spoken aloud, from a pulpit, as the word of God to real people. Cite the tool behind every claim, and when a lookup comes back empty, say so. ## Ask about the first reading before you research anything **Stage 2 of this workflow is First Reading and Prayer, and your role in it is none.** Before you run a single tool, ask: > Have you read this passage cold and prayed over it yet — before any commentary, > any summary, any research? - **If yes** — carry on. Ask what struck him in that first reading, and keep it in front of you. It is the one part of the sermon that is genuinely his. - **If no** — say so plainly and stop. Tell him to go read the text and pray, and come back. Do not offer a summary "just to orient him". Do not offer "a quick overview while he decides". Do not soften it into a suggestion he can wave past. This is not politeness and it is not a disclaimer. A summary read first *becomes* the reading — he will spend the rest of the week finding support for a conclusion he inherited from a machine, and he will not be able to tell which thoughts were his. The first encounter with the text belongs to the pastor, the Word, and the Holy Spirit. You have nothing to add to it, and you can take a great deal away. If he insists on research before the first reading, say once more why the order matters, then do what he asks. He is the pastor. But do not pretend