Church Communicator's Playbook ← Back to Main
See It In Action

Every skill. Real input. Real output.

If you’re curious (or a little skeptical) about what AI could actually do for your church’s communication, you’re in the right place. This page is a look behind the curtain at all 24 skills in the pack, tested on real church scenarios, so you can see exactly what goes in and what comes out before you try it yourself.

24/24
Skills tested
6
Categories
5
Skills working together
2
Safety checks confirmed
Start here

Short on time? See these 3 first.

The fastest way to see if this is for your church: three demos that show the range, from a five-minute copy fix to a system that runs your whole Monday.

How this was tested

One church. One busy season. All 24 skills.

Every test uses the same fictional church so you can see the pack working as a system: Grace Community Church (about 600 people, an active ministry calendar, and one part-time communications coordinator). The scenarios are grounded in reality: the marriage class, the Serve Day campaign, the overloaded announcement slide, and the Saturday-morning intake problem all come straight from the book.

1 · Draft the input

A realistic raw submission, request, or scenario, the kind that actually lands in a church communicator’s inbox, adapted from the book’s case studies.

2 · Run the skill

The skill was run in Claude exactly as a customer would run it, with Grace Community’s voice profile loaded. Outputs are the skill’s own work.

3 · Capture before & after

Inputs and outputs reproduced below. Longer system outputs are excerpted where marked; nothing shown was rewritten after the fact.

A quick note on how the AI “remembers” things: All of these tests happened in one ongoing conversation with Claude. That’s why later skills could build on earlier decisions — like reusing a real couple’s story in a later email, or remembering that a sensitive request (a grief support group) shouldn’t go on the big screens up front. It works the way you’d expect a conversation to work: the AI remembers what you already told it, as long as you’re still in that same conversation. Claude, ChatGPT, and Gemini each have a way to keep a conversation and its memory going over time so you don’t lose that context — Claude calls it a Project, ChatGPT has Custom GPTs and Projects, and Gemini has Gems. Whichever one your account offers, keeping related work together there is what lets these skills build on each other the way you see below.

Category 014 skills

Copy & Editing

The daily workhorses: raw ministry copy in, clear communication out: built on the book’s core writing rules (keep it simple, keep it clear, keep it consistent) and its approach to telling a good story.

simplify-the-announcement

Simplify the Announcement

Ch. 2 · Headline → Next Step → Details

Rewrites raw, enthusiastic ministry submissions into announcements a normal person understands in ten seconds.

Input — raw ministry submission
Family Ministry, via email, Tuesday 9:14 p.m.

“Hey!! So excited to share that Family Ministry is once again hosting our annual Trunk-or-Treat outreach extravaganza!!! It’ll be October 31st from 5:30–7:30pm in the main parking lot and we need families to decorate trunks and hand out candy, plus we’ll have a chili cook-off, bounce houses, and a photo booth! If you want to decorate a trunk sign up on the Church Center app, or you can email Dana, or just stop by the Family Ministry table! Invite your neighbors!! Candy donations can go in the bins in The Commons starting the 12th!”

Output — the skill’s rewrite

Trunk-or-Treat: the easiest invite of the year

Friday, October 31, 5:30–7:30 PM in the main parking lot — candy, chili, bounce houses, and a parking lot full of neighbors.

Want to host a trunk? Sign up at gracecc.org/trunk by October 24.

Free and open to everyone — just show up. Candy donations welcome in The Commons starting October 12.

What changed and why

  • Three competing CTAs (app, email Dana, visit table) → one primary action with one path
  • Headline leads with the human benefit (easy invite) instead of the event name
  • Attendee info separated from volunteer ask — two audiences, sequenced
What to noticeThe skill ran the five-question Simplicity Filter, then rebuilt the copy as Headline → Next Step → Details, and explained its edits so the communicator learns the pattern. Every date and fact preserved exactly.
decode-the-churchese

Decode the Churchese

Ch. 2 · The Simplicity Filter

Reads copy the way a first-time guest would, flags insider language, and offers plain-language alternatives.

Input — newcomer welcome email draft

“We’re so glad you visited! We’d love for you to take your next step by joining our Connect Track, meeting in the Fellowship Hall after second service. It’s the best way to start doing life together with our church family. Kids are welcome in KidZone, where our team will love on them while you attend. Questions? Stop by Guest Central in the narthex!”

Output — flags + revision
FlaggedSuggestedA first-timer reads…
“Connect Track”“a one-hour welcome class”A program name with no meaning yet
“after second service”“at 12:15, right after the 11:00 service”How many services are there?
“doing life together”“getting to know people here”Sounds warm, but a newcomer wouldn’t know what it means
“love on them”“take great care of them”Unfamiliar, slightly odd phrasing
“the narthex”“the lobby”A word they have never seen

Revised: “We’re so glad you visited! If you’d like to get to know Grace, join us for a one-hour welcome class this Sunday at 12:15, right after the 11:00 service, in the room just off the lobby. Kids are welcome next door in KidZone, where our team will take great care of them. Questions? Look for the Guest Central desk in the lobby — we’d love to meet you.”

Ten-second test: passes — a guest knows what, when, where, and what to do with their kids in one read.

What to noticeThe skill knew the difference between replacing a word and explaining one: it kept the KidZone ministry name (Grace uses it on signage) but translated everything else a guest wouldn’t know. “If a guest needs it explained twice, we’ve lost them.”
trifecta-edit

Trifecta Edit

Ch. 2 · Simple / Clear / Consistent

The full pre-publish check: figures out which of the three (simple, clear, consistent) is missing, then fixes it. Input adapted from the book’s “Event That Was Good… But Confusing” case study.

Input — Serve Day promo email

“Serve Day is coming! Join us as we love our city through food packing, campus cleanup, serving at Maple Street Elementary, and neighborhood outreach. Sign up for food packing here, campus cleanup here, Maple Street here, or neighborhood outreach here. You can also get involved by donating supplies (see list) or praying for the day. Get involved!”

Output — diagnosis + edit

Bottom line: Simple — pass, barely (readable, but five links create overload). Clear — fail (no defined win; “Get involved!” isn’t an action; four competing sign-ups). Consistent — fail (three different call to action verbs across the piece).

Edited version:

Serve Day — Saturday, April 26

One morning, four ways to love our city: food packing, campus cleanup, Maple Street Elementary, or neighborhood outreach.

Pick your project and register at gracecc.org/serveday — it takes about sixty seconds, and you’ll get a confirmation email with everything you need.

Change log

  • Clear: defined the win (people registered to a project), collapsed five links into one landing page with one call to action — “pick a project and register”
  • Clear: added “what happens after” (confirmation email) — the Clarity Check’s most-skipped question
  • Consistent: one call to action verb (“register”) — supplies and prayer moved to the landing page as secondary options
What to noticeThis mirrors the book’s actual case study resolution: one landing page, one next step, consistent wording, where the real-world version saw sign-ups rise and “What do I do?” emails stop.
story-first-rewrite

Story-First Rewrite

Ch. 4 · Four-Step Story Framework

Turns a plain schedule-and-price announcement into one that speaks to a real need people have. Input is the book’s best example: a class promo that ran unchanged for three years, until this kind of rewrite doubled sign-ups.

Input — the promo as submitted

“Marriage Renewal Class. Six weeks. Begins March 10, 6:30 PM, Room 204. $25 per couple, includes workbook. Register online.”

Accurate. Complete. Nobody signed up because of it.
Output — story-first version

“Every marriage has seasons where the conversations get shorter and the distance creeps in quietly. Nobody plans for that season — but you don’t have to stay in it.

Marriage Renewal is a six-week class that helps couples reconnect — not with a quick fix, but with honest conversation and practical rhythms that actually stick.

Six Tuesdays starting March 10, 6:30 PM · $25/couple · Register at gracecc.org/marriage

The need, named

“Couples drifting into distance and short conversations” — confirm with the ministry leader that this is the real, honest center of the class.

Story ask (no testimony on file — nothing was invented)

  • “What was your marriage like the month before you signed up?”
  • “What’s one moment from the class you still think about?”
  • “What would you say to a couple deciding whether to come?”
What to noticeThe skill skipped the “share a real story” step because there wasn’t a real one on file yet; instead it wrote the interview questions needed to get one. Handled correctly  It will never make up a quote. Either the quote is real, or it's left out.
Category 023 skills

Brand Voice

One church, one voice. These skills build Grace Community’s voice profile, keep drafts on-brand, and help everyone else write in that same voice, putting the book’s four consistency principles into daily practice.

load-your-church-voice

Load Your Church’s Voice

Ch. 2 · Language & ToneFeeds every other test

The skill you run first: looks at real samples of your writing plus a short interview, and builds the voice profile every other skill checks before it writes anything.

Input — samples + interview

Three samples supplied: a warm weekly-email intro (“Sunday’s coming, and there’s a seat with your name on it…”), a stiff building-update announcement, and an Instagram caption from Serve Day.

Interview answers: “We’re the church down the street that actually knows your name.” Always: warm, plain, invitational. Never: hype, guilt, churchy. We say Grace Kids, The Commons, “register at gracecc.org/events.” We avoid fellowship, narthex, unexplained acronyms.

Output — church-voice-profile.md (condensed)

Who we are: The church down the street that actually knows your name. We’d rather sound like a friend texting you than a brand welcoming you.

Tone — always: warm (contractions, first names), plain (one idea per sentence), invitational (“join us” not “don’t miss”). Never: hype (one exclamation point per piece, max), guilt (“we missed you” is banned), churchy (no unexplained insider terms).

How we sound: Short sentences with a human beat. “Sunday’s coming, and there’s a seat with your name on it” — yes. “Attention congregation” — never.

Words we use: Grace Kids · The Commons · “register at gracecc.org/…” Avoid or explain: fellowship → connect · narthex → lobby.

Rhythms: Email lands Wednesday 10 AM. Two stage announcements max. Story post every Friday.

Voice test passed: sample announcement rewritten in profile voice; approved on second revision (“yes, that’s us”).

What to noticeThe skill compared the samples to the interview answers; it noticed the stiff building announcement didn’t match and asked which one actually sounded like Grace. Every test after this one in this report runs with this profile loaded.

Using ChatGPT or Gemini instead of Claude? You may not be able to save a file and have the AI “read” it back later the same way Claude can. Instead, just copy this text and paste it into your Custom GPT, Project, or Gem (each platform has a spot for background info like this) — or paste it straight into your chat before you ask for anything else. Either way works fine; it just makes sure the AI has your church’s voice in front of it before it starts writing.
voice-check

Voice Check

Ch. 2 · Consistency AuditUses profile from test 5

Checks any draft against the voice profile, line by line: how fifteen different people can write for the church and it still sounds like one voice.

Input — student ministry volunteer’s draft

“ATTENTION PARENTS!!! Don’t miss out on Fall Retreat registration!!! It is mandatory that all forms be submitted by the 15th!! Students who fail to register on time will not be able to utilize the early-bird rate. Forms are in the narthex. Don’t let your student miss the best weekend of the year!!!”

Output — audit + correction

Bottom line: doesn’t sound like us — too much hype, guilt-tripping, and two words we don’t use. The information underneath is good.

FlaggedIssueFix
“ATTENTION PARENTS!!!”Hype (never-word); 9 exclamation points vs. profile max 1“Parents — one quick date for you”
“Don’t miss out” / “fail to register”Guilt-tripping (we don’t do this)Warmer: “register by Oct 15 to get…”
“utilize”Too formal for our voice“get”
“in the narthex”Avoid-list term“in the lobby”

Corrected: “Parents — one quick date for you: Fall Retreat registration closes October 15, and registering by then gets you the early-bird rate. Grab a form in the lobby or register at gracecc.org/retreat. It really is the best weekend of the year — we’d love your student there.”

Profile gap logged: no guidance yet for genuine-urgency situations — suggest adding a “how we do deadlines” line to the profile.

What to noticeThe skill preserved every fact and the volunteer’s genuine enthusiasm (“best weekend of the year” survived); it corrected drift, not personality. It also fed a gap back into the living profile.
ministry-style-guide

Ministry Style Guide

Ch. 2 + 6 · Written Guidelines

Drafts the one-page guide that equips ministry leaders to communicate well without the comms team: answers to the questions people ask anyway.

Input — the request

“I need something I can hand ministry leaders. Recurring problems: flyers with five fonts, requests arriving days before events, and three different registration platforms in use. We have Canva templates and a request form. Keep it to one page — they won’t read more.”

Output — the guide (excerpt of 6 sections)

How Grace Communicates — a one-page guide

Our voice in 60 seconds. Warm, plain, invitational. One exclamation point max. Say “connect,” not “fellowship.” Example call to action: “Register at gracecc.org/events — takes about a minute.”

What good looks like. Every piece: Headline (human, not a flyer title) → one Next Step → the two or three details people need now. One call to action per piece — if everything is bold, nothing is.

The practical rules. Start from a Canva template (link) — fonts and colors are already decided for you. All event sign-ups run through Church Center. Logo files live in the Toolkit folder.

Lead times. We build it: 6–8 weeks. We build it together: 3–4 weeks. You build it with our templates: days. Submit at gracecc.org/commrequest.

When to loop us in. Anything churchwide, anything public-facing beyond your ministry, or anytime you’re unsure. We’re a guide, not a gate.

Delivered with a 3-sentence cover note framing the guide as a toolkit, not a policy rollout.

What to noticeThe guide itself models the voice it teaches, and it stayed on one page. “Guidelines are answers to questions, not rules.”
Category 033 skills

Story & Campaign

People rarely change their lives because of an announcement, but they frequently change their lives because of a story. These skills find the story, aim it, and build campaigns around it.

story-gatherer

Story Gatherer

Ch. 4 · Share Evidence of TransformationCloses the loop from test 4

Builds the interview questions that pull out a real story, then turns the raw answers into copy you can publish, in the person’s own words.

Input — raw interview notes (marriage class couple)

“Mike & Jen R., did the class last spring. Jen: ‘honestly we weren’t in crisis, we were just… roommates? like the calendar ran the marriage.’ Mike said week 3 exercise (‘the 10-minute check-in’) is the thing they still do every night. Jen: ‘it gave us our conversations back.’ Both said they almost didn’t sign up because $25 felt like admitting something was wrong.”

Output — shaped story, three sizes

Pull quote: “We weren’t in crisis — we were just roommates. This class gave us our conversations back.” — Jen R. (her exact words, unchanged)

Paragraph (email/web): Mike and Jen almost didn’t sign up — registering felt like admitting something was wrong. Nothing was “wrong.” The calendar had just quietly taken over their marriage. Six weeks later, the ten-minute check-in they learned in week three is something they still do every night. “It gave us our conversations back.”

Approval note (auto-included): “Before this publishes anywhere: send both versions to Mike & Jen, confirm they approve the wording — especially ‘roommates’ — and ask which name format they prefer.”

What to noticeEverything quotable came straight from the notes; the skill marked which words were exact and which were reworded, and it built in a step asking the couple to approve it before it’s published. This story is used again in tests 13 and 16.
value-filter

Value Filter

Ch. 4 · The Value Filter

Three questions before anything becomes a slide, email, or post: Who is this actually for? What problem does it solve? Is this the right channel?

Input — the request

“Our GriefShare group starts in three weeks. Can we get a Sunday stage announcement and a churchwide email? People need to know this exists.”

Output — the three questions, answered

1 · Who is this actually for? People in a specific season of loss — not the whole congregation. Broadcasting it churchwide makes it feel generic exactly when the right person needs it to feel personal.

2 · What problem does it solve? “Grief doesn’t keep office hours, and most people carrying it feel like they should be ‘over it’ by now.” That’s the language the promotion should use.

3 · Right channel? Not the stage. Better: the care page, a card pastors can hand someone, the email’s quieter middle section, and a note to group leaders — the people most likely to know who’s grieving.

Recommendation: Keep this small and personal — reach people through leaders and caring conversations, not a broadcast. Better opening line: “If this year has carried a loss, you don’t have to carry it alone — a new GriefShare group starts March 4.”

Win-win reply included: “I love that you want people to find this — let’s make sure the right people do. Here’s what I’d suggest instead of the stage…”

What to noticeThe skill said no to the churchwide ask and gave the ministry a better plan plus kind wording to deliver it with; it fits the right people, not just the biggest audience, which is the book’s point in Chapter 3.
campaign-builder

Campaign Builder

Ch. 2–4 · Levels + Story + One call to action

Turns a churchwide moment into a full multi-week plan: one story, one call to action, sequenced across the right channels.

Input — the brief

“Fall series ‘Everyday Faith’ launches Sept 13, six weeks. Win: 150 people join a small group during the series. Call to action: gracecc.org/groups. We have 7 weeks of runway, all channels, one designer 5 hrs/week.”

Output — campaign one-pager (excerpt)

Story frame: Faith that only happens on Sunday runs out by Tuesday. Everyday Faith is about the other six days — and nobody builds an everyday faith alone. Spine call to action (identical everywhere): “Join a group at gracecc.org/groups.”

WeeksPhaseFocus
-2 → 0AwarenessStory posts: real group members, the “Tuesday problem” named. No call to action push yet.
1 → 3InvitationStage (2 of 3 allotted mentions), email above the fold, testimony post, landing page live.
4 → 6ActionDeadline framing: “groups close Oct 18” — final stage mention, what-happens-after copy.

Copy starter (stage, week 1): “Be honest — how’s the faith thing going on, say, a Tuesday? [PAUSE] That’s what this series is about…”

Full output also includes: channel map with the email/social/screens cadence, six copy starters, and an asset checklist with two lead-time flags (group-leader photos needed by Aug 30; landing page live before first stage mention).

What to noticeOnly three stage mentions across six weeks; the skill treated stage time as the book advises (limited and valuable, so don’t overuse it) without being told to, and every asset carries the same seven-word call to action.
Category 045 skills

Email & Social

The weekly volume work: the newsletter people actually read, the targeted email that gets replies, and social that stays 70% story. One skill per channel, on purpose.

newsletter-writer

Newsletter Writer

Ch. 3 · The three-tier email

Turns the week’s pile of submissions into a ninety-second email: churchwide on top, people groups in the middle, ministry bullets at the bottom.

Input — seven raw items, as submitted
  • Serve Day registration open (Apr 26)
  • “Everyday Faith” series starts Sunday
  • Men’s breakfast Saturday 8 AM
  • GriefShare group starting (from test 9)
  • Grace Kids needs 6 fall volunteers
  • North lot closed Sunday (repaving)
  • Youth car wash fundraiser
Output — the assembled email (structure shown)

Subject options: “A seat, a series, and a Saturday that serves” · “Everyday Faith starts Sunday — here’s your week” · “This Sunday: new series (and park in the south lot)”

Top — churchwide: Everyday Faith launch (one call to action: “bring somebody Sunday”) · Serve Day (“pick your project” — gracecc.org/serveday). Parking note as a one-liner under the Sunday block.

Middle — people groups: Men: breakfast Saturday (“no sign-up, just show up”) · Parents: Grace Kids team ask, story-flavored, linking to the volunteer email.

Bottom — more ways in: GriefShare (the quiet, personal line from test 9) · youth car wash — one line each, links out.

Demotions explained: “Car wash is Level 3 (youth families are reachable directly) — bullet, not feature. GriefShare stays low and personal by design, per the Value Filter recommendation.”

Read-aloud time of full draft: 84 seconds. Nothing submitted was dropped.

What to noticeNothing got cut; every item just got the right amount of space, and the skill gave Emily plain reasons she can repeat to ministry leaders if they ask why. This is the book’s three-part email structure, in action.
ministry-email-writer

Ministry Email Writer

Ch. 2–4 · One audience, one ask

Single-purpose emails to targeted lists: the volunteer ask, the invite, the follow-up. Real role, real time cost, real impact.

Input — the brief

“Grace Kids needs 6 new volunteers before fall kickoff. Send to: parents of Grace Kids families. From: Dana (kids director). Role is one Sunday a month, 9:00–12:15, always paired with an experienced leader. Background check required.”

Output — the email

Subject: “One Sunday a month. That’s the whole ask.”

Hi [first name],

Every Sunday, your kids walk into a room where somebody knows their name, learns what they’re into, and tells them about Jesus at their level. Here’s the honest math: keeping those rooms great this fall takes six more adults.

The ask is one Sunday a month, 9:00–12:15. You’re never alone — you’ll be paired with an experienced leader, and we handle the background check and training.

Ready, or just curious? Reply to this email or sign up at gracecc.org/gracekids-team.

You’ve seen what this team does for your kids. Come be that for somebody else’s. — Dana

147 words. One call to action, stated twice. Send timing note: Tuesday morning, three weeks before kickoff, with a single reply-nudge the following week.

What to noticeIt names the role, the time it takes, and why it matters: the book’s fix for a vague ask that nobody responds to. It’s signed by a real person, because people reply to people.
social-copywriter

Social Copywriter

Ch. 3–4 · 70% story / 30% promoUses testimony from test 8

Platform-specific social copy that keeps church social what it’s for: spaces and faces, not a flyer rotation.

Input — two asks

1) Story post from Serve Day: 214 people, 9 sites; best moment — a retired teacher and a third-grader reading together at Maple Street Elementary (photo, permissions confirmed).

2) Promo post for the Marriage Renewal class (testimony from test 8 approved).

Output — two posts, labeled

Instagram — STORY: “She taught third grade for 31 years. Saturday, she got one more student. [line break] 214 of you spent the morning across 9 sites in our city — packing food, painting, planting, reading. Church isn’t just where we sit. It’s where we show up. 💛” Visual: the reading photo, uncropped.

Instagram — PROMO (story-led): “‘We weren’t in crisis — we were just roommates.’ That’s how Jen described year nine. Six weeks later, she and Mike had their conversations back. Marriage Renewal starts March 10 — join them. Register at gracecc.org/marriage.” Visual: Mike & Jen, natural light, no stock.

Facebook variants included with fuller sentences and a share-friendly closing question. Mix check: this week’s feed runs 3 story / 1 promo.

What to noticeEven the promotional post opens with a real person’s real sentence (approved in test 8), and the skill kept track of how many story posts vs. promo posts were in the feed as it wrote.
social-planner

Social Planner

Ch. 2–4 · Rhythm consistency

A monthly calendar with recognizable content categories, sized to what one communicator can actually sustain.

Input — October brief

“Capacity: 3 posts/week, Instagram + Facebook. On the calendar: Everyday Faith continues, Trunk-or-Treat Oct 31, Grace Kids volunteer push. Photo library is thin. What’s been dying: event flyers as posts.”

Output — plan (excerpt)

Recurring categories: Faces of Grace (Mon — one person, one quote) · Tuesday Takeaway (series quote card) · Friday Story (the week’s best moment) · Invite Slot (promo, max 1/week).

DateCategoryTopicAsset
Oct 6Faces of GraceGreeter team’s 20-year memberneed photo — gather Sunday
Oct 7TakeawaySeries week 4 quotetemplate — have
Oct 10Friday StoryGrace Kids volunteer “why I serve”need quote — ask Dana
Oct 13Invite SlotTrunk-or-Treat host pushcopy from channel-adapter

Mix: 13 posts planned — 9 story / 4 promo (69/31). Gathering list: one photo session after second service Oct 5 covers three slots.

Every slot marked skippable-without-guilt; plan holds at 2/week if a season gets heavy.

What to noticeThe skill planned the gathering, not just the posting: one Sunday photo session covers three slots. Each category has a name people will recognize week to week, so followers learn what to expect.
channel-adapter

Channel Adapter

Ch. 2 · Repeat the next step everywhereContinues test 1

One approved message → every channel, same story, identical call to action. The fix for “the slide says learn more, the email says register.”

Input — the message spine (from test 1)

Trunk-or-Treat · Oct 31, 5:30–7:30 PM, main lot · need trunk hosts · call to action: “Sign up to host a trunk at gracecc.org/trunk” · channels: email, Instagram, stage (30s), web, slide.

Output — five versions (condensed)

Email block (68 words): “The easiest invite of the year… Sign up to host a trunk at gracecc.org/trunk.”

Instagram: “Your trunk. Two hours. A parking lot full of neighbors who now know a church that knows their name. Sign up to host a trunk at gracecc.org/trunk.”

Stage (30s, 74 words): “If you’ve ever wished inviting your neighbors to church felt… easier — [PAUSE] — it’s about to. October 31, our parking lot fills with trunks, candy, and chili… Here’s what to do: sign up to host a trunk at gracecc.org/trunk.”

Slide: TRUNK-OR-TREAT · Oct 31, 5:30 PM · Sign up to host a trunk: gracecc.org/trunk

Consistency confirmation: “call to action reads ‘Sign up to host a trunk at gracecc.org/trunk’ in all 5 versions. Date format identical throughout.”

What to noticeFive different versions, one core message: each one was rewritten from scratch for its channel instead of just shortened from the last one, exactly like the skill is supposed to do.
Category 053 skills

Web & Weekend

Where communication meets people: the landing page every channel points to, the sixty seconds on the stage, and the slide readable from the back row.

website-copywriter

Website Copywriter

Ch. 2–4 · The details homeContinues tests 4 & 8

Writes the page everything links to: complete enough for the person checking details at 11:30 p.m. the night before registration closes.

Input — facts for the marriage class landing page

Six Tuesdays from March 10 · 6:30–8:00 PM · Room 204 · $25/couple incl. workbook · led by Pastor Dave & Karen · approved testimony from test 8 · childcare status: unknown.

Output — page copy (condensed)

Hero: “Get your conversations back. — A six-week class for marriages that feel more like logistics than friendship. [Register for March 10 →]

Body: need → how the class works (honest conversation, practical rhythms, no group sharing required) → Mike & Jen’s story with the approved pull quote.

Details block: dates, time, room, cost, workbook, leaders — scannable.

FAQ: Do we have to talk in front of others? (No.) What if we miss a week? Is this for struggling marriages only? (It’s for any marriage that wants better rhythms.) What happens after I register? (Confirmation email with everything you need.)

FAQ gap list — needs answers before publish: ⚠ Is childcare offered? ⚠ Can I attend if my spouse can’t come?

What to noticeThe skill refused to guess about childcare: it flagged the missing answer clearly instead of making something up, because an unfinished page breaks every link pointing to it.
stage-announcer

Stage Announcer

Ch. 3 · Beachfront property

Spoken-word scripts with a human opening and one confident action, because print copy read aloud sounds wooden and wrong.

Input — the brief

“60 seconds, delivered by our host (Sarah) after the second worship set. Family Ministry workshop: ‘Praying with Your Kids,’ one night, Feb 20. Call to action: sign up at the Next Steps table today.”

Output — the script

“If you’ve ever tucked your kids in and thought, I honestly don’t know how to pray with them — you are in very good company. [PAUSE]

Nobody teaches us this. We just… feel like we should know.

So on one night — Thursday, February 20 — Family Ministry is hosting Praying with Your Kids. No prep, no homework, nothing weird. Just practical help from parents a few steps ahead of you, and honest answers to the questions you’ve actually got. [PAUSE]

Here’s what to do: on your way out today, stop by the Next Steps table and put your name down. Takes thirty seconds — and February-you will thank you.”

142 words ≈ 57 seconds. Includes a 15-second ultra-short variant and the non-negotiable note: read it aloud once before Sunday; revise anywhere you stumble.

What to noticeOpens with a human moment, never the event name; ends with one action stated confidently (“here’s what to do”), not “if you’d like to…”: both rules straight from the skill.
slides-and-screens

Slides & Screens

Ch. 3–4 · The overloaded slide, fixed

Short copy plus a plan for what makes the screen and what doesn’t: the direct fix for the book’s seven-event slide that the congregation learned to stop reading.

Input — six items, one rotation

Everyday Faith launch · Serve Day · GriefShare · men’s breakfast · youth car wash · Grace Kids volunteers — “they all want the Sunday screens.”

Output — triage + slide copy

In-service rotation (3): Everyday Faith (churchwide, this week) · Serve Day (churchwide, deadline near) · Grace Kids (broad parent audience, urgent need).

Rerouted: men’s breakfast → lobby screens (reachable group, low stakes) · car wash → lobby + youth channels · GriefShare → not screens; care page & pastor referral per test 9.

SlideHeadline / line / call to action
1THIS SUNDAY: EVERYDAY FAITH · Faith for the other six days · gracecc.org/groups
2SERVE DAY · April 26 — pick your project · Register: gracecc.org/serveday
3GRACE KIDS NEEDS SIX · One Sunday a month · gracecc.org/gracekids-team

Every slide passes the ten-second, back-row-of-the-room test; the call to action wording matches the email and stage versions word for word.

What to noticeThe skill stuck to the two-or-three-slide limit and gave a one-line reason for each call, and it remembered the earlier GriefShare decision without being reminded.
Category 066 skills

Systems & Strategy

The skills that change the job, not just the copy: a clear picture of what you actually own, a shared way to decide what's urgent, a working system for taking in requests, and a week you plan instead of just survive.

scope-mapper

Scope Mapper

Ch. 1 · Own / Influence / Support

Turns “I guess I'm in charge of everything” into a clear, written list of what you actually own, plus the exact words to say when you talk to leadership about it.

Input — Emily’s brain-dump (12 items, excerpt)

Website · weekly email · socials · Sunday slides · kids ministry flyers (“every Thursday, somehow”) · pastor’s letters (“clean it up a bit”) · new-ministry launch assets · event photography · bulletin · ProPresenter uploads…

Output — labeled map (excerpt) + scripts
ItemDomainLabel
Weekly email, website, socialsDigital ChannelsOwn
Pastor’s lettersMessagingInfluence — he owns voice & content; you bring clarity
Kids ministry flyersVisual IdentitySupport — template + review, not production
Sunday slidesSunday ExperienceOwn (content) / Influence (service flow, with worship)

Mismatches flagged: 1) Thursday flyers are being treated as Own — four hours/week that a template system returns to you. 2) New-ministry launches arrive as Support-priced requests but are Create-scale work — needs the lead-time conversation.

Conversation opener (word-for-word from the book): “Can we spend thirty minutes mapping what communications actually owns versus what we help with? I think we’ve got some work to do.”

What to noticeThe output treats every boundary as a way to serve well, not defend turf, and it schedules its own 90-day check-in, since the labels will need updating.
level-sorter

Level Sorter

Ch. 3 · The three levels

“What level is this?”: the five-question sort that turns visibility debates into shared decisions, plus the coaching language.

Input — three live requests

1) Easter services promotion. 2) Women’s mentoring program launch. 3) Tech team training huddle (“can we get it announced Sunday?”).

Output — sorted, with reasoning

Easter → Level 1 Churchwide. For basically everyone, including the community. Full channel support; the loudest channels serve the broadest audience.

Women’s mentoring → Level 2 People Group. Large demographic, real momentum — featured email placement, dedicated social, targeted follow-up. Not stage-by-default: “this is about fit, not importance.”

Tech huddle → Level 3 Ministry. Q4 settles it: the audience is already reachable (the team’s own channel). Coaching reply included: “Love that you’re investing in the team — a Sunday announcement would mostly reach people it isn’t for. Let’s send it straight to your team roster and I’ll give you a template that takes five minutes.”

What to noticeEach answer shows its work, and a “no” always shows up as a better plan instead. (The skill also generated a second output: a one-page guide to the three levels with Grace-specific examples, tested and working.)
request-system-builder

Request System Builder

Ch. 5–7 · The Saturday Morning system

Takes the book’s Saturday Morning story and turns it into a real system you can use: an intake form, timelines, a simple way to score requests, ready-to-send replies, and a guide explaining what the team can realistically handle, all in one run.

Input — the situation

“Solo coordinator, ~600 people. Requests arrive by text, email, and hallway conversation after second service. No form, no stated lead times. I need a real intake system I can roll out at staff meeting.”

Output — the system (excerpt)

Form (9 fields): ministry & contact · what’s happening, plainly · who it’s for, really · the one next step · event date / date needed · Communication Level (best guess is fine) · support type — Create / Collaborate / Consult (“not sure? leave blank & we’ll figure it out together”) · content status · anything already designed.

Lead times, printed on the form: Create 6–8 weeks · Collaborate 3–4 weeks · Consult days.

Response template — the not-yet (1 of 4): “I love this, and I want it to land well — which it won’t on this week’s calendar next to the series launch. Here’s what I can offer: featured email slot on the 22nd and the social template today. Can we aim the bigger push there?”

Full output also includes a simple 5-point scoring guide, ready-made replies for “yes,” “yes, with changes,” and “not this time,” and a one-page guide for ministry partners on what to expect.

What to noticeBuilt to fit a team of one: the skill kept the system simple on purpose, since a complicated system nobody keeps up with is worse than no system at all, and every reply sounds warm enough to send as-is.
request-triage

Request Triage

Ch. 3, 4, 7 · The Monday pass

The weekly workhorse: everything else in this pack, run together against a real Monday inbox: sorting by level and category, checking timelines, deciding what's urgent, and drafting the replies.

Input — Monday’s five requests, exactly as they came in
  • “New ministry launch in 6 days — need logo, landing page, 3 emails, social. Not a big deal!”
  • “Flyer for kids parent meeting next week, nothing fancy”
  • “Sermon series assets — launches in 7 weeks”
  • “Announcement for Marge H.’s memorial service”
  • “Social post for men’s breakfast?”
Output — triage table + replies (excerpt)
RequestLevel / CategoryVerdict
Ministry launch, 6 daysL2 / Create-scaleTimeline fails — honest-conversation reply drafted
Kids flyerL3 / ConsultTemplate + 10-min review; this week
Series assetsL1 / CreateRight runway — schedule kickoff now
Memorial serviceSet aside for a person to handle“This one needs a conversation, not a template”
Men’s breakfast postL2 / ConsultTemplate today

Drafted reply (the 6-day launch): “I’m genuinely excited about this ministry — and I want its first impression to be great, which six days can’t deliver at full scale. Here’s what six days can do well: a clean announcement, an email to the people most likely to care, and a simple sign-up. Then let’s plan the full launch package for [date] — logo, landing page, the works. Can we grab 20 minutes?”

Pattern noticed: “Two of five requests arrived under lead time — the capacity guide from request-system-builder should go out at this month’s staff meeting.”

What to noticeHandled correctly  The memorial announcement wasn’t drafted at all: it was sent straight to a real conversation with pastoral leadership instead, exactly what the pack promises to do with sensitive moments like this.
weekly-comms-planner

Weekly Comms Planner

Ch. 2–4 · The week, plannedContinues test 22

Turns the sorted-out week into a day-by-day plan built around the one big churchwide focus: a week you run instead of a week that just happens to you.

Input — this week

Approved items from Monday’s triage · churchwide focus: Everyday Faith launch Sunday · email sends Wednesday 10 AM · capacity: ~12 production hours.

Output — the weekly plan (excerpt)
DayEmailSocialStage / screens
TueTakeaway: series teaserslides finalized
WedNewsletter (series on top)
FriFriday Story: group member
Sunlaunch-day photo post2 announcements · 3 slides

Production checklist: series slides (done) · kids flyer template pass (Tue, 30 min) · breakfast social template (Tue, 15 min) · series kickoff meeting booked (Thu).

Flags: Story slot preserved (Friday) — the week isn’t all promotion. Youth car wash bumped to next week’s email: “nothing this week should compete with the launch.”

What to noticeOne churchwide focus, protected: the plan pushed a good idea to next week rather than let it compete with the main thing, and it still kept a slot for a real story. This is the book’s advice to protect one focus per week, applied to an actual week.
ai-policy-drafter

AI Policy Drafter

Ch. 5 · A Theology of the Tool

Drafts the AI guidelines the book assigns as homework: built on four simple questions about using AI responsibly, sized to fit how cautious or open the church wants to be.

Input — the situation

“Church of 600. Elder board is cautious but open. Staff and two volunteers already use Claude and Canva AI informally. I need a one-pager the elders can adopt — practical, not a theology paper.”

Output — the policy (excerpt)

Preamble: “Like the printing press and the livestream before it, AI expands what’s possible for good and for harm. Our response is neither blanket rejection nor uncritical embrace, but wise stewardship. These guidelines are how we practice it.”

The four rules, in plain terms: 1) Mission — okay to use for drafting, editing, brainstorming, summarizing, and internal systems. 2) Dignity — no personal, pastoral, or identifiable information about anyone in the congregation ever goes into an AI tool. 3) Stewardship — AI should free up time for the work only a person can do, not replace it. 4) Verification — a human reads and approves every AI draft before it goes out. The tool drafts; we decide.

Always human: pastoral care · decisions about people · anything presented as someone’s own words · crisis and grief communication. Never: manufactured testimonials · impersonated voices · AI-generated content passed off as human where it matters.

Delivered with a three-bullet staff-meeting summary and an annual review cadence. Flagged for elder review before adoption — “the draft informs their judgment; it doesn’t replace it.”

What to noticeThe policy the pack ships with is the same ethic the pack runs on: the “always human” list is why there are no crisis or pastoral-messaging skills in this product at all.
Results

24 for 24.

Every skill delivered what it promised, matched the church’s voice, kept every fact accurate, and followed the book’s approach. And twice, a skill correctly stepped back instead of pushing forward: it wouldn’t invent a testimony (test 4), and it sent a memorial announcement to a human instead of writing it (test 22).

#SkillScenarioWhat it used from the bookResult
1simplify-the-announcementTrunk-or-Treat submissionSimplicity Filter; Headline → Next Step → Details
2decode-the-churcheseNewcomer welcome emailChurchese trades; replace vs. explain
3trifecta-editServe Day email (book case)Simple / Clear / Consistent check
4story-first-rewriteMarriage class promo (book case)Four-Step Story Framework; wouldn’t invent a quote
5load-your-church-voiceSamples + interviewLanguage & tone consistency
6voice-checkVolunteer’s retreat draftConsistency Audit
7ministry-style-guideA one-page guide for ministry leadersWritten guidelines that equip, not restrict
8story-gathererMarriage class testimonyEvidence of Transformation + approval step
9value-filterGriefShare stage requestThe Value Filter (3 questions)
10campaign-builder“Everyday Faith” seriesLevels + story arc + One call to action
11newsletter-writerSeven raw itemsThe book’s three-part email structure
12ministry-email-writerGrace Kids volunteer askValue-first framing; real ask
13social-copywriterServe Day story + class promo70/30 story mix
14social-plannerOctober calendarRhythm consistency; content categories
15channel-adapterTrunk-or-Treat spineRepeat the next step everywhere
16website-copywriterMarriage class landing pageThe details home; FAQ gaps
17stage-announcer60-second workshop scriptSpoken-word rules; one action
18slides-and-screensSix items, one screen rotationDeciding what makes the screen; 10-second rule
19scope-mapperEmily’s 12-item brain-dumpOwn / Influence / Support, across five areas of the job
20level-sorterEaster / mentoring / tech huddleThree levels; five questions
21request-system-builderA solo coordinator’s request intakeThe Saturday Morning system; timelines for each type of request
22request-triageMonday’s five requestsEvery tool in this pack, used together; caught a sensitive request
23weekly-comms-plannerLaunch weekChurchwide focus protected
24ai-policy-drafterOne-page policy for eldersFour questions for using AI responsibly
What’s deliberately missing

No crisis scripts. No pastoral messaging. On purpose.

Two of these tests show a skill saying no to work instead of just doing it: it wouldn’t make up a testimony, and it wouldn’t write a memorial announcement. That’s on purpose, straight from Chapter 5 of the book: the tool drafts, you decide, and anything that needs a leader’s judgment or a pastor’s presence gets handed back to a person, every time.

The book teaches the approach. The Skills Pack puts it into practice. This report shows that in action.

Grace Community Church and all named individuals are fictional; scenarios are adapted from case studies and frameworks in The Church Communicator’s Playbook by Josh King. Tests shown here were run in Claude with the Skills Pack installed and a loaded voice profile; outputs are the skills’ own work, excerpted where marked. These skills are just written instructions, so they work in Claude, ChatGPT, or Gemini — you set them up a little differently depending on which one you use, but the instructions themselves don’t change. This report is not affiliated with Anthropic, OpenAI, or Google. The AI Skills Pack works with Claude, ChatGPT, or Gemini; free tiers are supported. © 2026 Josh King · churchcommplaybook.com