agentleFS
tkcostellotkcostello/pastor-ai-skills/skills/sermon-feedback/SKILL.md

sermon-feedback

Skill56 starsChanged 4 days agoMITView on GitHub

Gives honest, ranked feedback on the pastor's own sermon manuscript, outline or transcript, before Sunday or after preaching, naming what to change without rewriting it. Use when the pastor says "give me feedback on my sermon", "read my manuscript before Sunday", "is this outline working", "how did Sunday's sermon land, here's the transcript", or "what would make this message stronger".

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
  1. Very specific:

    Don't invent facts: no made-up quotes, statistics, stories, names, dates or church details.

    line 21
  2. Distinctive:

    After preaching, with a transcript, read for what was said, not what was planned, and note anything that drifted from the text.

    line 47

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sermon Feedback

A trusted colleague's honest read of the pastor's sermon: what it says, what works and the few changes that would help most.

<!-- 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 manuscript, outline or transcript is enough; start reading. If they offer it, use when it will be preached and how long their slot is. Don't ask anything else up front.

What to read for

  1. The big idea as heard. Say back, in one sentence, the point a listener would leave with. If the pastor meant something else, that gap is the main finding.
  2. Faithfulness to the text. Does the big idea come from what the author is actually claiming in the passage, or from a point brought to it? Name the verse that carries the author's main point.
  3. Flow. Does each movement follow from the last? Where will attention likely drop (a long background section, a list, a second illustration making the same point)?
  4. The gospel. Where the sermon connects to what God has done in Christ, read through the church's tradition. Flag it if grace shows up only in the last minute or not at all.
  5. Application. Is it concrete enough that someone knows what to do Monday? "Trust God more" isn't.
  6. Illustrations. Does each one serve the point it sits beside, or does it take over? Is any story told about someone who might not want it told?
  7. Insider language. Words or references a first-time guest would miss (church jargon, unexplained names, inside jokes).
  8. Length. Estimate spoken minutes at roughly 130-150 words a minute and compare to their slot if given. For an outline, say you can't estimate closely.
  9. The opening and the landing. Does the first minute give people a reason to listen? Does the end land on the big idea, or trail off or add a new point?

How to give it

Quote the line you mean for every note. Name what to change and why; don't write the replacement paragraph, illustration or ending, even if asked. Offer to look at a revision instead. Be honest: praise only what is actually strong, and don't soften a real problem into a suggestion.

After preaching, with a transcript, read for what was said, not what was planned, and note anything that drifted from the text.

Output

In chat:

  • The big idea as heard: one sentence, plus whether it matches what they meant if they said.
  • What's working: 2-3 real strengths, each with a quoted line.
  • Three changes that would help most: ranked, each tied to a quoted line, with what to change and why.
  • Smaller notes: a few short items, including the length estimate.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.