midweek-devotional
Skill56 starsChanged 4 days agoMITView on GitHub
Writes a short midweek devotional (about 200-300 words) for the congregation's email, app or text. Use when the pastor says "write this week's devotional", "midweek devo on Psalm 46", "something encouraging to send Wednesday", "a short devotional tied to Sunday's sermon", or gives a verse or theme for a between-Sundays note.
In this repository18 other files it gives its agents.
- announcement-scriptSkill
- church-emailSkill
- church-letterSkill
- church-social-postSkill
- funeral-prepSkill
- meeting-agendaSkill
- pastor-foundationSkill
- pastor-setupSkill
- 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
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
- Very specific: line 21
Don't invent facts: no made-up quotes, statistics, stories, names, dates or church details.
≈ “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
Midweek Devotional
A short note from the pastor that lands on Wednesday: one passage, one honest thought, something to carry into the rest of the week.
<!-- 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
A verse, passage or theme is enough. Use anything else the pastor offers: the current sermon series, something the church or town is going through this week.
The voice
Write it the way a pastor texts a friend who's having a hard week. First person is good. Skip the greeting ("Happy Wednesday, church family!") and start inside a real moment the reader will recognize, like how Sunday's resolve tends to fade by midweek. Quote one to three verses in full and let them stand without a verse-by-verse breakdown. Then stay with one idea, tied to something concrete people are carrying this week rather than a thought that fits any week of any year. Give them one sentence worth remembering. End with a short prayer (we, us, our) or a blessing, not both, and with no sign-off after it.
Keep it to roughly 200-300 words, short paragraphs, no section labels in the finished piece. If the pastor mentioned the sermon series, one light line of connection is plenty ("We've been in Philippians on Sundays..."), unless they ask you to build the devotional on Sunday's text. It's a devotional, not a sermon or an announcement: leave events and promotions for the church email.
After a tragedy or a death
When the church or town is grieving: lament with them and don't explain why it happened. Name someone who died only if the pastor confirms the family is fine with it. Include the practical help people need this week (a prayer gathering, counselors at the school, who to call), even though it's an event.
Output
Give the devotional in chat, ready to paste. 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.

