sermon-to-blog
Skill56 starsChanged 4 days agoMITView on GitHub
Turns a preached sermon (transcript, notes or outline) into a standalone, search-friendly blog post for the church website. Use when the pastor says "turn Sunday's sermon into a blog post", "make this transcript a blog", "write up my message for the website", "blog version of this sermon", or pastes sermon notes and asks for an article.
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-researchSkill
- sermon-seriesSkill
- 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
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 37
Write in the pastor's own first person ("I"), as a post under their name, unless they ask for something else.
≈ “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 to Blog Post
Rebuild the sermon as an article for someone who never heard it, reading on a phone. It is not a transcript, and it is not a summary of the service.
<!-- 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 transcript is best; notes or an outline with the main points, scripture and stories will do. Use a target keyword if the pastor has one. If not, pick the plain phrase a person would actually search for this topic ("what the Bible says about forgiveness") and say which you chose.
Find the core first
Before drafting, pull out the big idea in one sentence (the transferable truth, not the sermon title or passage), the one passage the message hangs on, the illustration that will work in print, and the three or four takeaways a reader can act on. Those decide the structure. Leave the rest of the sermon behind.
Writing it for readers
Write in the pastor's own first person ("I"), as a post under their name, unless they ask for something else. Never narrate the pastor in the third person ("Pastor Mike tells a story...").
- Title. Name the question or truth, not the series ("The Anchor Holds, Week 3" means nothing to a searcher). Keep it around 60 characters so it isn't cut off in search results, with the keyword in it naturally. Offer three and recommend one.
- Meta description. About 150 to 160 characters saying what the reader gets, in a human sentence.
- Opening. Two or three sentences that start where the reader is: a tension, a question, a moment they'll recognize. Don't open with "Last Sunday I preached," the sermon title, a block of scripture or "In this post we'll explore." Someone arriving from search doesn't know or care that it was a sermon yet.
- Body. Three or four sections with H2 subheadings that say something, one sermon point each. Weave scripture in by phrase and reference rather than block-quoting every point. Retell stories for the page: spoken stories carry setup and repetition that drag in print, so tighten them and lead with what matters. Short paragraphs, bold used rarely, bullets only for real lists.
- Close. One clear takeaway and one specific thing to do today (not "spend time in prayer this week"). End on a line that lands. Skip "In conclusion."
- Length. About 800 to 1,200 words. If it runs long, cut; a reader who finishes is worth more than one who quits halfway.
Adapt altar-call language ("if you're ready to give your life to Jesus tonight") into an invitation that fits a reader: talking with a pastor, or visiting, using the profile's service times and website. Leave out response steps that only worked in the room or on the livestream ("come to the front," "text HOME to..."). Use the keyword a few times where it reads naturally and nowhere it doesn't.
Output
In chat: the recommended title with two alternatives, a short URL slug (older-brother-prodigal-son), the meta description, the full article with H2 subheadings ready to paste into WordPress or any CMS, ending with a line pointing to the full message at [sermon video link], a featured-image idea (a real church photo beats stock) with one sentence of alt text, and a one-line SEO note naming the primary keyword and any secondary terms that came up naturally. List any stories you flagged for the pastor's OK.
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.

