sermon-to-blog

sermon-to-blog is a skill for Claude Code from tkcostello/pastor-ai-skills. It costs 27 tokens per session (1,549 once invoked), scanned A, original, MIT.

A guide for turning a preached sermon into a standalone blog post for a church website. It works from a transcript, recording notes, detailed outline, or key points.

In plain words
What is it for?
Use it to create a structured, web-ready article from sermon material, optionally shaped around a search topic or keyword.
Why use it?
It makes the sermon useful to people who were not at the service without simply publishing a raw transcript.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

Part of the pastor-skills plugin — 15 skills shipped together

Good fit Use it to create a structured, web-ready article from sermon material, optionally shaped around a search topic or keyword.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tkcostello/pastor-ai-skills/sermon-to-blog
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add tkcostello/pastor-ai-skills --skill sermon-to-blog
Clone the repo
git clone --depth 1 https://github.com/tkcostello/pastor-ai-skills

Made for: Claude Code.

Or install pastor-skills, the plugin that ships this one along with the rest of its 15 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sermon-to-blog

README.md
[![agentmods](https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/sermon-to-blog/github.svg)](https://agentmods.dev/skills/tkcostello/pastor-ai-skills/sermon-to-blog)
Your own site
<a href="https://agentmods.dev/skills/tkcostello/pastor-ai-skills/sermon-to-blog"><img src="https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/sermon-to-blog/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sermon-to-blog

Your own site · 80×15
<a href="https://agentmods.dev/skills/tkcostello/pastor-ai-skills/sermon-to-blog"><img src="https://agentmods.dev/badge/skills/tkcostello/pastor-ai-skills/sermon-to-blog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,549 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.01549
Opus 5 $0.00014 $0.00775
Sonnet 5 $0.00005 $0.00310
Haiku 4.5 $0.00003 $0.00155

Measured 13d ago against content hash 30e31687dedf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sermon-to-blog scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sermon-to-blog/SKILL.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sermon to Blog Post

Preach it once, publish it forever.

Before writing: follow the pastor-foundation skill and load the church profile from ~/.claude/pastor-profile.md. If the profile file is missing, run the pastor-setup skill first.


What This Skill Does

You preached a sermon. Maybe it was great. Maybe it was the best thing you've said from the pulpit all year. And now it's sitting in a folder somewhere as a transcript or a set of notes, doing nothing for the people who weren't in the room.

This skill turns that sermon into a standalone, web-ready blog post that works for someone who has never heard you preach. Not a transcript dump. Not a summary. A real article, structured for reading, optimized for search, and written in your voice.


Input

Provide one of the following:

  • Full sermon transcript (preferred)
  • Recording notes or detailed outline with key points and illustrations
  • Bullet points covering the main ideas, scripture references, and any stories you told

Optional but helpful: A target keyword or topic angle for SEO (e.g., "how to overcome anxiety as a Christian" or "what the Bible says about forgiveness").

If you don't provide a keyword, one will be identified from the sermon content.


Workflow

Step 1: Extract the Core Message

Before writing a single word of the post, identify:

  • The big idea. One sentence. What is this sermon actually about? Not the title, not the passage. The transferable truth.
  • The strongest illustration. One story, analogy, or real-world example from the sermon that will translate well to reading (not all illustrations work the same way in print).
  • The 3-4 most practical takeaways. What can someone actually do, think differently about, or believe differently because of this content?
  • The primary scripture. The passage the whole message hangs on.

This step determines the structure. A blog post is not a transcript. It is a distilled, restructured version of the sermon's best content, rebuilt for a reader who is skimming on a phone at 7am.

Read the full file on GitHub · 170 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 170 lines · 27 tokens per session scan A 30e31687dedf

Subscribe to this mod's changes

sermon-to-blog is a skill published in the GitHub repository tkcostello/pastor-ai-skills (52 stars, last pushed 15d ago), licensed MIT. It adds 27 tokens to every session and 1,549 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens